Level should be the layers relative to the (lowest) ground, regardless of
how that's defined in the building, for consistency sake. As often as not
here, 1 is either the second floor off the ground or the ground floor, with
G being Ground. Granted, this gets a little tricker, with complex
-- Original message --From: ba...@ursamundi.orgSent: 26/05/2015 12:07To: tagging@openstreetmap.orgSubject: Re: [Tagging] Wiki: Key:level: proposed rewriteLevel should be the layers relative to the (lowest) ground, regardless of how thats defined in the building, for consistency sake. As often
Did you forget to add any comments?
On May 26, 2015 6:58:49 AM wp4...@gmail.com wrote:
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
___
Tagging
2015-05-25 9:25 GMT+02:00 Michael Reichert naka...@gmx.net:
Any objection if I 'rewrite http://wiki.openstreetmap.org/wiki/Key:level
?
It seems to have been written with the misconception that floor names are
numbers when they're not.
A rewrite:
- Won't affect existing names
Hi,
Am 2015-05-25 um 01:41 schrieb pmailkeey .:
Any objection if I 'rewrite http://wiki.openstreetmap.org/wiki/Key:level ?
It seems to have been written with the misconception that floor names are
numbers when they're not.
A rewrite:
- Won't affect existing names that appear as
No.
If you were to do that you would need a scheme that defines the sequence.
If you work with floor names, you need to define a table that assigns
levels to names as well.
The approach to count is correct and the base shold be that ground level is
level 0.
On 25 May 2015 at 01:41, pmailkeey .
The floor level *order* will be clear from the ele(vation) tag, won't it.
Hence no need for a new tag of level_name.
--
Mike.
@millomweb https://sites.google.com/site/millomweb/index/introduction -
For all your info on Millom and South Copeland
via *the area's premier website - *
*currently
On 25/05/2015, Michael Reichert naka...@gmx.net wrote:
I oppose. Numeric level values can be used to display a building plan
layer by layer where higher floors lay over lower floors. Most software
which uses level=* at the moment expects that it is a numeric value.
Example:
On 25/05/2015, pmailkeey . pmailk...@googlemail.com wrote:
The floor level *order* will be clear from the ele(vation) tag, won't it.
No.
Since when has the ele=* tag been used for floors in a building?
___
Tagging mailing list
Using level = number would also mean you'd lose relative floor height
information:
Lifts (Elevators)
Highest floor available
Red Sky Lift – floor numbers correspond to the Main Building.
7
Blue Sky Lift – floor numbers correspond to the South Wing
10 or 11
North Wing
10
In the above
On 25 May 2015 at 13:55, moltonel 3x Combo molto...@gmail.com wrote:
On 25/05/2015, Michael Reichert naka...@gmx.net wrote:
I oppose. Numeric level values can be used to display a building plan
layer by layer where higher floors lay over lower floors. Most software
which uses level=* at
On 25 May 2015 at 14:08, Andrew Errington erringt...@gmail.com wrote:
On 25/05/2015, pmailkeey . pmailk...@googlemail.com wrote:
The floor level *order* will be clear from the ele(vation) tag, won't it.
No.
Since when has the ele=* tag been used for floors in a building?
What other tag
elevation tag is not a good solution, as it requires a measurement that in
most cases is difficult to obtain
On 25 May 2015 at 14:49, pmailkeey . pmailk...@googlemail.com wrote:
The floor level *order* will be clear from the ele(vation) tag, won't it.
Hence no need for a new tag of level_name.
On 25/05/2015, pmailkeey . pmailk...@googlemail.com wrote:
There are two distinct needs : enabling software to sort levels
for rendering and navigation purposes, and the need to show the
textual name that humans expect. The level=* key is currently used
for the fist case (otherwise you'd see
On 25/05/2015, pmailkeey . pmailk...@googlemail.com wrote:
Also knowing the street elevation would give the clue as to which floor was
'ground level' - as would a highway linking internal routes to external.
You shouldn't focus on trying to determine the ground level, as
there are many many
The level key is intended for OSM internal use, to tell routing and
rendering software what connects to what. For indoor mapping, it would make
sense to also have a way to name floors, which needs to allow for both
numeric and non-numeric floor names. I have been in buildings that have
more
2015-05-25 16:44 GMT+02:00 Colin Smale colin.sm...@xs4all.nl:
The ele tag specifically refers to the height above sea level. What we
would want here is a height above ambient ground level. Overloading ele
in this way would lead to untold confusion and be a recipe for disaster.
yes
The ele tag specifically refers to the height above sea level. What we
would want here is a height above ambient ground level. Overloading
ele in this way would lead to untold confusion and be a recipe for
disaster.
//colin
On 2015-05-25 15:29, pmailkeey . wrote:
On 25 May 2015 at 14:08,
On 25 May 2015 at 15:44, Colin Smale colin.sm...@xs4all.nl wrote:
The ele tag specifically refers to the height above sea level. What we
would want here is a height above ambient ground level. Overloading ele
in this way would lead to untold confusion and be a recipe for disaster.
//colin
On 5/25/15 1:20 PM, John Eldredge wrote:
The level key is intended for OSM internal use, to tell routing and
rendering software what connects to what. For indoor mapping, it would
make sense to also have a way to name floors, which needs to allow for
both numeric and non-numeric floor names. I
The ele tag is for indicating the elevation of an object above sea level.
Not many people will know the elevation of each of a building's floors
above sea level.
On May 25, 2015 8:30:26 AM pmailkeey . pmailk...@googlemail.com wrote:
On 25 May 2015 at 14:08, Andrew Errington
Yes, I object. The purpose of the level tag is to tell routing and
rendering software what the vertical order of objects is. It indicates
what connects to what, and, if they don't connect, what renders above what.
It is not intended to hold floor names.
On May 24, 2015 6:42:03 PM pmailkeey
I, too, object. level=* is meant to be the numeric stacking order of
floors/levels in a building.
One redundant tag to level=* is addr:floor=*. This tag currently has the
same definition as level=* (with the same numbering convention). I propose
that we use addr:floor=* instead for your string
So if I'm right, it's 1 for changing the wiki page, and 12 (including me)
opposed.
Janko
pon, 25. svi 2015. 20:10 John Eldredge j...@jfeldredge.com je napisao:
The ele tag is for indicating the elevation of an object above sea
level. Not many people will know the elevation of each of a
Any objection if I 'rewrite http://wiki.openstreetmap.org/wiki/Key:level ?
It seems to have been written with the misconception that floor names are
numbers when they're not.
A rewrite:
- Won't affect existing names that appear as numbers.
- Will encourage mappers to use correct names for
Yes, I object.
level=* is an internal value. Its meaning is absolute, which is
necessary because it is used worldwide.
When the value is displayed, the displaying software should localise the
result according to either the viewer's language, or viewer's location.
Perhaps you are not aware that
I believe that level=* is not intended for direction finding but for 3D
rendering. So, yes, it is an “internal value” which needs to be uniform through
out the world. And for building rendering numerical values make much more sense
than text. Pretty much like lanes=* or width=* need to be
On 25/05/2015 1:18 PM, Andrew Errington wrote:
It's highly likely that the street level floor would be named 'Ground' - so
if software needs to know this, that would be a good starting point. It
could also be worked out by which highway meets the street.
That's funny. In your previous example
It's highly likely that the street level floor would be named 'Ground' - so
if software needs to know this, that would be a good starting point. It
could also be worked out by which highway meets the street.
That's funny. In your previous example no floor is named 'Ground'.
On 25 May 2015 at 01:52, Andrew Errington erringt...@gmail.com wrote:
Yes, I object.
level=* is an internal value. Its meaning is absolute, which is
necessary because it is used worldwide.
When the value is displayed, the displaying software should localise the
result according to
On 25/05/2015 10:52 AM, Andrew Errington wrote:
Yes, I object.
level=* is an internal value. Its meaning is absolute, which is
necessary because it is used worldwide.
When the value is displayed, the displaying software should localise
the result according to either the viewer's language,
On 25 May 2015 at 03:53, Warin 61sundow...@gmail.com wrote:
A person seeking something on level henry will not recognise OSM level
numbers ... they want the name..
If OSM does not use names, but they are used within the wanted building
.. then there will need to be a declared relationship
32 matches
Mail list logo
