Alternative is in stead of a route to use track
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1";
<http://www.topografix.com/GPX/1/1> creator="OSM Route Manager"
version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation="http://www.topografix.com/GPX/1/1
http://www.topografix.com/GPX/1/1/gpx.xsd";
<http://www.topografix.com/GPX/1/1http://www.topografix.com/GPX/1/1/gpx.xsd>>
<!-- All data by OpenStreetMap, licensed under cc-by-sa-2.0
(http://creativecommons.org/licenses/by-sa/2.0/). -->
<wpt lat="50.788708" lon="4.5839511">
<name>301</name>
</wpt>
<wpt lat="50.788718" lon="4.5839521">
<name>302</name>
</wpt>
<trk>
<name>Dijleland 301-302</name>
<src>OpenStreetMap.org</src>
<type>foot</type>
<trkseg>
<trkpt lat="50.788708" lon="4.5839511" > </trkpt>
<trkpt lat="50.788709" lon="4.5839515" > </trkpt>
</trkseg>
<trkseg>
<trkpt lat="50.788709" lon="4.5839515" > </trkpt>
<trkpt lat="50.788718" lon="4.5839521" > </trkpt>
</trkseg>
<trk>
<trk>
<name>Dijleland 302-303</name>
<src>OpenStreetMap.org</src>
<type>foot</type>
<trkseg>
<trkpt lat="50.788718" lon="4.5839521" > </trkpt>
<trkpt lat="50.788719" lon="4.5839525" > </trkpt>
<trkpt lat="50.788728" lon="4.5839531" > </trkpt>
</trkseg>
</trk>
</gpx>
Advantage is the track segment trkseg element that matches the ways in
the sub relations.
(and no need to filter out double nodes from start and end of these ways)
Regards,
Gerard.
Jo wrote:
That doesn't look too complicated, I'll look into it, tomorrow.
Jo
2011/8/2 Gerard Vanderveken <g...@ghia.eu <mailto:g...@ghia.eu>>
As a minimum you require an output file dijleland.gpx like this
example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1";
<http://www.topografix.com/GPX/1/1> creator="OSM Route Manager"
version="1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation="http://www.topografix.com/GPX/1/1
http://www.topografix.com/GPX/1/1/gpx.xsd";
<http://www.topografix.com/GPX/1/1http://www.topografix.com/GPX/1/1/gpx.xsd>>
<!-- All data by OpenStreetMap, licensed under cc-by-sa-2.0
(http://creativecommons.org/licenses/by-sa/2.0/). -->
<wpt lat="50.788708" lon="4.5839511">
<name>301</name>
</wpt>
<wpt lat="50.788718" lon="4.5839521">
<name>302</name>
</wpt>
<rte>
<name>Dijleland 301-302</name>
<src>OpenStreetMap.org</src>
<type>foot</type>
<rtept lat="50.788708" lon="4.5839511" > </rtept>
<rtept lat="50.788709" lon="4.5839515" > </rtept>
<rtept lat="50.788718" lon="4.5839521" > </rtept>
</rte>
<rte>
<name>Dijleland 302-303</name>
<src>OpenStreetMap.org</src>
<type>foot</type>
<rtept lat="50.788718" lon="4.5839521" > </rtept>
<rtept lat="50.788719" lon="4.5839525" > </rtept>
<rtept lat="50.788728" lon="4.5839531" > </rtept>
</rte>
</gpx>
For every node there is a waypoint element wpt with the
coordinates and as name its ref number
For every sub relation there is a route element rte
It contains route points rtept.
These rtept are all the nodes of the ways from the subrelation.
The streets and their nodes need to be ordered from start to end
node (the ones with the ref tag)
Regards,
Gerard
Jo wrote:
Gerard,
If you provide me with a detailed example of what data in the osm
file, needs to become which information in the gpx, I might try
to program this in Python. It's possible to add python scripts to
JOSM.
Jo (Polyglot)
2011/8/2 Gerard Vanderveken <g...@ghia.eu <mailto:g...@ghia.eu>>
It is not an obligation to have this 'not yet official'
collection relation.
I got the idea by looking at some Alp paths, where it was
used to link all paths of the network.
Everyone can add to the Wiki (registration and login required).
But if you feel uncomfortable doing edits in a Wiki , I can
do it for you, if you send me the relevant data.
The relation has to be created first, so the reference can be
put in the Wiki
For the creation of this specialised GPX, the exporting
functions of OSM are not suitabe.
There is some programming or script required to put each sub
relation into a route and convert the nodes to waypoints.
Regards,
Gerard.
network (as far as they exist).
Should such a collection be created for all other
knooppunten networks ?
If so, can someone update the wiki page to reflect this,
so I can properly create and tag that collection for
Rivierenland
I downloaded the gpx file from Zuid-Dijleland. I was
hoping to get the collection of knooppunten as waypoints.
The result was disappointing (import in Garmin RoadTrip).
Too many routes, even non-existing, waypoints without the
number of the knooppunt.
Is there a better way to retrieve the information as GPX
? I would already be happy with the knooppunten alone,
without the routes between them.
I've tried exporting them from JOSM, but this also looses
the number (which only exists as rwn_ref).
Marc
------------------------------------------------------------------------
_______________________________________________
Talk-be mailing list
Talk-be@openstreetmap.org <mailto:Talk-be@openstreetmap.org>
http://lists.openstreetmap.org/listinfo/talk-be
_______________________________________________
Talk-be mailing list
Talk-be@openstreetmap.org <mailto:Talk-be@openstreetmap.org>
http://lists.openstreetmap.org/listinfo/talk-be
------------------------------------------------------------------------
_______________________________________________ Talk-be mailing
list Talk-be@openstreetmap.org <mailto:Talk-be@openstreetmap.org>
http://lists.openstreetmap.org/listinfo/talk-be
_______________________________________________
Talk-be mailing list
Talk-be@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-be
