I want to raise attention to this page:
http://wiki.openstreetmap.org/wiki/Proposed_features/Building_attributes
which most of you certainly are aware of. This page is pretending to
be a proposal page, but actually has become mostly a documentation
page for several application programmers to
2012/2/8 SomeoneElse li...@mail.atownsend.org.uk:
Volker Schmidt wrote:
How do I tag a Site of Community Importance (see
http://en.wikipedia.org/wiki/Site_of_Community_Importance)?
A few people have gone for:
On 08/02/2012 13:40, Martin Koppenhoefer wrote:
6. building:levelPlan=* What each storey is used for, Examples: 0-2:
shop, 3-12: residential; 0: restaurant, 1: residential; -1: unused, 0:
lobby, 1: restuarant, 2-12: offices, 13: unused, 14-66: offices
- missleading key (one would expect a link
Am 08.02.2012 um 15:38 schrieb Colin Smale colin.sm...@xs4all.nl:
On 08/02/2012 13:40, Martin Koppenhoefer wrote:
6. building:levelPlan=*What each storey is used for, Examples: 0-2:
shop, 3-12: residential; 0: restaurant, 1: residential; -1: unused, 0:
lobby, 1: restuarant, 2-12:
What you describe is proposed here:
http://wiki.openstreetmap.org/wiki/Proposed_features/lanes_General_Extension
Martin
Am 08.02.2012 um 15:38 schrieb Colin Smale colin.sm...@xs4all.nl:
On 08/02/2012 13:40, Martin Koppenhoefer wrote:
6. building:levelPlan=*What each storey is used for,
I suggest putting the lanes qualifier in front,
allowing arbitrary tag hierarchies to follow at a fixed location.
This was suggested, but dropped for better readability: see Default
values; minimise ambiguity on the Discussion page.
You introduce a new tag applies_to to limit the lane to a
Am 08/feb/2012 um 17:03 schrieb John Sturdy jcg.stu...@gmail.com:
On Wed, Feb 8, 2012 at 12:40 PM, Martin Koppenhoefer
dieterdre...@gmail.com wrote:
5. building:min_level=* Number of stories between ground and actual
first existing floor
- I'd completely discourage usage of this key,
A 'site of special scientific interest' is different to a 'site of
community importance', at least in the UK. A 'site of community importance'
appears to be a way for the EU to notify a member countries that a piece of
land should be designated a SAC.
There doesn't appear to be an agreed way to
4. building:levels=*Number of stories of the building above ground.
- why only above ground? I find this missleading as well. The logical
meaning of a tag building:levels would be the total amount of
building levels. If it is for the levels above ground, why not
building:levels:above_ground
2012/2/8 Kytömaa Lauri lauri.kyto...@aalto.fi:
IMO this is a make mapping easy choise (vs. code requires sticking
to definitions, even if it is against day to day speak): you can get a
random mapper to count the windows and have them enter that.
If one
asks people if a building is a, say,
2012/2/8 Colin Smale colin.sm...@xs4all.nl:
On 08/02/2012 16:00, Martin Vonwald wrote:
question of syntax rather than concept. What triggered my post was actually
a comment by Martin K who also felt a need for multi-value tags (i.e.
arrays) in the context of the floors within a building.
I
2012/2/8 Martin Vonwald imagic@gmail.com:
That is a very bad idea. Splitting the way would mean, that there is
no possiblity to switch between the lanes (as they are separated),
which in reality often is not correct. This would also break routing.
you could have a relation to say that
On 2/8/2012 2:25 PM, Martin Koppenhoefer wrote:
The lane-case is a little different though, because if you have
multiple values there (plus a definition from where to start) you
won't need lane numbering. For buildings you will have unambigous
numbers for the floors anyway, and they are the
Am 08.02.2012 um 18:48 schrieb Colin Smale colin.sm...@xs4all.nl:
On 08/02/2012 17:52, Martin Vonwald wrote:
I suggest putting the lanes qualifier in front,
allowing arbitrary tag hierarchies to follow at a fixed location.
This was suggested, but dropped for better readability: see Default
Colons in keys are likely to make many casual mappers uneasy about
editing said tag, let alone two of them in one key.
Casual mappers seem an unlikely target for this particular type of highly
technical mapping.
That said:
The 3D mapping by tags is interesting. But another
Am 08.02.2012 um 20:38 schrieb Martin Koppenhoefer dieterdre...@gmail.com:
you could have a relation to say that there is a linear possibility to
switch between the lanes (proposed area relation). This would make
some things much easier (we could use standard tags on the ways and it
would be
On 08/02/2012 20:25, Martin Koppenhoefer wrote:
2012/2/8 Colin Smalecolin.sm...@xs4all.nl:
On 08/02/2012 16:00, Martin Vonwald wrote:
question of syntax rather than concept. What triggered my post was actually
a comment by Martin K who also felt a need for multi-value tags (i.e.
arrays) in the
On 08/02/2012 21:03, Nathan Edgars II wrote:
On 2/8/2012 2:25 PM, Martin Koppenhoefer wrote:
The lane-case is a little different though, because if you have
multiple values there (plus a definition from where to start) you
won't need lane numbering. For buildings you will have unambigous
On 2/8/2012 3:14 PM, Bryce2 Nesbitt wrote:
Colons in keys are likely to make many casual mappers uneasy about
editing said tag, let alone two of them in one key.
Casual mappers seem an unlikely target for this particular type of
highly technical mapping.
Adding the number of
On 2/8/2012 3:47 PM, Colin Smale wrote:
For building floors, are there any cultures which number their floors
downwards?
The Troglodytes.
There is of course the common leaving off of the 13th floor.
___
Tagging mailing list
On 08/02/2012 22:00, Nathan Edgars II wrote:
On 2/8/2012 3:47 PM, Colin Smale wrote:
For building floors, are there any cultures which number their floors
downwards?
The Troglodytes.
:-D
There is of course the common leaving off of the 13th floor.
Mentioned that a couple of posts ago:
21 matches
Mail list logo
