Difference between revisions of "geo-extension-waypoints"

From Microformats Wiki
Jump to navigation Jump to search
(References - DCMI Box Encoding Scheme)
(more on terms)
Line 1: Line 1:
 
= Geo Waypoint Trails =
 
= Geo Waypoint Trails =
An exploration of publishing trail or boundary information using series of Geo data waypoints.
 
  
[http://en.wikipedia.org/wiki/Waypoint Waypoints] are geographic points, as currently published using the [[geo]] microformat.
+
An exploration of publishing information about sequences of geographical points using series of Geo (or other) microformats.
  
Presented sequentially, they can describe trails or routes (which may or may not have been traversed at specific times) or boundaries (which may be on any scale, from a small garden to a continent).
+
==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 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 (or box). 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 ==
Line 64: Line 69:
  
 
==Issues==
 
==Issues==
*How to differentiate between a trail (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 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 sequence/ timestamp waypoints
+
*How to sequence/ timestamp tracks and routes
**Perhaps using [[hatom|hAtom]] and/ or [[hcalendar|hCalendar]]?
+
**Perhaps using order in source code, ordered lists, [[hatom|hAtom]], and/ or [[hcalendar|hCalendar]]?
  
 
==References==
 
==References==

Revision as of 11:06, 11 June 2007

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 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 (or box). 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>

Typical mandatory attributes

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

Typical optional attributes

  • elevation
  • image
  • note ?
  • url ?

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 sequence/ timestamp tracks and routes
    • Perhaps using order in source code, ordered lists, hAtom, and/ or hCalendar?

References

See Also