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 uniformly defined 
numeric values for the whole world.

If a text value is needed, it is a lot easier to regionally map a uniform 
numeric value into a text string than taking any number of regional text 
strings and mapping them into a number for rendering building height.

Cheers,
Tod


> On May 24, 2015, at 8:05 PM, pmailkeey . <pmailk...@googlemail.com> wrote:
> 
> 
> 
> On 25 May 2015 at 03:53, Warin <61sundow...@gmail.com 
> <mailto: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 between the two. 
> So there needs to be a relation between the names used locally to the OSM 
> level=number ?
> 
> If OSM uses names then OSM will need a relationship between the names and 
> which one is 'ground' and there respective order. 
> 
> 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. 
> 
> Why would floor order be specifically required within OSM other than where 
> they are related (e.g. stairs)? Why numerify a labelling system ?
> 
> Floor 'numbers' have been obviously used for the convenience of the numerical 
> symbols (like street address numbers - yet not all properties have a number 
> some are named). Some floor labelling schemes are by colour code - and I've 
> even come across animals used to identify a particular floor! (We parked on 
> elephant level).
> 
> 
> So? A new tag to relate one to the other?
> level:name=1:henry      ? 
> the wiki http://wiki.openstreetmap.org/wiki/Key:level#String_values 
> <http://wiki.openstreetmap.org/wiki/Key:level#String_values> has a mention of 
> string values .. but NO real way of adding them in a usefull way.. 
> nor is there any indication of how to use these tag on a map... as in 
> rendering. 
> For the given example above the indoor map should display the level name .. 
> not the number .. 
> And this could be used where the level numbering is not that used by OSM .. 
> but using the level:name=0:1 could correctly display the correct local number 
> wile retaining the OSM level system. 
> 
> 
> 
> 
> Indoor .. a GPS will not be of much use .. so the 'indoor map' will need to 
> be a good representation of what goes on. 
> 
> 
> 
> 
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org <mailto:Tagging@openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/tagging 
> <https://lists.openstreetmap.org/listinfo/tagging>
> 
> 
> 
> 
> -- 
> 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 unavailable due to ongoing harassment of me, my family, property & 
> pets
> 
> T&Cs 
> <https://sites.google.com/site/pmailkeey/e-mail>_______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to