>> *"For example, use the feature leisure=picnic_site with the property
>> tag drinking_water=yes, instead of using the separate feature tag
>> amenity=drinking_water on the same node or area."
>>
>> This example is a bad idea and mappers shouldn't be encouraged to do
>> so. amenity=drinking_water
On 05/07/19 19:57, Mariusz wrote:
On 05.07.2019 07:05, Joseph Eisenberg wrote:
I've removed this statement from the page because it leads to
ambiguous data and directly contradicts the One feature per one
element rule
[Examples of bad situations:] "An area object representing a
single-use build
On 05.07.19 11:57, Mariusz wrote:
> On 05.07.2019 07:05, Joseph Eisenberg wrote:
>> [Examples of bad situations:] "An area object representing a
>> single-use building with a point object inside it. Move the tags to
>> the area object and delete the point."
>
> This is common and widly accepted pr
On 7/4/2019 11:17 PM, Joseph Eisenberg wrote:
We've also had problems with features tagged "tourism=camp_site" or
"landuse=meadow" plus "barrier=hedge" or "barrier=wall". Is the
barrier supposed to be an area or a linear feature in this case?
I can see the confusion here, but I think this rule s
On 05.07.2019 07:05, Joseph Eisenberg wrote:
I've removed this statement from the page because it leads to
ambiguous data and directly contradicts the One feature per one
element rule
[Examples of bad situations:] "An area object representing a
single-use building with a point object inside it.
I've removed this statement from the page because it leads to
ambiguous data and directly contradicts the One feature per one
element rule
[Examples of bad situations:] "An area object representing a
single-use building with a point object inside it. Move the tags to
the area object and delete the
I agree that this page could be improved. Until now it hasn't
mentioned the problems with tagging multiple features on one database
object.
This can be difficult for database users, for example this comment at
the Openstreetmap-carto github page:
https://github.com/gravitystorm/openstreetmap-carto
On 05/07/19 03:11, marc marc wrote:
Le 04.07.19 à 18:26, Jmapb a écrit :
As far as I know, amenity=school is the *only* accepted landuse-esque
tagging for school grounds.
it's the perfect example of confusion between two different things.
if a school is located on the ground floor of an apartme
On 7/4/2019 1:11 PM, marc marc wrote:
it's the perfect example of confusion between two different things.
if a school is located on the ground floor of an apartment, office,
or commercial building, believing that amenity=school is a landuse
is wrong. in this case amenity=school (as a node or a wa
On 7/4/2019 12:48 PM, Martin Koppenhoefer wrote:
you could also overlap (multipolygons or not) different schools when
they share the indoor space, but if there are distinct names for the
campus and the schools, we would need a tag for the campus which we
don’t have yet, AFAIK
Cheers, Martin
Yea
Le 04.07.19 à 18:26, Jmapb a écrit :
> As far as I know, amenity=school is the *only* accepted landuse-esque
> tagging for school grounds.
it's the perfect example of confusion between two different things.
if a school is located on the ground floor of an apartment, office,
or commercial building,
sent from a phone
> On 4. Jul 2019, at 18:26, Jmapb wrote:
>
> But what I'm faced with very often in NYC is a single campus,
> sometimes with one building and sometimes more, that's shared by several
> schools -- and there's no accurate way to divide up the buildings.
you could also overlap
On 7/4/2019 6:33 AM, Warin wrote:
On 04/07/19 20:09, Janko Mihelić wrote:
I've been tagging it with an empty amenity=school polygon around
everything, and then two points with amenity=school + name=* + all
the other specific tagging.
I too have used similar.
Usually a polygon/way with one scho
On 04/07/19 20:09, Janko Mihelić wrote:
I've been tagging it with an empty amenity=school polygon around
everything, and then two points with amenity=school + name=* + all the
other specific tagging.
I too have used similar.
Usually a polygon/way with one school on it and then a node inside it
I've been tagging it with an empty amenity=school polygon around
everything, and then two points with amenity=school + name=* + all the
other specific tagging. But if mapped like that, a data consumer would see
3 schools. I like your solution with overlapping multipolygons.
Janko
čet, 4. srp 2019
The one feature page states:
More than one of something on the same site e.g. two schools sharing grounds.
Normally if the schools are separate they would have separate neighbouring
grounds, but if the only thing defining a separation between two schools is
their buildings, then the containing a
16 matches
Mail list logo
