[Tagging] Data redundancy with "ref" tag on ways vs relations
ppawel at fastmail.fm
Mon Jul 30 17:58:59 BST 2012
I understand what you're saying about ease of use but at the same time I
am very concerned about the quality of data - it is clear from reports
that there are just so many errors that the ref data is virtually
useless for navigation or location purposes.
I feel like there is no clear contract between the data and the
consuming software - some people use "ref" on ways, some people add
relations (this is preferred now as I see from remapping efforts). I see
two ways to "fix" it:
* Invest time in QA - like reporting, auto fixing bots etc. so that the
relations and refs on ways are synced.
* Choose one way (relations is clear "winner" here), invest time into
making consuming software support this way and clearly encourage it.
My feeling is that if there is no encouragement or "blueprint" for
tagging in this area then the data will always be a moving target and we
can endlessly do QA, fix it etc. And since the consuming software moves
slower than data (and maybe even slower than blueprints I guess?), the
data quality and end user experience for navigation, rendering is always
On Mon, Jul 30, 2012, at 18:35, Peter Wendorff wrote:
> Am 30.07.2012 18:22, schrieb Paweł Paprota:
> > Hi all,
> > As part of the Poland remapping effort I have implemented a reporting
> > system called OSMonitor which analyzes road network in Poland in OSM
> > data and produces reports. Recently one user requested additional
> > validation - checking if ways in a relation for a specific road contain
> > proper "ref" tag values (where "proper" means that "ref" on ways
> > includes "ref" from the relation).
> > This is what came out of OSMonitor:
> > https://wiki.openstreetmap.org/w/index.php?title=OSMonitor/Poland_Major_Roads&oldid=791535
> > Note the error named "relation contains ways with wrong ref". So for
> > some roads the ways contain multiple variants of "ref" value. More -
> > "ref" tag for ways is out of sync with relation membership, see
> > http://www.openstreetmap.org/browse/way/172192711 (I am referring to the
> > version 2 of this way in case it has been fixed in the meantime) for
> > example.
> > So the question is - why does "ref" on way level make sense at all when
> > there is another (better and more flexible) way (pun intended) of doing
> > things?
> On the one hand it's easier to add for users than to maintain route
> That in mind "allowing" this as one option enables even beginners to add
> refs, too.
> The other thing is that it's not more difficult to handle refs on single
> ways for software than to pull these from relations as the relations
> often are broken, too, so unconnected routes have to be handled with
> both options - from single ways as well as from relations.
> What makes relations easier to use for data consumers (not mappers) is
> that it's defined which ways belong to the relations and therefore it
> may be easier to "guess" missing links between unconnected parts.
> I think, ref makes sense on both: relations and ways, as this allows
> mappers to easily add a tag where it belongs to, even if it's not
> possible to edit the relation - due to the usage situation online and a
> restricted editor used, due to missing knowledge about route relations
> or whatever.
> On the other hand it allows to find possible errors by checking if
> there's a conflict - like you do now.
> A conflict may be, where a ref is on a way directly and on the relation
> the way belongs to, and these refs mutually exclude each other.
> This isn't always the case: a cycleway-ref may be correct in parallel to
> a county street ref and so on; but sometimes it may in fact be an error,
> and at least it's "not complete" in a sense that on the way a ref might
> be missing, when it's on a relation where the way is a member.
> Tagging mailing list
> Tagging at openstreetmap.org
More information about the Tagging