[Tagging] Proposed features - Voting - Pressurized waterways
Janko Mihelić
janjko at gmail.com
Tue Jan 23 17:30:16 UTC 2018
uto, 23. sij 2018. u 16:16 François Lacombe <fl.infosreseaux at gmail.com>
napisao je:
>
> To get the whole hydrographic system, users have to query waterway,
> pipeline and some other keys not all related to water.
> If all water paths would have only waterway=*, this would be simpler and
> sustainable.
> Would you be happy if I remove highway=* from tunnels or bridges just
> because it's not "natural" roads?
>
> Not to mention standard osm render doesn't currently render pipelines.
> Introducing a new value of waterway, already imported in mapnik schema may
> be simpler than adding pipeline and some extra keys.
>
Calling pipelines waterway=pressurized because it would be easier for you
to extract it and render it makes this tagging for the renderer. Tags
should be as consistent as possible for the mappers, not data consumers. If
a mapper sees a pipeline, and you tell him "tag that as
waterway=pressurized because then my SQL query can be nice and short" the
mapper is going to get annoyed and quit. If it's a pipeline, tag it as a
man_made=pipeline, and that's it. Somebody else can tag the type of a
pipeline, but nobody is suposed to think about SQL queries when mapping.
Janko Mihelić
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20180123/5f724148/attachment.html>
More information about the Tagging
mailing list