Re: [Tagging] New Key capacity:*=n values

[johnw]

So back to capacity:*=n discussion. 

-The vehicle parking lots I usually tag have the following kinds of parking 
spaces, marked with signs and broken up into groups (visible on service area 
signs):

 (Some values taken from the access=* key wiki page. 
http://wiki.openstreetmap.org/wiki/Key:access#Land-based_transportation 
)


car (of course)  

tourist_bus (there are parking lots for tour busses at many tourist 
attractions, airports, service areas, stations. This is not “bus,” as per 
access=* wiki, those are public transport busses) 

hgv (large delivery truck, no articulation or removable trailer, parking lots 
usually found in distribution centers). 

“Semi” truck - tractor-trailer - (unsure of what value to put, but they have 
separate larger and longer parking spaces than the standard HGV vehicle - 
probably 5% of HGV vehicles in Japan are giant articulated US style semi 
trucks. I have not seen a 5th wheel yet.). Japan calls them “trailer” trucks. 
Please [suggest a good tag value] for these articulated tractor-trailer semi 
vehicles. 

oversize  (no difference between bus & HGV, as there are long spaces for both 
to use. Japan calls them “big” vehicles.)  [suggested value]

Motorcycle 

Disabled (car)

disabled-van (extra room to side-unload a wheelchair via a ramp).  [suggested 
value]

Disabled-bus (separate parking adjacent to the location, as opposed to normal 
bus parking which is way out in the parking lot. Also, no adjacent spaces, 
since they need room to unload).  [suggested value]

These lots are usually broken up into groups -separate lots - so it would be 
easy to tag one as amenity=parking for cars, amenity=motorcycle_parking for 
motorcycles, but there is no “oversized” vehicle parking (bus parking, truck 
parking, “long parking", &  semi parking), which I know from travelling are 
common lots to see at tourist spots and road stations around the world - but 
looking at taginfo, Amenity=* only has 10 uses for values contain bus or truck 
parking. 

So I am proposing a new amenity key amenity=oversize_parking, and we can use a 
subkey (oversize=bus, truck, semi, caravan, construction, multi) to handle 
creation of the new lots. It should have a Bus or HGV vehicle icon.  This is 
not for vehicle storage (like boat parking), but rather just parking lots 
dedicated to oversized vehicles, as found in commercial, industrial, tourist, 
and motorway parking lots for daily use. 

I’m surprised there is no oversized or equivalent parking currently. 

and the creation of the capacity:*=n values above marked with [suggested value] 
to handle it in a mixed lot setting. 

I look forward to your feedback. 

Javbw

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

Re: [Tagging] Feature Proposal - RFC - (nutrition_supplements)

[Andreas Goss]

Brought this up a few months back.

http://gis.19327.n5.nabble.com/shop-supplements-gt-shop-dietary-supplements-td5845622.html

What I found is that dietary supplements was what wikiepdia used and 
also most common on government pages (e.g. Food and Drug 
Administration). The EU even just seem to call it food supplements. 
Dietary seems a but more neutral than nutriotion and even when you 
google nutrition you will find a lot of pages that say dietary. Looks 
like a better fit to me.


But everything is better than just supplements.
__
openstreetmap.org/user/AndiG88
wiki.openstreetmap.org/wiki/User:AndiG88‎


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

Re: [Tagging] Contact:* prefix

[Andreas Goss]

Isn't so addr:
as well?


I actually don't like the addr: either. Because in most editors it means 
I have to type addr:s to get autocomplete, while it just have to type 
"ph" to get phone. Especially on mobile with the : it's not that great.


In addition we have so many tools and good editors these days that check 
for missing tags isn't that big of a deal. Also a lot of stuff like 
country or state or maybe even postalcodes in the future can be taken 
from boundaries so only a few addr: tags remain.


I mean we are at a point where it makes no sense to reverse it, but I 
honstly don't even see the big advantages there. And as Martin pointed 
out it was still more logical than contact. Ever tried to contact a 
company on Facebook or Twitter? Well, good luck.

__
openstreetmap.org/user/AndiG88
wiki.openstreetmap.org/wiki/User:AndiG88‎


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