<div dir="ltr">I'd like to put in a plug here for the route relation, specifically the route=road relation:<div><a href="https://wiki.openstreetmap.org/wiki/Tag:route%3Droad">https://wiki.openstreetmap.org/wiki/Tag:route%3Droad</a><br></div><div><br></div><div>These relations are really useful to data consumers because you're not reliant on getting each and every way in a route tagged exactly right -- you can rely on the route relation as the central source for information on a route and put a ref=*, unsigned_ref=*, networl=*, name=*, etc at that level. The American mapping community is getting very close to solving the long-standing problem of linear highway shield rendering in vector maps. The biggest challenge we have is that concurrent routes (a road is part of more than one route) are very common in the US, and so it's not enough to just draw a single icon on a road -- you need one for each route. Having accurate (and where concurrencies exist, overlapping) route relations with a consistent network/ref scheme gives us a predictable data scheme that a renderer can rely on.</div><div><br></div><div>There is of course nothing wrong with also repeating the multiple refs on each way, and legacy data consumers probably rely on this style of tagging, even though it's technically redundant where a route relation exists.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 5, 2021 at 7:19 AM Mateusz Konieczny via talk <<a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div><br></div><div><br></div><div><br></div><div>Aug 5, 2021, 09:20 by <a href="mailto:colin.smale@xs4all.nl" target="_blank">colin.smale@xs4all.nl</a>:<br></div><blockquote style="border-left:1px solid rgb(147,163,184);padding-left:10px;margin-left:5px"><blockquote><div>On 08/05/2021 5:02 AM stevea <<a href="mailto:steveaosm@softworkers.com" target="_blank">steveaosm@softworkers.com</a>> wrote:<br></div><div><br></div><div> <br></div><div>+1<br></div><div><br></div><div>On Aug 4, 2021, at 5:30 PM, Joseph Eisenberg <<a href="mailto:joseph.eisenberg@gmail.com" target="_blank">joseph.eisenberg@gmail.com</a>> wrote:<br></div><div>> Two of the principles on the "Good Practice" page suggest that the real-world information, as found on signs or other physical evidence, rather than the laws in the register office somewhere, are considered the primary source. This advice has been in the wiki for over 10 years: <a href="https://wiki.openstreetmap.org/wiki/Good_practice." target="_blank">https://wiki.openstreetmap.org/wiki/Good_practice.</a>..<br></div></blockquote><div><br></div><div>"Primary source" is not the same as "sole source." Where sources conflict, we exercise judgement. Which source is most likely to be "correct" in OSM terms?<br></div><div><br></div><div>If you have a road which is signed (for example) "A12" for almost its entire length, but somewhere there is a one-off sign that says "A21", do we tag that bit of road as "A21"? Over what length? Or do we map following our cognitive processes, and assume that the sign is erroneous?<br></div><div><br></div><div>If you have a road that in fact used to be the B2009 but was declassified years ago, but somewhere along its length there is a rusty fingerpost in the hedge that has the old number on it, does that road magically regain its number from 30 years ago?<br></div><div><br></div><div>If we are not going to let many decades of data modelling experience get in the way of our tagging schema, we accept that there is only one "ref" for a road.<br></div></blockquote><div dir="auto">In general I agree with your message (ground truth is true, but using brain to discard obviously<br></div><div dir="auto">invalid signs is needed).<br></div><div dir="auto"><br></div><div dir="auto">But road can have multiple refs at once, see ref=A4;7 at<br></div><div dir="auto"><a href="https://www.openstreetmap.org/?mlat=50.0818&mlon=19.8083#map=15/50.0818/19.8083&layers=N" target="_blank">https://www.openstreetmap.org/?mlat=50.0818&mlon=19.8083#map=15/50.0818/19.8083</a> <br></div><div dir="auto"><br></div> </div>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>
</blockquote></div>