[Tagging] Lyft and nameless sectioning in OSM

[Evan Carroll]

>
>
> The wiki is often incomplete or wrong.    You are proposing a massive
> change in OSM, essentially to deprecated the concept of landuse, and I
> think very few people share that view.
>


I don't see it like that. Why do you? Nothing in the wiki on landuse
mentions property lines.  That's not how they're used. I asked what the
value was, I was told to emphasize and de-emphasize areas on maps. They're
currently being mapped as a collection of buildings,  ie., a group of
residential buildings sits on landuse that is residential. Lyft is doing
this remotely, without ever having a foot on the ground. That's what this
topic is about. I don't see the value: but I'm saying I can do it
automatically and more accurately then Lyft, and then we can keep it in
sync rather than creating a maintenance burden. All while continuing to
deliver the same value that people see.

For reference, I disagree with tag:landuse in OSM, but this suggestion is
precisely because as OSM is currently using unnamed landuse of
developed land, the process can be automated internally and I believe we
can make everything better. What difference would be though if I
demonstrate it can be done automatically oblivious to property lines, or
Lyft continues to fund gaggles of workers to do it (oblivious to property
lines)?

Lastly, the wiki is editable. And this is the list to have a conversation
about property lines and landuse. This whole thread was because I did not
understand landuse. Now as it's been explained and as I understand it, I
have a different model of it then you do. This is problematic for everyone.
You should post on this thread about how to reform the tag:landuse:* to
mention property lines if you feel that's how the tag should be used (or is
used currently). You're the first person to bring it up as far as I see.

--
Evan Carroll - me at evancarroll.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20221012/bdfd70f3/attachment-0001.htm>