<div dir="ltr"><div><div><div><div><div>Hi Per Eric,<br><br></div>What you are looking for is definitely on the wiki side.<br><br></div>The information isn't available as described for now but it would be interesting to document tags like this.<br></div>And a new application/projet might not be necessary if wiki can support it.<br><br><br></div>That question was rose a few times ago.<br><br></div>All the best<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><b>François Lacombe</b><br><br>fl dot infosreseaux At gmail dot com<br><a href="http://www.infos-reseaux.com" target="_blank">www.infos-reseaux.com</a><br><a href="http://www.twitter.com/InfosReseaux" target="_blank">@InfosReseaux</a></div></div></div>
<br><div class="gmail_quote">2016-11-17 11:51 GMT+01:00 Per Eric Rosén <span dir="ltr"><<a href="mailto:per@rosnix.net" target="_blank">per@rosnix.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
I have been making a few maps and applications using OSM data, mostly stored in postgis. In all cases, I have had to make custom carto rules /<br>
database post-processing / application rules to compensate for multiple<br>
ways of expressing the same information in OSM. Also, in some cases,<br>
for taking care of which tag implies which information.<br>
<br>
Is there some way of doing this just once; for example with some parseable implication database, and library? There is some "implies" on the wiki; but it's not completely chine-readable in a reliable way.<br>
<br>
Such a database would probably also need being optionally keyed on country, "highway=cycleway" may imply different rules in different countries for example.<br>
<br>
Would such a tool/database be useful, if not existing already?<br>
<br>
I see two somewhat different usage cases, and I don't know if the same tool/database should be used for both:<br>
<br>
1. normalizing a database before usage, for example changing<br>
"highway=ford" to "ford=yes" and moving to modern lifecycle tags<br>
<br>
(it could be argued that this shoud be done on the main OSM database<br>
by a bot, but data consumers could probably have larger or more<br>
specific needs of normalization compared to what can be agreed to do<br>
by changing the master OSM data)<br>
<br>
2. getting specific implications without writing it to a database, for<br>
example highway=cycleway implies bicycle=yes, foot=yes in country X<br>
<br>
best regards<span class="HOEnZb"><font color="#888888"><br>
Per Eric Rosén<br>
--<br>
^): Per Eric Rosén <a href="http://rosnix.net/~per/" rel="noreferrer" target="_blank">http://rosnix.net/~per/</a><br>
/ <a href="mailto:per@rosnix.net" target="_blank">per@rosnix.net</a> GPG 7A7A BD68 ADC0 01E1 F560 79FD 33D1 1EC3 1EBB 7311</font></span><br>______________________________<wbr>_________________<br>
dev mailing list<br>
<a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/dev" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/dev</a><br>
<br></blockquote></div><br></div>