Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It seems like the obvious solution to this would be for Google to provide a sensible way to accept corrections to their maps.

We had to get a change made to Google maps to prevent people getting killed here, and it took national news, and personal contacts within the organisation.

Something is rotten in the state of Denmark.




In the US its pretty easy to submit corrections. I've submitted a few corrections on US public lands but now I usually don't bother and just update open street map instead.


I have submitted many glaring fixes, often multiple times for when it continues to be a problem, over months... and almost never is it fixed.


I once submitted a correction for the exact location of a public park. The correction looked like it was applied, but when I looked later it had been reverted.


The data pipelines for maps can be very long - certain changes might take 6 months or more to be applied, because the computation required to rebuild certain things is massive, and it isn't worth doing simply because some street edge moved by a few centimeters.


This wasn't a few centimeters - I had trouble finding the park because Google had it a couple of blocks away from its actual location.


> and just update open street map instead

I think this is the right approach. Why do free ground-proofing for a for-profit company? (Who is also so unresponsive). Better to submit fixes to a community project.


"Something is rotten in the state of Denmark" is quote from Hamlet :)




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: