[talk-au] TomTom - OSM Collaboration

[Stéphane Guillou]

Hi Will

Thank you for reaching out before starting, it's really appreciated.

As Phil mentioned, a wiki page detailing the intentions, methods and OSM 
editors is important. Here is Facebook's as an example: 
https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Facebook

just a word of caution, when it comes to (semi-)automated edits of the 
database: there has been in the past several examples of conflicts 
between OSM volunteer editors and well-meaning companies. Communication 
is primordial to avoid conflicts and lasting bad reputation in the 
community because of community time spent on fixing up dozens of 
changesets because the plan wasn't discussed and tested enough before 
being executed.

Please keep in mind that I am not criticising business involvement in 
editing the database, I am only hoping to minimise potential conflict. 
Your ideas sound interesting and useful, and again, you reaching out is 
very appreciated :)

About scraping media and housing development data, I guess the legality 
of it needs to be thoroughly studied as it might be perceived as a 
breach of copyright, but I'm not knowledgeable enough to judge.

I agree with Phil that the established tasks can be something to get 
started on, it could be a more guided way to introduce new contributors 
to the database.

Cheers

On 7/9/22 07:54, Phil Wyatt wrote:
>
> Welcome aboard Will,
>
> There is no shortage of tasks to make a better Australian map in OSM. 
> There are plenty of map roulette challenges for updating addresses, 
> fixing deprecated tagging on features and fixing road tagging to name 
> just a few.
>
> https://maproulette.org/dashboard/
>
> The community is also very grateful for folks ‘in the know’ who may be 
> able to source data in truly open formats that can be ingested into 
> OSM using the normal import procedures or via the RapID editor (for 
> ESRI community layers)
>
> https://github.com/facebookmicrosites/Open-Mapping-At-Facebook/wiki/Esri-ArcGIS-FAQ
>
> https://wiki.openstreetmap.org/wiki/Esri/ArcGIS_Datasets - as you can 
> see there are no layers from Australia.
>
> https://wiki.openstreetmap.org/wiki/Import/Guidelines - import guidelines
>
> If there is going to be concerted effort by Tom Tom then it might also 
> pay to have a read of the organised editing guidelines and maybe set 
> up a wiki page with some details of the company intentions (and maybe 
> a list of OSM editors that will be editing on behalf of Tom Tom.
>
> We look forward to your edits and conversations in the mailing lists.
>
> Cheers – Phil
>
> *From:*William Ireland <William.Ireland at tomtom.com>
> *Sent:* Wednesday, 7 September 2022 10:12 AM
> *To:* talk-au at openstreetmap.org
> *Subject:* [talk-au] TomTom - OSM Collaboration
>
> Hi Australia OSM Community,
>
> My name is Will from TomTom. From one mapper to another, I can say 
> that we truly admire how the OSM community collaborates to shape a map 
> product that benefits everyone, and we would love to be a part of it. 
> I would like to let you know that we are planning on contributing to 
> OSM by providing meaningful leads to improve map quality and to locate 
> missing features. Some initial ideas include but are not limited to 
> providing leads from media sources extracted by our web scraping tool 
> or locating missing highways from new housing developments.
>
> We would love to hear from you. What do you think of these ideas? And 
> are there any other areas where you need assistance or fields we can 
> collaborate on? We are open to all suggestions and ideas. As for me, I 
> am based here in Australia and happy to answer any questions or be 
> part of any discussions.
>
> Looking forward to hearing from you,
>
> Will
>
>
> _______________________________________________
> Talk-au mailing list
> Talk-au at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-au/attachments/20220907/f1e0e1df/attachment-0001.htm>