On Thu, Apr 2, 2015 at 11:49 PM, Martin Vonwald imagic@gmail.com
wrote:
This contradicts in many cases our current page
http://wiki.openstreetmap.org/wiki/Map_Features/Units
It's not a contradiction, it's a proposal.
Computers are very good at removing spaces ( s/ //g ), and converting
On Fri, Apr 3, 2015 at 1:25 AM, Martin Vonwald imagic@gmail.com wrote:
+1 for the deletion (or at least move it to the proposal namespace). A
simply direct link to Map_Features/Units should be enough.
The majority of existing tags have a summary of the Map_Features/Units
embedded on their
2015-04-03 10:01 GMT+02:00 Lukas Sommer sommer...@gmail.com:
I think this template should be deleted or be changed to reflect
exactly what Map_Features/Units says. (But probably even a direct link
to Map_Features/Units would be easier and clearer – so I don’t see any
need for this template.)
On 3/04/2015 4:21 PM, Bryce Nesbitt wrote:
To try and make unit description consistent here is a proposed template.
This would apply to tags like ele, est_width, circumference, height,
width, maxwidth, minwidth, distance. A separate table could be made
for speed weight.
Use as follows:
It's not a contradiction, it's a proposal.
So please move it to the “Proposal/” namespace.
2015-04-03 8:01 GMT, Lukas Sommer sommer...@gmail.com:
The default unit is _not_ always “meters”. There are tags where the
default unit is “meters” (e. g. width) and there are others where the
default
On Fri, Apr 3, 2015 at 1:01 AM, Lukas Sommer sommer...@gmail.com wrote:
A wide variety of formats are acceptable:
The list that is following this statement doesn’t contain “km”. It
seems to be only a list of some non-mandatory examples
The template takes a parameter to adapt to different
The default unit is _not_ always “meters”. There are tags where the
default unit is “meters” (e. g. width) and there are others where the
default unit is “kilometers” (e. g. distance).
“Centimeters” isn’t in the current list of accepted units at
I'd ask the following be excluded ?
cm (used in the clothing and foot ware trades ..not an OSM thing )
cubits
I don’t think that there is a need to “exclude” some values (and
“allow” anything else). Insteat, I think there is a need to “allow”
some values (and exclude anything else).
On Fri, Apr 3, 2015 at 2:14 AM, Warin 61sundow...@gmail.com wrote:
ele= only takes meters as a unit .. the reason states is that Renderers
have no way of doing conversions on the fly to local units while creating
image tiles ... and this is an 'approved' tag.
That's mapping for the
From an IT perspective we should be keeping form and function separate.
There are two facts here:
1) the altitude of that point is 14505 ft - it is what it is, whatever
units you use. Saying the altitude is 4421.124m is also correct. The
value needs a number and a unit, in an agreed format.
So please move it to the “Proposal/” namespace.
That's not possible for a working template,
Note the template is not USED,
And it should also not be used, because it’s just your personal
proposal for a discussion. So there is no need to have a working
template. So please move it to the
The majority of existing tags have a summary of the Map_Features/Units
embedded on their own pages.
That's a good thing for tl;dr readers.
Map_Features/Units isn’t a big wiki page. It’s really short (3
sentences and some tables). Maybe for keys like “width” it could be
usefull to have only
This contradicts in many cases our current page
http://wiki.openstreetmap.org/wiki/Map_Features/Units
* The use of meters is discouraged
* cm should not be used generally, maybe only on some specific tags
* There should always be a space in front of the unit
* Neither feet nor inches should be
2015-04-03 9:39 GMT+02:00 Bryce Nesbitt bry...@obviously.com:
It's not a contradiction, it's a proposal.
Then you should label it accordingly. Currently it is nowhere identified as
proposal.
___
Tagging mailing list
Tagging@openstreetmap.org
I am against adding yet another template to wiki, intended to be used as
part of article
text.
Many pages are already obnoxious to edit because on editing it turns out
that table
is hidden in a template - so it is necessary to open another page.
It also promotes explicit numbers (e.g. 20 m) over
On 3/04/2015 7:39 PM, Bryce Nesbitt wrote:
Either way, a cleanup of the recognized units is in order (e.g. km,
m/meters/m, ft/feet/foot/ ).
I note that;
ele= only takes meters as a unit .. the reason states is that Renderers
have no way of doing conversions on the fly to local units
On 3/04/2015 8:33 PM, Bryce Nesbitt wrote:
On Fri, Apr 3, 2015 at 2:14 AM, Warin 61sundow...@gmail.com
mailto:61sundow...@gmail.com wrote:
ele= only takes meters as a unit .. the reason states is that
Renderers have no way of doing conversions on the fly to local
units while
To try and make unit description consistent here is a proposed template.
This would apply to tags like ele, est_width, circumference, height, width,
maxwidth, minwidth, distance. A separate table could be made for speed
weight.
Use as follows:
{{Unit_Tagging_Length|tag_name|furlongs}}
The
18 matches
Mail list logo
