tinuzz
Forum Replies Created
-
Forum: Plugins
In reply to: [Trackserver] Maximum of tracks?Hi Wolfgang,
Looks cool, I’ll take a look at that tool shortly. Nice to see other people’s solutions for manipulating GPX files ; I have written a few myself.
There’s always GPSbabel, which can do everything and more…
I checked out the simplification algorithms in GPSbabel, and I think I can implement one in PHP for in Trackserver. Maybe I’ll give it a go.
Cheers,
Martijn.Forum: Plugins
In reply to: [Trackserver] Maximum of tracks?Hi Viktor,
“After that I don‘t get any error but just a map without any tracks and any error.”
Yes. The track data is requested from Javascript with an AJAX request, which is supposed to return a JSON object. In your case, the response is not JSON, but HTML containing the error message.
I think Trackserver would relay an error message to the user if the AJAX request would be unsuccessful, but in your case, the server is returning a 200 status, which means ‘OK’. So, basically, Trackserver is confronted with a successful request, but with invalid data, which it doesn’t really handle. It just doesn’t show any track data, because there is nothing to show.
Apart from increasing the memory_limit or simplifying the tracks, there’s nothing to do about this in the short term, I’m afraid.
Best regards,
Martijn.Forum: Plugins
In reply to: [Trackserver] Maximum of tracks?To be more clear: it’s not so much the number of tracks, but the number of points that’s the problem.
You could consider using simplified versions of the tracks for the total overview, so that the number of points is lower. But that would require you to process the tracks outside of trackserver.
With ‘simplified’, I mean something like this:
https://www.gpsbabel.org/htmldoc-development/filter_simplify.htmlBest regards,
Martijn.- This reply was modified 4 years, 4 months ago by tinuzz.
Forum: Plugins
In reply to: [Trackserver] Maximum of tracks?Hi Viktor,
Great journey, I’m jealous 🙂
When I request only the track data for the ‘Todo el viaje’ map, I get a PHP error from your webserver:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in xxx/wp-db.php on line 2022
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in xxx/functions.php on line 4639
I think you should increase the memory_limit setting on your PHP instance.
This nicely explains that it worked before, but started to show problems gradually, because the memory usage would increase with the number of tracks in a single query.
I hope this helps.
Best regards and safe travels,
Martijn.Forum: Reviews
In reply to: [Trackserver] Very Nice pluginThank you!
Forum: Plugins
In reply to: [Trackserver] OSMANd track managementWell, 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.Forum: Plugins
In reply to: [Trackserver] OSMANd track managementHi,
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.Forum: Plugins
In reply to: [Trackserver] elevation dateHi,
Yes, you are right. Elevation data was simply omitted from the exported data. Your fix is good, I will include it in the next release, which I hope to get out in the next month or two. Thank you.
Best regards,
Martijn.Forum: Plugins
In reply to: [Trackserver] embedded map issueHi,
This is a little embarrassing. The HTML template for embedded maps that shipped with Trackserver is broken. It is missing important function calls, and in fact it does not load any of the necessary CSS and JavaScript because of that. TBH, I have no idea how it could ever have worked, even for me. I just don’t know and I sincerely apologize.
To make it work, you have to download this file:
https://github.com/tinuzz/wp-plugin-trackserver/blob/master/embedded-template.php
and upload it to the Trackserver folder (wp-content/plugins/trackserver/) on your WordPress install. The only difference with the previous file is a call to
wp_head();at the top, and a call towp_footer();at the bottom.Of course, this fix will be part of the next release, which I hope to get out soon.
Simply adding calls to
wp_head()andwp_footer()will potentially add a lot of CSS and Javascript to the embedded map HTML, because all of your WordPress plugins will be active for embedded maps, like for any other page. The next Trackserver release will limit the CSS and Javascript in an embedded map to the styles and scripts used by Trackserver itself, and not include any styles and scripts added by other plugins, keeping the map HTML lean.Best regards,
Martijn.- This reply was modified 5 years, 1 month ago by tinuzz.
Forum: Plugins
In reply to: [Trackserver] embedded map issueSorry for not replying any sooner.
This is a weird issue. The page source that you posted is missing lots of important stuff, like CSS and Javascript for rendering the map and the tracks.
It seems that the template in Trackserver is to blame, but at this point I’m kind of baffled by how I could have not noticed that before.
I’ll look into it. Thank you.
Forum: Plugins
In reply to: [Trackserver] Track not shwoing?I didn’t notice this was a duplicate post, and did in fact reply to the other one. Closing this.
- This reply was modified 5 years, 1 month ago by tinuzz.
Forum: Plugins
In reply to: [Trackserver] Track not shwoing?Closing due to inactivity.
Forum: Plugins
In reply to: [Trackserver] GPS-Download-LinkThe change described above will be part of the next release.
Closing due to inactivity.
Forum: Plugins
In reply to: [Trackserver] Track not shwoing?Sorry for not replying to your post. Did you manage to get it working?
Best regards,
Martijn.The next release of Trackserver will work differently: the access keys, that are already in use for TrackMe and other protocols, will work for all protocols. That way, they will work like ‘application passwords’ that you sometimes find in other applications that need to support clients that do not understand SSO protocols like oAuth. That will most likely solve your problem, but I need to ask for your patience, because it will take some more time for the next release to be ready.
Martijn.