tinuzz

Well, first of all, collecting locations and displaying them on a map are two different things.

1) Does TrackMe display any errors during live tracking?
2) Do any tracks appear in Trackserver’s database (see ‘Manage tracks’) ?

Regards,
Martijn.

• This reply was modified 6 years ago by tinuzz.

The HTTP upload functionality as currently implemented requires HTTP Basic Auth with the WordPress username and password. It only workst with HTTP POST.

Does that work?

Best regards,
Martijn.

There is the [tslink] shortcode, since Trackserver 3.0. To quote the original blog post:

GPX downloads

Trackserver has a new shortcode: [tslink], perhaps not the most intuitive name. This shortcode produces a link, with which the specified tracks can be downloaded as a GPX file. Other formats are on the horizon, please open a feature request issue on Github if you need a specific format. [tslink] is used almost the same as [tsmap], except that it lacks all the styling attributes.

[tslink track=12,87,525 user=patrick]

will give you a link to a dynamically generated GPX file, containing tracks with IDs 12, 87 and 525, as well as Patrick’s latest track. There is also a class attribute that can be used for styling the resulting <a> element, and a format attribute whose only valid value is ‘gpx’ at this time.

Does that help?

If you envision something else, please let me know!

Best regards,
Martijn.

• This reply was modified 6 years, 2 months ago by tinuzz.
• This reply was modified 6 years, 2 months ago by tinuzz.
• This reply was modified 6 years, 2 months ago by tinuzz.

Just a quick answer, because I didn’t have mucht time to look into it.

It’s not very complicated, but there are one or two caveats to work around.

First, adding support for ‘geojson’ URLs is easy. Basically, you search the ‘class-trackserver.php’ file for occurrences of ‘kml’, and duplicate that code, replacing all instances of ‘kml’ with ‘geojson’:

Insert at 1109:
'geojson' => false,

Insert at 1278:

			if ( $atts['geojson'] ) {
				$urls = explode( ' ', $atts['geojson'] );
				$j    = 0;
				foreach ( $urls as $u ) {
					if ( ! empty( $u ) ) {
						$u        = $this->proxy_url( $u, $post_id );
						$tracks[] = array(
							'track_id'   => 'geojson' . $j,
							'track_url'  => $u,
							'track_type' => 'geojson',
							'style'      => $this->get_style(),
							'points'     => $this->get_points(),
							'markers'    => $this->get_markers(),
							'markersize' => $this->get_markersize(),
						);
						$j++;
					}
				}
			}

For the rest, Trackserver already knows how to display GeoJSON content, because it can use GeoJSON for internal tracks too.

First caveat: due to its internal use of GeoJSON, Trackserver expects the actual GeoJSON data to be wrapped in some Trackserver-specific construct, so the code must be changed for this use case. The simplest fix would be this:

In trackserver.js, on line 60, replace

return o.track;

with

            if (o.hasOwnProperty( 'track' )) {
                return o.track;
            }
            else {
                return o;
            }

With that in place, I was able to display the ‘majorincidents.json’ file using

[tsmap geojson=<url>]

It doesn’t seem to work with polygons, though. If your run into CORS restrictions loading JSON from an external domain, you may have to use Trackserver’s proxy feature.

There may be other issues. Please let me know how well this works.

Best regards,
Martijn.

Hi,

In the app, under “TrackMe Server settings”, do you have “Sync my positions” checked?

This setting was introduced a while after Trackserver was born, and the screenshots don’t mention this setting, even though it is disabled by default, IIRC.

If:
– you have at least one track in Trackserver,
– the track actually has some locations,
– you have [tsmap user=@] on your post/page,
– the author of the post/page is the same user that has the track,

the track should be visible. If it’s not, I’m not sure what is wrong.

Best regards,
Martijn.

Well, I it might. You would have to create the same amount of WordPress accounts and instruct everyone how to configure their apps.

And I’m not sure how the webpage with the map would perform if it had to show 100 tracks, but you would have to try.

Trackserver is ‘multi user’ and a WordPress user with sufficient privileges can publish a map with other users’ tracks on it, so that would not be a limitation.

Regards,
Martijn.

Hi Jason,

The “No tracks to display” message seems quite accurate to me if there are no tracks in your database 😉

The URL seems correct, as in: https://ontheroadbike.com/trackme/requests.z (the final URL that TrackMe uses for location uploads) is handled by Trackserver correctly, as far as I can tell.

What does TrackMe say in its log?

Best regards,
Martijn.

Great find. Good to hear that it works.

The fact that the value of $request_uri is ‘/.info.php’ seems very strange to me.

Best regards,
Martijn.