[talk-au] Mapbox mapping activity

Alex (Maxious) Sadleir maxious at gmail.com
Sat Apr 23 03:45:48 UTC 2022


It's not just us Aussies left scratching our heads, several country
mailing lists got this message.

DWG is aware https://github.com/mapbox/mapping/issues/409
> Please answer (on this issue and every other country issue) the same questions that were asked at #387 , and make sure that a local mailing list also sees those answers.
> Simply posting the same link without explanation for every country is not good enough.
> -- Andy (SomeoneElse, from OSM's Data Working Group)
> Communication isn't occurring - hence the angry reply at http://lists.openstreetmap.ch/pipermail/talk-ch/2022-April/011470.html ,
> Another is that the quality of some of Mapbox's mapping doesn't reflect https://wiki.openstreetmap.org/wiki/How_Mapbox_Data_RAVE_team_work_on_receiving_feedback_from_OSM_users . The DWG have had a number of issues recently where Mapbox editors have changed something from "wrong, and detected by a QA metric" to "differently wrong, but not detected by a QA metric". In the long term editing like this harms the quality of OSM because it prevents mappers fixing problems properly.
> Obviously we (the DWG) raise issues with individual mappers and if necessary with Mapbox directly but the worrying thing is that Mapbox as a company appears not to be learning from its mistakes - Mapbox has been involved with (and dependent on) OSM data for many years now but we're still seeing examples of really poor quality mapping, of the "just remove a tag so that a detected error goes away, never mind if it actually matches the actual situation" variety.


On Sat, Apr 23, 2022 at 9:35 AM stevea <steveaOSM at softworkers.com> wrote:
>
> OK, I've found the links, but a couple of things:
>
> 1)  On the wiki page (about "linting," I've used "lint" in C code, is that what you mean?), I don't want to see "examples," (although, they are better than nothing), I want to see SPECIFICS.
>
> 2)  The GitHub page is also pretty vague.  You say "we use internal Mapbox data validation jobs that search OSM data for errors for detecting issues related to road network data in Australia. In total, we are going to review issues in 9 categories."
>
> OK, WHAT 9 categories?
>
> I appreciate that you are "offering notice," but please be less vague.
>
> > On Apr 22, 2022, at 12:08 AM, Sergey Beliamei via Talk-au <talk-au at openstreetmap.org> wrote:
> >>
> >> Hello from the Mapbox Team!
> >> In April 2022 our team is going to start a mapping project in Australia. As part of on-going work to improve the quality of OpenStreetMap data, our team is planning to review a subset of the detections to better understand the type of issues, and also fix any valid data issues directly in the OSM. We're concentrating on road mistakes to improve map condition. In Australia
> >> we plan to upload data once a week to see and fix the latest mistakes in mapping after reviewing the 1st iteration.
> >> We would really appreciate your feedback, any questions you have about this
> >> project, as well as local insights that you think will help us better understand the data.
> >> There's a link to our Github ticket to the related issue and a link to our page in OSM Wiki.
> >>
> >>
> >> Best regards,
> >> Member of Mapbox team,
> >> Sergey
> >
>
>
> _______________________________________________
> Talk-au mailing list
> Talk-au at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au



More information about the Talk-au mailing list