[OSM-talk] Craigslist OpenStreetMap Rendering Issue

Marc Gemis marc.gemis at gmail.com
Mon Jun 1 07:55:21 UTC 2015


just a few thoughts:

What is the value of a 1 time mechanical edit cleanup ? From the moment you
ran your script, new data can arrive in the OSM with the wrong values.
Will you run your script daily ? What if a data consumer obtains the data
between 2 runs of your script ?

Wouldn't it be better to properly inform the data consumer about the
existence of some "fix" scripts that can be run after obtaining the data
from OSM ?

Of course one could imaging an OSM setup where those mechanical edits would
run automatically after each submission, but that is out of the question I
think. Part of that work could be (or is) done by the validators in the
editors.

regards

m



On Mon, Jun 1, 2015 at 8:36 AM, Bryce Nesbitt <bryce2 at obviously.com> wrote:

> The tag oneway=true is extinct in the database.
>
>
> Without defending the author of the Craigslist stylesheet: tracking OSM
> data changes is hard.
>
> In part due to the negative attitude towards cleanup mechanical edits, the
> data is all over the place.
> 1, -1, reverse, true, false, no, yes, maybe.  Aghgh.  Stuff gets
> deprecated then rots in place for weeks
> months years.
>
> How could a rendering engine keep up with all the positive and negative
> terms people dream up,
> wikifi, and then use inconsistently?
>
> ---------------------
>
> Mechanical edits help data consumers.  Clear tag descriptions help data
> consumers and mappers.
> Editor validations helps data consumers, and it's rather weak right now.
> API level rejection of certain
> edit patterns would help even more.
>
> A clear migration path between tagging schemes would help data consumers a
> lot.
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20150601/822c872f/attachment.html>


More information about the talk mailing list