(Difference between revisions)

Jump to: navigation, search
(Issues: KML folder)
Current revision (19:00, 7 September 2007) (view source)
m (Tools)
(6 intermediate revisions not shown.)
Line 56: Line 56:
===Existing formats===
A number of other formats (which route/ track parsers may wish to export) are listed at
*[ GPS Babel] is a free command line utility (there is a GUI, but it has limited functionality) for converting between these formats.
*[ GPS Visualizer] reads a variety of GPS formats <blockquote>including but not limited to: GPX, OziExplorer, (.loc), IGC sailplane logs, Garmin Forerunner (.xml/.hst/.tcx), Timex Trainer (v1.3+), Cetus GPS, PathAway, cotoGPS, CompeGPS, TomTom (.pgl), IGN Rando (.rdn), Emtac Trine, Suunto X9/X9i (.sdf), NetStumbler/WiFiFoFum, GPSManager, MS Excel, and of course tab-delimited or comma-separated text</blockquote> and converts them, maps them, or outputs a graphical representation or plain-text list.
===Typical mandatory attributes===
===Typical mandatory attributes===

Current revision


Geo Waypoint Trails

An exploration of publishing information about sequences of geographical points using series of Geo (or other) microformats.


Conceptually, a collection of points, with no sequential relationship (the county towns of England, say, or all skyscrapers in New York), is deemed a collection (or set) of individual Waypoints. A sequentially-ordered collection of points may be expressed as a track or a route. Tracks are a record of where a person has been, routes are suggestions about where they might go in the future. So, for instance, there might be timestamps for each point in a track (because someone is recording where and when they were there), but timestamps for each point in a route are unlikely to be provided, because the author is suggesting it, and nobody might ever have travelled it.

A route which ends at its beginning may also describe a boundary (also called a box or polygon). A boundary may be for an object or area on any scale, from a small building or plot of land to a continent, at any level of granularity.

It may therefore be appropriate to use a sequence of hCalendar microformats for tracks and of hCard microformats for routes, boundaries and waypoints.

The Problem

To allow the publishing of series of waypoints in such a way that they are downloadable and that their ordering is parsable.


Real-World Examples


    <div class="geo">
      <span class="latitude">52.38616</span><br/>
      <span class="longitude">4.91199</span>
  <td ><a href="...">Waypoint 10</a></td>
  <td >Amsterdam (3 km) <a title="" href="...">Map</a></td>


  <wpt lat="39.921055008" lon="3.054223107"> 
  <name>Cala Sant Vicenç - Mallorca</name> 

Existing formats

A number of other formats (which route/ track parsers may wish to export) are listed at


Typical mandatory attributes

Typical optional attributes



See Also

geo-extension-waypoints was last modified: Friday, September 7th, 2007