On 09/15/2017 05:56 PM, Tom Pfeifer wrote:
> I have seen a few mappers recently adding
> contact:[ yelp | tripadvisor | foursquare ]
> to businesses.
>
> IMHO these are not means of contact, instead these are review websites.
> While I personally think that we do not need them in OSM at all, they
On 2017년 09월 16일 00:56, Tom Pfeifer wrote:
I have seen a few mappers recently adding
contact:[ yelp | tripadvisor | foursquare ]
to businesses.
IMHO these are not means of contact, instead these are review websites.
While I personally think that we do not need them in OSM at all, they
On 16-Sep-17 08:56 AM, Tom Pfeifer wrote:
I have seen a few mappers recently adding
contact:[ yelp | tripadvisor | foursquare ]
to businesses.
IMHO these are not means of contact, instead these are review
websites. While I personally think that we do not need them in OSM at
all, they
I have seen a few mappers recently adding
contact:[ yelp | tripadvisor | foursquare ]
to businesses.
IMHO these are not means of contact, instead these are review websites. While I personally think
that we do not need them in OSM at all, they certainly do not belong in the contact:* namespace.
On 2017-09-15 20:34, Viking wrote:
> On the contrary, now I think that we must made explicit all water sources and
> do not use at all waterbody. Stream, river, lake, pond, sea, ocean are clear
> enough to be understood by an occasional mapper and correspond to existing
> tags. Instead, to
> I don't like adding more and more tag
> but IMHO 1 key = 1 function is much simpler.
+1
The volume must be ONLY in water_volume=* and not in implicitly given by
another tag. It must br clear enough to be understood by an occasional mapper.
More complexity is when a piece of information is
