Re: [Tagging] weight limit in short tons

2019-01-28 Thread Warin

Point. However where have you seen a weight limit in stone?

Possibly a lift? Though they usually just say number of people .. and 
beep if over loaded.


The abbreviation form short ton has been there a while.


On 29/01/19 08:51, Andrew Hain wrote:
As a quick objection from a British mapper old enough to remember 
obsolete measurements: long tons are pointless, too similar to toes 
and not used on signs anywhere I know of, the abbreviation st can 
stand for a stone (6.3kg or 14lb).


--
Andrew

*From:* Warin <61sundow...@gmail.com>
*Sent:* 27 January 2019 23:11
*To:* tagging@openstreetmap.org
*Subject:* Re: [Tagging] weight limit in short tons
On 28/01/19 04:24, Sergio Manzi wrote:

On 2019-01-27 17:53, OSMDoudou wrote:

Indeed, it's very strange to require mappers do the maths when there is a 
notation to indicate the unit and let the renderers do the maths.

Hi!

Why do you talk about math? Do you expect renderers to automatically convert 
weights from whatever unit to the one you're using for your locale? Or maybe to 
use those weight limits as a parameter for the router?


Yes. The renders have to cope with different units for speed, length, height, 
elevation etc. so why not weight?

As has been said before - far easier to find an error in the rendering and 
correct it than
find an error in the maths used by a single entry or a single mapper in the 
data base.

If this is what you want, then the problem is the parsing of the string used to define the units used within the tag: 
as already pointed out, "ton" is the symbol used for both "long" (UK, imperial) and 
"short" (US, cental) tons, so we must find a "controlled" way to indicate which measurement system 
is in use for the tag.

On the wiki page for units there is now the default unit of the tonne (metric 
ton for usa), and then alternative units of st for short ton, lt for long ton.
https://wiki.openstreetmap.org/wiki/Map_Features/Units
I just recently add the lt for long ton, the short ton was already there. If 
you want to add other units .. do so.


If the mapper uses the unit 'ton' then they have not complied with the wiki and
there would need to be a decision on using it at all, if using it then what 
unit is to be used.


If instead we are not interested in possible computations, then we can live 
with the customary way to indicate tons, and deduce from the location which 
kind of tons we are talking about, same as if we were traveling to the place 
and see the indication on a sign, with our own eyes.

And indeed the same heuristics can possibly be applied to a parser...

Sergio






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


Re: [Tagging] Feature Proposal – RFC – natural=peninsula (Was: Feature Proposal – RFC – place=peninsula)

2019-01-28 Thread Markus
On Sun, 27 Jan 2019 at 23:52, Graeme Fitzpatrick  wrote:
>
> "Both the cape & the peninsula can sometimes share the same name eg "Cape York
> https://www.openstreetmap.org/node/2138519757#map=9/-10.6415/142.5873 is the 
> extreme tip of Cape York Peninsula
> https://en.wikipedia.org/wiki/Cape_York_Peninsula#/media/File:A2015_Cape_York_Peninsula_map.svg;?

Good idea, thanks! I've added it to the proposal page.

Regards

Markus

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


Re: [Tagging] crossing=cycleway as a node

2019-01-28 Thread Martin Koppenhoefer


sent from a phone

> On 28. Jan 2019, at 10:59, Marc Gemis  wrote:
> 
> representing a way in OSM, and foot=yes on the way (can be implicit),
> but foot=no on the X representing the bicycle crossing, pedestrians
> cannot pass point 'X'.
> At least that is how I understand the current access rules in OSM.


right, it might lead to problems, better not put it, it could prevent the 
router from routing pedestrians on the road.

Thank you for pointing it out

Cheers, Martin 
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] crossing=cycleway as a node

2019-01-28 Thread Marc Gemis
On Sun, Jan 27, 2019 at 6:30 PM Martin Koppenhoefer
 wrote:
>
>
>
> sent from a phone
>
> > On 27. Jan 2019, at 12:29, Marc Gemis  wrote:
> >
> > But often, the cycleway crossing the road is not mapped. How would you
> > map a bicycle only crossing if the parallel cycleway is mapped as
> > cycleway=lane on the highway=x ?
>
>
> foot=no on the highway=crossing node
> Also if the cycleway is mapped explicitly it would make sense (if it were 
> forbidden for pedestrians to cross the street there), because it could still 
> mean there’s an implicit footway crossing otherwise.


foot=no means that pedestrians cannot pass that node for any way
passing through the node, not ?


so if you have


--X--->

representing a way in OSM, and foot=yes on the way (can be implicit),
but foot=no on the X representing the bicycle crossing, pedestrians
cannot pass point 'X'.
At least that is how I understand the current access rules in OSM.

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