<div dir="ltr"><div><br></div>Just thought of this: since a node can belong to multiple networks (cycling, walking, equestrian), we need a tagging scheme for the network name that takes this into account.<div>So something like : network:rcn:name, network:rwn:name and network:ren:name </div>
<div><br></div><div>rcn= regional cycling network</div><div>rwn= regional walking network</div><div>ren=regional equestrian network (?)</div><div><br></div><div>both rcn and rwn are already used in the numbering of the nodes (rwn_ref, rcn_ref). I'm not familiar with the equestrian networks</div>
<div><br></div><div>Another problem is for routes that form the connection between 2 networks. Right now, they are placed in the 2 network relations. How would you tag the network names for them ?</div><div><br></div><div>
<br></div><div>regards</div><div><br></div><div>m</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 11:07 AM, Marc Gemis <span dir="ltr"><<a href="mailto:marc.gemis@gmail.com" target="_blank">marc.gemis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">When the name, operator,etc. has to be moved down to the routes and nodes, we have prefix all those tags with e.g. network.<br>
<div>So we get network:name, network:operator on each node and route, right ?</div>
<div><br></div><div>Please note the network relations are not used to group all routes and nodes in a country or province. When you are interested in the nodes & routes of 1 network you can only do this via the name of the network.</div>
<div>So a spatial query won't help much in that case, although I admit that it might not be interesting to limit the query to a specific network and not to a geographical region.</div><div><br></div><div>BTW, I wouldn't mind to start using a tagging schema that doesn't use network relations.</div>
<div><br></div><div>regards</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>m</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 10:36 AM, Pieren <span dir="ltr"><<a href="mailto:pieren3@gmail.com" target="_blank">pieren3@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jul 16, 2014 at 8:17 AM, Jo <<a href="mailto:winfixit@gmail.com" target="_blank">winfixit@gmail.com</a>> wrote:<br>
> The same is true for cycling and equestrian networks with numbered nodes.<br>
> There are a few of those networks in Germany as well.<br>
> These are not collections/categories. They are networks of route relations.<br>
<br>
Well, you could do the same for all McDonald's restaurants in<br>
Netherlands or all pharmacies in a network or bank branches in Belgium<br>
and say "we move one tag to the upper relation to avoid its<br>
repetition". What is done by such relations can be done by a query in<br>
the database with one or two arguments (like the "operator" or<br>
"network" tag) and a bbox (see XAPI, overpass, etc for more info).<br>
Repeating the network or operator or brand name is not a problem for<br>
many features in OSM. I don't see why we should create an exception<br>
for footway routes.<br>
As it was writen by Frederik Ramm in 2008 ([1]):<br>
"Our database is a spatial database; this means that it has intrinsic<br>
knowledge about the location of objects. If you want to know about all<br>
footways in East Anglia, simply pass in a bounding box of East Anglia<br>
and request all footways, and the collection is made for you<br>
on-the-fly."<br>
<br>
Pieren<br>
<br>
[1] <a href="http://wiki.openstreetmap.org/w/index.php?title=Relations/Relations_are_not_Categories&oldid=179750" target="_blank">http://wiki.openstreetmap.org/w/index.php?title=Relations/Relations_are_not_Categories&oldid=179750</a><br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>