Plugin Author
tinuzz
(@tinuzz)
Hi,
First off, I am happy that Trackserver is almost perfect for you 🙂
Regarding the track names from OsmAnd and the hourly rotation, please look at the ‘OsmAnd trackname format’ on the options page. The default value is ‘OsmAnd %F %H’. If you remove the ‘%H’, you’ll get daily rotation. Remove the strftime() placeholders altogether to use a static name (which I wouldn’t recommend).
I have had a request for allowing the track name to be set from OsmAnd before, and I’ll add something in the upcoming release.
Regarding the display of the track in WordPress, use the ‘opacity’ shortcode attribute. Use ‘opacity=0.0’ to hide the track, and ‘markers=e’ to remove the green marker at the start, so you only get the red marker of the latest position.
Does that work?
Best regards,
Martijn.
No not almost perfect.. its perfect 🥰
The information was there in the settings page, I hadn’t read it properly.. so user error.
Why do you not recommend using a static name? It would seem a good solution to my issue of merging tracks? I am thinking of having a static name “OSM locationname” and change locationname when I want to start a new segment of my journey.
I have already configured OSMand to minimise the number of GPS points it sends by increasing the minimum displacement to 50m, the general log interval to 5 minutes (my boat is slow), and the minimum speed to >0
Plugin Author
tinuzz
(@tinuzz)
Well, if you’re going to change the name on a regular basis, it’s not really static anymore 😉
My reservation would be that you’d keep accumulating points in a single track, which would grow larger over time, and become unmanageable at some point.
In the next release, I will include support for a ‘label’ URL parameter, so you can set it from within OsmAnd, and in Trackserver, you could specify something like ‘OSM {label}’ as your trackname format.
I think for most people, the time-based machanism would be sufficient. For example, if you’re hiking, motorcycling or cruising around in a campervan, one track per day would seem entirely reasonable to me 😉 But I see your use case and I will support it in Trackserver v5.
Best regards,
Martijn.
