[Openstreetmap-dev] REST

[Stefan Holst]

hi,

this is my first post here - please be gentle ;)
i live in Sindelfingen near Stuttgart, Germany and began mapping
a few weeks ago using my bike, a gpsr, an old palm, ruby scripts
to compile shapefiles out of the collected data and a local
mapserver/ka-map installation for viewing.

i'm currently using my own xml-format but i'll convert to gpx
to upload the data to osm asap :)

so i was thinking about a proper gpx-extension for the metadata
i collected. this metadata includes:

- estimated position error and elevation error for each trackpoint
- name of the street (if known)
- surface (asphalt, dirtroad, gravel, ...)
- roadtype (mainroad, sideroad, farmway, footpath ...)
- hiking and biking guides along current road

so here are my thoughts...

Nick Whitelegg wrote:
> <trkseg>
> <trkpt....>
> 
> track points...
> 
> </trkpt>
> <extensions>
> <type>road</type>
> <name>Church Road</name>
> </extensions>
> </trkseg>

it would be nice to have this extension also defined for whole tracks.
values assigned to a track are valid for each segment unless they're
overwritten. this should save some space for roads with many segments.
(given that roads are saved as distinct tracks.)

what about locatized names? at least some points of interest have
several names in different languages

<name:de>Kurmärker Kaserne</name:de>
<name:en>Patch Barracks</name:en>

and most streets in belgium have two names. i'd vote also for something
like:

<surface>asphalt</surface>
<hikingtour>bluecross</hikingtour>
<cyclingtour>de.bw.radelrund</cyclingtour>

> but this could be revised in a way appropriate to the key value system e.g.
> something like the following to indicate that a segment has a name of
> Church Road and is accessible to car, horse, foot, bike:
> 
> <extensions>
> <permissions car="1" horse="1" foot="1" bike="1"/>
> <name>Chuch Road</name>
> </extensions>

in germany, there are also streets where the drive-through is not
allowed. you may only use these if you visit someone (Anlieger frei).
from a biker's perspective, it would be nice to indicate if there's
a seperate bikepath along a road or not.

junctions should also be modelled. this is necessary for routing
and practical for the survey. in gpx, they are simple waypoints
with apropriate extensions. but to refer to streets, they have
to have unique ids.

to ensure this uniqueness, the ids must have a hierachical structure.
starting with the tld of the country, followed by federal states and
districts (specific to each nation, i suppose) and suffixed by
the simplyfied name of the feature. this name should only contain
lowercase letters and numbers (no spaces) in the case the id is used
as a filename.

a concluding example:

<gpx version="1.1">
   <metadata>
     <name>two_streets</name>
     <copyright author="Stefan Holst">
       <year>2005</year>
       <license>http://creativecommons.org/licenses/by-sa/2.5/</license>
     </copyright>
   </metadata>
   <wpt lat="48.734" lon="9.012">
     <ele>513.0</ele>
     <time>2005-03-26T16:53:21Z</time>
     <type>junction</type>
     <extensions>
       <epe>6.0</epe>
       <eee>11.0</eee>
       <street>de.bw.bb.sindelfingen.pfarrwiesenallee</street>
       <street>de.bw.bb.sindelfingen.leonbergerstr</street>
       <trafficlights>yes</trafficlights>
     </extensions>
   </wpt>
   <trk>
     <name>de.bw.bb.sindelfingen.pfarrwiesenallee</name>
     <type>mainroad</type>
     <extensions>
       <name:de>Pfarrwiesenallee</name:de>
       <bikepath>yes</bikepath>
     </extensions>
     <trkseg>
       ...
     </trkseg>
     ...
   </trk>
   ...
</gpx>


RY
Stefan