Difference between revisions of "geo-extension-waypoints"

From Microformats Wiki
Jump to navigation Jump to search
(→‎Issues: sequencing)
m (move toc and close a code tag)
 
(40 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Geo Waypoints =
+
= Geo Waypoint Trails =
An exploration of adding waypoint information to Geo data. [http://en.wikipedia.org/wiki/Waypoint Waypoints] are a series of points, describing routes or boundaries.
+
 
 +
An exploration of publishing information about sequences of geographical points using series of Geo (or other) microformats.
 +
__TOC__
 +
==Terms==
 +
 
 +
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 [http://en.wikipedia.org/wiki/Waypoint 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 ==
 
== The Problem ==
To allow the publishing of waypoints in such a way that they are downloadable and parsable.
+
To allow the publishing of series of waypoints in such a way that they are downloadable '''and''' that their ordering is parsable.
  
 
== Participants ==
 
== Participants ==
Line 12: Line 21:
 
*[http://gpsnepal.com/waypoint.php?trek=everest Jiri to Everest Trek in Nepal]
 
*[http://gpsnepal.com/waypoint.php?trek=everest Jiri to Everest Trek in Nepal]
 
**(or any other treks on that site)
 
**(or any other treks on that site)
 +
**relevant mark-up: <code><nowiki><tr><td>Jiri Bus Park</td><td>27° 38.173'</td><td>86° 13.909'</td><td>1924</td></tr></nowiki></code> ("1924" is the elevation)
 
*http://members.aol.com/gpspage/waypoints.html
 
*http://members.aol.com/gpspage/waypoints.html
 
*[http://grothserver.princeton.edu/~groth/frs142s04/waypoint_hunt/waypoint_hunt.html Freshman Seminar Waypoint Hunt]
 
*[http://grothserver.princeton.edu/~groth/frs142s04/waypoint_hunt/waypoint_hunt.html Freshman Seminar Waypoint Hunt]
 +
**relevant mark-up: <code><nowiki><tr><td>BENCH</td><td>40.33855</td><td>-74.66465</td><td><a href="bench.html"><img src="bench_c.gif" alt="[...]"></a></td></tr></nowiki></code>
 +
 +
===Collections===
 +
*[http://www.poi66.com/ POI66]
 +
**example: [http://www.poi66.com/maps/show_album?album=adelaarspad Amsterdam CS-Alkmaar CS walking route] (n.b long page; 612 waypoints)
 +
**relevant mark-up: <s><code><nowiki><li><div>waypoint 10<br/>Latitude 52.386165<br/>Longitude 4.91199</div></li></nowiki></code></s>
 +
  <pre><nowiki>
 +
  <tr>
 +
  <td>10</td>
 +
  <td>
 +
    <div class="geo">
 +
      <span class="latitude">52.38616</span><br/>
 +
      <span class="longitude">4.91199</span>
 +
    </div>
 +
  </td>
 +
  <td ><a href="...">Waypoint 10</a></td>
 +
  <td >Amsterdam (3 km) <a title="" href="...">Map</a></td>
 +
  </tr>
 +
</nowiki></pre>
 +
 +
===Other===
 +
* [http://www.topografix.com/gpx.asp GPX] - XML schema for trails
 +
**[http://en.wikipedia.org/wiki/GPX GPX on Wikipedia]
 +
**example (extract):
 +
<pre><nowiki>
 +
  <wpt lat="39.921055008" lon="3.054223107">
 +
  <ele>12.863281</ele>
 +
  <time>2005-05-16T11:49:06Z</time>
 +
  <name>Cala Sant Vicenç - Mallorca</name>
 +
  <sym>City</sym>
 +
  </wpt>
 +
</nowiki></pre>
 +
 +
===Existing formats===
 +
A number of other formats (which route/ track parsers may wish to export) are listed at http://www.gpsbabel.org/capabilities.html
 +
 +
===Tools===
 +
*[http://www.gpsbabel.org/ GPS Babel] is a free command line utility (there is a GUI, but it has limited functionality) for converting between these formats.
 +
*[http://www.gpsvisualizer.com/ GPS Visualizer] reads a variety of GPS formats <blockquote>including but not limited to: GPX, OziExplorer, Geocaching.com (.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===
 +
*Latitude (WSG84, using decimal or degrees-minutes-seconds values)
 +
*Longitude (ditto)
 +
*text label
 +
 +
===Typical optional attributes===
 +
*timestamp
 +
*elevation
 +
*image
 +
*note ?
 +
*url ?
  
 
==Issues==
 
==Issues==
*How to differentiate between a route (for example in the shape of a letter "U") and a boundary - in other words, to say whether or not, after the last point, the line returns to the first.
+
*How to indicate that a set of waypoints is a specific, but unordered, collection (i.e. a set of all the metro stations in Paris, and another set of all the underground stations in London, may be published on the same page)
*How to sequence/ timestamp waypoints
+
**KML uses "Folder" for each such set. e.g [http://tinyurl.com/32o6lm]
**Perhaps using [[hatom|hAtom]] and/ or [[hcalendar|hCalendar]]?
+
*How to sequence routes
 +
**Perhaps using order in source code, ordered lists, [[hcalendar|hCalendar]] or [[hatom|hAtom]]?
 +
**We could use [[hatom|hAtom]] and the feed category to distinguish between ordered, unordered and polygons.
 +
***hAtom requires both an author and date, neither of which are required for routes or polygons. [[User:AndyMabbett|Andy Mabbett]]
 +
*How to timestamp tracks (timestamps imply a chronological sequence)
 +
**Perhaps using [[hcalendar|hCalendar]]?
 +
*How to differentiate between a route (for example in the shape of a letter "U") and a boundary (or polygon) - in other words, to say whether or not, after the last point, the line returns to the first.
 +
**Suppose we use <code>class="folder"</code> for a sequence (per KML; see above). We could have <code>class="folder route"</code> or <code>class="folder polygon"</code>.
 +
*What can we learn, or use, from the GPX (XML schema for GPS data) specification?
 +
 
 +
==References==
 +
*[http://dublincore.org/documents/dcmi-box/ DCMI Box Encoding Scheme]
  
 
== See Also ==
 
== See Also ==
 
{{geo-related-pages}}
 
{{geo-related-pages}}

Latest revision as of 00:51, 17 February 2021

Geo Waypoint Trails

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

Terms

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.

Participants

Real-World Examples

Collections

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

Other

  <wpt lat="39.921055008" lon="3.054223107"> 
  <ele>12.863281</ele> 
  <time>2005-05-16T11:49:06Z</time> 
  <name>Cala Sant Vicenç - Mallorca</name> 
  <sym>City</sym> 
  </wpt>

Existing formats

A number of other formats (which route/ track parsers may wish to export) are listed at http://www.gpsbabel.org/capabilities.html

Tools

  • 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

    including but not limited to: GPX, OziExplorer, Geocaching.com (.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

    and converts them, maps them, or outputs a graphical representation or plain-text list.

Typical mandatory attributes

  • Latitude (WSG84, using decimal or degrees-minutes-seconds values)
  • Longitude (ditto)
  • text label

Typical optional attributes

  • timestamp
  • elevation
  • image
  • note ?
  • url ?

Issues

  • How to indicate that a set of waypoints is a specific, but unordered, collection (i.e. a set of all the metro stations in Paris, and another set of all the underground stations in London, may be published on the same page)
    • KML uses "Folder" for each such set. e.g [1]
  • How to sequence routes
    • Perhaps using order in source code, ordered lists, hCalendar or hAtom?
    • We could use hAtom and the feed category to distinguish between ordered, unordered and polygons.
      • hAtom requires both an author and date, neither of which are required for routes or polygons. Andy Mabbett
  • How to timestamp tracks (timestamps imply a chronological sequence)
  • How to differentiate between a route (for example in the shape of a letter "U") and a boundary (or polygon) - in other words, to say whether or not, after the last point, the line returns to the first.
    • Suppose we use class="folder" for a sequence (per KML; see above). We could have class="folder route" or class="folder polygon".
  • What can we learn, or use, from the GPX (XML schema for GPS data) specification?

References

See Also