tinuzz

Hi,

If the ‘Full custom URL’ is what Trackserver shows in the profile, then there must be something weird with your setup.

Trackserver tries to find out what the ‘blog URL’ is, which it seems to do correctly (https://excessiveweaving.com.au/). It then tries to match all incoming requests against the configured ‘slug’ for the endpoint for location updates (‘mapmytracks’). This is where things seem to fail, as this results in a 404. Unfortunately, I cannot explain this.

If you’re comfortable with PHP, you should add some debugging code to the parse_request() function (file: class-trackserver.php, line 1425 in Trackserver v4.3.2).

The MapMyTracks handling code starts at line 1485:

https://github.com/tinuzz/wp-plugin-trackserver/blob/7fa62a6c1b0d7b5dd3d1a85603c8344a3f172e59/class-trackserver.php#L1485

I would be interested in the values of $request_uri and $uri on line 1488. These should be the same, and in your setup they apparently are not.

Best regards,
Martijn.

Hi,

‘localhost:8888’ could never work, you need to fill in the name of your WordPress server.

Best regards,
Martijn.

Hi @ewsatsea,

That’s some incredible journey you’re making.

Regarding the tools you’re using, I’m not quite sure what to advise. It seems you are better informed on satnav applications than I am 😉 In general, I can think of two ways to achieve what you want, both of which are supported by Trackserver:

• GPX (or other file format) upload
• Live tracking

For live tracking, you obviously need an internet connection that is mostly available. OsmAnd had never been my favorite for live tracking. It is difficult to configure and it drains my battery in no time at all. OruxMaps and TrackMe are the reliable choices for the Android platform.

GPX files with extension should be handled by Trackserver without problems, as long as they conform to the spec. That means that the extensions should be properly namespaced. You can find more information on validating GPX files here: https://www.topografix.com/gpx_validation.asp

Regarding the ‘jump’ around the globe when crossing from 180E to 180W: this happens because that’s how Leaflet (the JS mapping library) works. Leaflet supports coordinates < -180 and > 180 to accomodate for this. It will then draw the lines on adjacent ‘copies’ of the world. Trackserver does not implement this yet.

So if you cross the boundary in westward direction, like you did, all the longitudes from that point on should be corrected with -360 degrees (so you’d go from -180 to -181).

This can probably be fixed quite easily for tracks that are served from Trackserver’s database. I’m not sure it can be fixed for external GPX / KML files.

Unfortunately, fixing this would require a new release of Trackserver, and I’m in the middle of quite a big code restructuring effort which kind of makes that impossible right now. I’ll see what I can do.

Best regards,
Martijn.

Hi,

Your question isn’t entirely clear. In your first sentence, you write “Seems to work fine.”. What exactly works fine?

I assume you are using the Online tracking feature of the GPX plugin for live tracking. Are your location updates appearing in Trackserver? You write “there is no tracks uploaded”, so I assume they are not?

You should check your webserver access and/or error log to see what OsmAnd is sending to the server and why that doesn’t work.

Are you using the Full URL as displayed in your Trackserver profile in the OsmAnd settings, including the ‘username’ and ‘key’ parameters?

Regarding the error that you’re getting with uploading the GPX file, I’m not sure why that happens. I just tried it with a GPX from OsmAnd 3.4.8, and it worked fine. Can you send me one of your GPX files so I can have a look to see what is wrong with it?

To be clear: Trackserver validates the uploaded XML file against the GPX specification (version 1.1 first, version 1.0 second). If this gives an error, there is most likely something wrong with the file. I have seen many many applications that generate non-conforming GPX files, that why the check is there in the first place. It could be anything from self-invented or missing tags, to an inappropriately formatted timestamp field. I can’t say without looking at the actual file.

Best regards,
Martijn.

Hi,

From your post, it is not entirely clear what exactly doesn’t work. Is it the collection of location data (creation of tracks), or the display of tracks on a map?

I suspect it is the former, since you write about changing the username in “the app”. What app is that? Are you aware that different users have different passwords? And that some apps (TrackMe, OsmAnd) use a ‘secret’ which is set in the Trackserver user profile, and that other apps (OruxMaps, OwnTracks) should use the user’s WordPress password?

But I’m confused since you also write that you can get the map to show a live location. Is that for any user? That would mean that data collection /does/ work.

Can you be a little more specific in the problem description?

Regards,
Martijn.

In class-trackserver.php, look for a function named ‘validate_user_ids’.

It checks if a list of user-ids exist in the database, but if the author of the page isn’t allowed to publish other users’ tracks (i.e. s/he’s an admin), all user-ids except the author id are removed from the list before the check:

if ( ! user_can( $author_id, 'trackserver_publish' ) ) {
	$user_ids = array_intersect( $user_ids, array( $author_id ) );
}

If you wrap this code in something like:

if ( $author_id != null ) {}

It will probably work. You should check the actual value of $author_id in your case, because I don’t know if it is null or something else.

Good luck,
Martijn.

What have you tried?
What didn’t work?