<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
It makes perfect sense to me and I totally agree.<br>
But I assume you mean ways in stead of nodes in 'So the route
relations should only contain (a preferably) continuous set of nodes'<br>
<br>
On top of that, I find it handy when the route realations have a name,
so it is easy to see which are the relations of a road.<br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/way/73069100">http://www.openstreetmap.org/browse/way/73069100</a><br>
When they have 2 or 3 meaningful letters in front (followed by a space)
of the numbers, you can also easily see on the hike or bike maps which
network is in place <br>
eg ZD 239-240 = Zuid-Dijleland from node 239 to 240<br>
<a class="moz-txt-link-freetext" href="http://hiking.lonvia.de/?zoom=12&lat=50.779&lon=4.56392">http://hiking.lonvia.de/?zoom=12&lat=50.779&lon=4.56392</a><br>
With only the numbers, <br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/relation/14142">http://www.openstreetmap.org/browse/relation/14142</a><br>
it is truncated and thus cluthering the map.<br>
<a class="moz-txt-link-freetext" href="http://cycling.lonvia.de/?zoom=13&lat=50.78855&lon=4.59216&layers=FFBTT">http://cycling.lonvia.de/?zoom=13&lat=50.78855&lon=4.59216&layers=FFBTT</a><br>
Also when a way is part of more than one network (hike and bike) the
numbers don't tell which is which.<br>
Here a good addition could be DL for Dijleland<br>
Alternative is to provide an osmc tag with the shortened name in it
(probably not working for bike maps).<br>
This tagging info for prper naming should be added to the Wiki<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Walking_Routes#Walking_node_networks">http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Walking_Routes#Walking_node_networks</a><br>
and<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Cycle_Routes#Cycle_Node_Networks">http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Cycle_Routes#Cycle_Node_Networks</a><br>
and maybe also in the general remarks in conventions.<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Walking_Routes">http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Walking_Routes</a><br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Cycle_Routes">http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Cycle_Routes</a><br>
<br>
<br>
Regards,<br>
Gerard.<br>
<br>
<br>
Jo wrote:<br>
<blockquote type="cite"
cite="midCAJ6DwMBW3wn30OfVstM5EY_+8eaBA+0afTky4qqqQpR=F6e=kA@mail.gmail.com">Hi,<br>
<br>
I'm working on the cycle node network in Flanders/Southern Netherlands.<br>
<br>
I created a collection relation:<br>
<br>
<a href="http://www.openstreetmap.org/browse/relation/1726882">http://www.openstreetmap.org/browse/relation/1726882</a><br>
<br>
This should make it a lot more convenient to find all the
nodes/routes/networks involved in the rcn. Fiddling with XAPI and such
is not very productive... It's extremely time consuming and very error
prone.<br>
<br>
Which contains a network relation for each set of numbered nodes (where
each set contains only one time 01,02, etc) (I'm working without the
maps of Toerisme Vlaanderen, so I had to improvise for the naming and
where to make a subdivision)<br>
<br>
For the moment I'm abusing the role to add the node number. This works
easier and is only temporary. I'll take them all out again, when I'm
done inventorizing.<br>
<br>
The network relations contain the route relations. As far as I'm
concerned, the route relations don't need to contain the nodes anymore.
They are part of the ways, anyway. So the route relations should only
contain (a preferably) continuous set of nodes. I try to have them
start at the lower numbered node. If the forward and backward relation
don't follow the same route, I use forward/backward roles. The idea I'm
following is that it should be possible to go from the lower numbered
to the higher numbered node by following all the ways without a role
until ways with forward roles are met. Then all the ways with forward
roles until a way with a backward role is found. Then skip the ways
with backward roles and continue with the ways without a role.<br>
<br>
All this, because I want to be able to 'validate' the routes for
continuity with a script/program and this will probably simplify the
life of the people of Fietsnet as well.<br>
<br>
I'll post an example to illustrate later on.<br>
<br>
Polyglot<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div
style="padding: 0px; visibility: hidden; left: -5000px; position: absolute; z-index: 9999; margin-left: 0px; margin-top: 0px; overflow: hidden; color: black; font-size: 10px; text-align: left; line-height: 130%;"
id="avg_ls_inline_popup"></div>
<pre wrap="">
<hr width="90%" size="4">
_______________________________________________
Talk-be mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/talk-be">http://lists.openstreetmap.org/listinfo/talk-be</a>
</pre>
</blockquote>
</body>
</html>