tinuzz

OK, then something else must be wrong.

How are your PHP / troubleshooting skills?

Around line 1429, there is this:

$this -> osmand_terminate( 200, 'OK, track ID = ' . $track_id );

This line can be changed to include any desired information, because I don’t think that OsmAnd cares about the output.

I would like to know the values of the following things:

• $_GET["timestamp"]
• round( (int) urldecode( $_GET["timestamp"] ) / 1000 );
• $ts

If you can include that in the output and then try the OsmAnd URL in a browser:

http://www.vomac-nl.com/osmand/?lat=51.586636&lon=4.9822874&timestamp=1449990037252&altitude=60.0&speed=0.0&bearing=0.0&username=xxx&key=xxxx

My suspicion is, that the timestamp is changed to 0 at some point, but I don’t know why.

Hm, there must be something wrong with the way I calculate the timezone offset for the timestamp.

Can you edit trackserver.php, and remove this line from the function handle_osmand_request():

$ts += $this -> utc_to_local_offset( $ts )

It should be line 1371 or close to that (my local version has some changes compared to v1.9, so it could be off by a few lines).

I’d like to know if the removal of that line makes a difference in the result. If it does, we know that it’s the timezone offset calculation that’s causing the problem.

Best regards,
Martijn.

Hi Marc,

I see markers on that map just fine, but maybe there is a misunderstanding: the markers appear just at the start and the end of a track, and not for every trackpoint. They are the green (start) and red (end) dots on the map…

This issue can in no way be related to timestamps being off, because the timestamps aren’t even part of the track as it is downloaded from the server, only the coordinates are, and the markers are just drawn at the first and last trackpoint, and don’t (can’t) use the timestamps at all.

Best regards,
Martijn.

Can you have a look at you webserver access logs and figure out what the timestamps that your WordPress receives from OsmAnd look like?

They should be in milliseconds sinds 01-01-1970 (something like ‘1450101110157’). I cannot reproduce the issue with OsmAnd 2.2.3.

The code that converts the timestamp for storing it in the database involves some timezone calculations, which are always tricky, but it seems unlikely that the resulting timestamp would be in 1970.

Is your timezone configured correctly in WordPress and/or PHP?

As per https://itunes.apple.com/nl/app/sendlocation/id377724446:

“Where you must provide the “http://yourserver.com/yourscript.php” part to application settings.”

It would be possible to implement a scheme where the WordPress username becomes part of the URL, like this:

http://yourserver.com/wordpress/<sendlocation-slug>/<username>/?lat=...

and the deviceID could be used as a password.

If anyone is willing to test this, I can put support for it in GitHub….

Best regards,
Martijn.

How do you see ‘multiple live tracks from the same user’? In the current implementation, the ‘live’ track is just the user’s last updated track, so the concept of ‘multiple live tracks’ does not exist.

I tend to see WordPress users as real persons, and the idea of a single person being in multiple places at once seems a little unnatural 😉

I am open to suggestions though.

Best regards,
Martijn.

Hi,

Sorry for the delayed response, I havent’t been around computers a whole lot for the past few weeeks.

What is on the road map is multiple tracks per map, but NOT multiple LIVE tracks per map, sorry.

In Trackserver there is no way to share tracks between users, so there is no way to create a map with tracks from multiple users. This is not on the road map.

Best regards,
Martijn.

Hi,

Glad you worked it out.

Cheers,
Martijn.