Am 08/ott/2013 um 01:58 schrieb SomeoneElse li...@mail.atownsend.org.uk:
Er, what?
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
+1, that's exactly the reason. A building is not the same feature as the
business occupying it.
cheers,
On Tue, Oct 8, 2013 at 9:38 AM, Martin Koppenhoefer
Er, what?
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
+1, that's exactly the reason. A building is not the same feature as the
business occupying it.
Cool down, Martin. Amenity (or shop or whatever) reusing the building
Le 08/10/2013 10:21, Pieren a écrit :
On Tue, Oct 8, 2013 at 9:38 AM, Martin Koppenhoefer
Er, what?
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
+1, that's exactly the reason. A building is not the same feature as the
business occupying it.
Cool down, Martin. Amenity (or
2013/10/8 Pieren pier...@gmail.com
Cool down, Martin.
I am cooled down ;-)
Amenity (or shop or whatever) reusing the building
polygon is common practice.
yes, it is common practice, and it is a shortcut that works at least as
long as there are only very few attributes, but there are
On Tue, Oct 8, 2013 at 11:30 AM, Martin Koppenhoefer
If you put a tag wikipedia to a building like this, will
it refer to the building or to the amenity?
Yep but ... buildings with dedicated wikipedia articles or names are
the exception. There is also a disadvantage to draw the same polygon
2013/8/23 Vivien Deparday vivien.depar...@gmail.com
Case C:
For building usage,
building=
building:use=
I am not sure what is the best between these two or do they have different
goal/usage? building= seem to be a mix of usage, amenity type, structure
type.
building:use is for the
On 07.10.2013 22:39, Vivien Deparday wrote:
Thank you Tobias (sorry for the late answer), that is very useful
feedback and pretty much exactly in line with our thinking on all the
cases which is great. For B, we are actually also using plaster as one
of the values as the values are recorded by
Am 08/ott/2013 um 00:48 schrieb fly lowfligh...@googlemail.com:
Think your values would fit with
simple operator=* and if you want to separate the operator of the
building from the operator of the amenity I think operator:amenity would
be better
you should not use amenity and building
I don't see the use of multipolygon relations in this manor in the wiki. Nor
have I noticed it in use in the areas that I have edited. Nor do I recall
answers suggesting using multiple multipoloygons on the help site.
Is this a common technique that I have somehow missed?
Thanks!
Tod
--
Sent
Martin Koppenhoefer wrote:
you should not use amenity and building on the same object
Er, what?
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
Cheers,
Andy
___
Hi all,
The OpenDRI project has been doing some work in Nepal and Sri Lanka to
trace building footprints and to enter attribute data about the buildings.
We are looking to get feedback from the tagging and HOT mailing list on the
building presets that we are using and we would like to consolidate
Hello Vivien,
I develop a 3D renderer working with OSM data, so I will look at your
questions based on that background.
Case A: roof:material vs. building:roof
The preferred key from 3D rendering documentation is roof:material
because, as you guessed, it clearly differentiates this attribute
12 matches
Mail list logo
