[Tagging] Lyft and nameless sectioning in OSM

[Minh Nguyen]

Vào lúc 18:27 2022-10-11, Shawn K. Quinn đã viết:
>> If, like me, you want to see fewer unnamed landuse areas in your 
>> backyard, map more named landuse areas corresponding to retail and 
>> residential developments. These areas not only reduce the pressure to
>> "fill in" the map visually but also add information about the shape
>> of these developments that's often difficult to obtain from other map
>> services.
> 
> What I'd like to see less of is the use of dubious tag combinations like 
> this:
> 
> landuse=retail
> amenity=fuel
> shop=convenience
> name=Exxon
> 
> or whatever the brand might be. First, the convenience store and fuel 
> should be separately tagged; I tag the fuel canopy (or an area near the 
> pumps if no canopy)  as being the fuel station, and the building as the 
> convenience store (which also gets the address data if  known). 
> Convenience stores may be inside a landuse area, but shouldn't be tagged 
> on the same way as a landuse area as I understand it.

Dual-tagging a landuse area as a POI might make sense in some cases, but 
I agree that dual-tagging the entire property as a gas station would be 
misleading. In the U.S., a gas station is usually an amenity of a 
convenience store or auto mechanic, not the other way around.

Anyhow, I was suggesting mapping combinations like the following:

Apartment complex: landuse=residential residential=apartments name=*
Mobile home park: landuse=residential residential=trailer_park name=*
Residential subdivision: landuse=residential residential=single_family 
name=*
Office park: landuse=commercial name=*
Strip mall: landuse=retail name=*

Non-landuse alternatives wouldn't be as precise or informative or enjoy 
as much existing software support. Along with quasi-landuse areas like 
amenity=hospital and leisure=park, typical American sprawl would have 
enough of this more specific kind of landuse area to ward off the 
broader kind to some extent.

-- 
minh at nguyen.cincinnati.oh.us