30 Apr 2019, 13:51 by [email protected]: > > > On Tue, 30 Apr 2019 at 05:40, Joseph Eisenberg <> [email protected] > <mailto:[email protected]>> > wrote: > >> On 4/30/19, Mateusz Konieczny <>> [email protected] >> <mailto:[email protected]>>> > wrote: >> > 29 Apr 2019, 23:11 by >> [email protected] <mailto:[email protected]>>> >> : >> > >> >> Since healthcare=* is now rendered by standard carto, there's no reason >> to >> >> include amenity=*. >> >> >> > Please, avoid basing tagging decision on one specific renderer. >> > >> >> (Also, that information is no longer correct: >> >> https://github.com/gravitystorm/openstreetmap-carto/pull/3731 >> <https://github.com/gravitystorm/openstreetmap-carto/pull/3731> >> Due to: >> >> https://github.com/gravitystorm/openstreetmap-carto/issues/3639 >> <https://github.com/gravitystorm/openstreetmap-carto/issues/3639> >> Sorry.) >> > > Hmmmmmmm. I actually checked that healthcare=* rendered by finding an example > without a corresponding amenity tag. So I'm now confused (which is fairly > normal for > me). > It is rendered in a currently used version, version that is not yet used on OSM servers will include #3731 that drops this rendering. > I'm also puzzled as to why (if I understand the issue correctly) you'd stop > healthcare=* > rendering for anything just because it fails to render on polygons without an > area=yes. > See explanation in https://github.com/gravitystorm/openstreetmap-carto/pull/3731 <https://github.com/gravitystorm/openstreetmap-carto/pull/3731> > This provides inconsistent mapper feedback, suggesting that features need to > be > double-tagged with "amenity" or mapped as a node
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
