Each of them can contain multiple values, separated by commas (or colons, in the case of ‘dash’), to be applied to different tracks in order. The following attributes apply to tracks that are drawn on the map. For a map with only static tracks, this number represents the maximum zoom level, so the map will always fit all the tracks. For a map with live tracks, this number is absolute. zoom: the zoom factor to use for the map, a number between 0 and 18.Please check the Trackserver user profile page in the WordPress backend for which placeholders are supported. Instead of ’true’ or ‘yes’, a template string containing one or more placeholders (like, etc.) can be given to the attribute, in which case it overrides the value specified in the user profile. When multiple live tracks are requested, the infobar will display the data of the first track only. This only works with ’track=live’ or the ‘user’ parameter, and has no effect in other cases. infobar: true (or ’t’, ‘yes’ or ‘y’), false (default), or a template string, to specify whether an information bar should be shown on the map, when live tracking is active.Multiple URLs should be separated by spaces, and the value as a whole enclosed by double quotes (kml=” If enabled in the settings, when a url is prefixed with the string ‘proxy:’, the request is proxied through Trackserver. kml: one or more URLs to KML files to be plotted on the map.Multiple URLs should be separated by spaces, and the value as a whole enclosed by double quotes (gpx=” If enabled in the settings, when a url is prefixed with the string ‘proxy:’, the request is proxied through Trackserver. gpx: one or more URLs to GPX files to be plotted on the map.The only effect this has, at the moment, is that intermediate start markers are yellow instead of green. continuous: true (default) or false (or ‘f’, ‘no’ or ‘n’), for lack of a better word, to indicate whether multiple tracks should be considered as one continuous track.class: a CSS class to add to the map div for customization, default: not set.align: ‘left’, ‘center’ or ‘right’, default: not set.The value is a time expression in the form of a number and a unit, for example: ‘120s’, ’30m’, ‘2h’, ‘3d’. If this parameter is given, all user tracks that have not been updated in the last X amount of time, will not be displayed. maxage: the maximum age of a live track for it to be included on the map.This can be used for example with an externally updated GPX or KML file. live: true (or ’t’, ‘yes’ or ‘y’), or false (default), to force live tracking for this map.The map view will follow the latest location and the infobar (if present) will display its information. When the end-marker is enabled for a live track (and why shouldn’t it?), clicking it will change the focus of the liveupdate to that track. When viewing the map, the liveupdate feature will follow the track of the first user specified. A literal means the author of the post (you). user: one or more user IDs, separated by commas, who’s latest track to follow ‘live’.track: one or more track IDs, separated by commas, or ‘live’ (deprecated, is preferred).Leaflet.fullscreen by John Firebaugh and othersįAQ What are the available shortcode attributes?.Leaflet.js by Vladimir Agafonkin and others.It includes some code and libraries written by other people: This plugin was written by Martijn Grendelman. Trackserver requires PHP 5.3 or newer and it needs both DOMDocument and SimpleXML extensions installed. See the FAQ section for more information on the shortcode’s supported attributes. To publish a map with a track in a post or a page, just include the shortcode: Maps can be viewed in full-screen on modern browsers. Maps are displayed using the fantastic Leaflet library and some useful Leaflet plugins are included. PhoneTrack-Android also works with OsmAnd’s protocol (Trackserver >= 4.3)Ī shortcode is provided for displaying your tracks on a map.MapMyTracks protocol, for example using OruxMaps, including upload functionality.Several mobile apps and protocols are supported for getting tracks into trackserver: It’s all about keeping your data to yourself. Unlike other plugins that are about maps and tracks, Trackserver’s main focus is not the publishing, but rather the collection and storing of tracks and locations. It can also be used for live tracking, where your visitors can follow you or your users on a map. It is a server companion to several mobile apps for location tracking, and it can display maps with your tracks on them by using a shortcode. Trackserver is a plugin for storing and publishing GPS routes. Getting your GPS tracks into WordPress and publishing them has never been easier! Please read the release notes for more information. NOTE: Trackserver v5.0 contains backwards-incompatible changes and changes to client configurations are needed.
0 Comments
Leave a Reply. |