I’ve developed a very efficient way for following up on my edits in Google Maps.
First of all, I use a JavaScript tool created by @gncnpk called “A tool for filtering edits on Google Maps by status and type.”
Special thanks to him — especially for the edit statistics and edit count features, which help me track all my approved and rejected edits.
For approved edits, I continue making improvements in that area until there are no new roads left to add.
For rejected edits, I ask myself why Google might have rejected them — was it due to a tree, shadow, color change, edit length (too short or too long), or something else?
Then I try to add the road again, sometimes from the other side.
In cases where an edit keeps getting rejected, I take photos of the road, my submitted edit, and the submission confirmation email — I might need them later if I open a case with Google Maps support.
I place a marker for every road I create and remove it only when all work in that area is complete and there’s no further need for follow-up.
In the third stage, I retrieve all my edits from the past three or four days and compare them with my existing markers.
Any marker without a nearby edit usually means one of two things:
A poor-quality edit that will disappear after 90 days, or
An incomplete edit that I missed and need to finish.
If a marker remains unapproved for more than two months, I change its flag so I can skip it in my daily checks — until I either re-edit it or Google rejects it and I start the process again.
In both cases, I only use a single function of the scripts, the Auto Load feature. After scrolling to the end, I open the developer console and copy the underlying HTML to clipboard and wrote some Python scripts which extract the essential information and converts to a CSV format, which I then paste into spreadsheets for further analysis and tracking.
Instead of setting markers in Maps, which I also tried for a short time, I keep the permalinks now in my spreadsheets. For some of my road edits, I copy the little map of the email also into the spreadsheet.
Thank you for your feedback. You’ve actually solved one of my problems! I was wondering how I could get the coordinates of my edits. There’s no Google API for that, but with the developer console and a Python script, it works perfectly.
Amazing — I really appreciate it.
I thought it will be straight forward to find the coordinates of my edits using developer tool “I will see them directly” but I couldn’t “I don’t know where to do or click”.
Please your help. hope you have a video in YouTube or details steps.
Hello @Port
I am able to extract several parts of information, such as the date of submit (but not the time), type of action (road edit, name change, … etc), name and sometimes the address of the place, the status (pending, accepted, rejected …) and even the number of views for some types of edits (e.g. adding a new place listing).
However, I still need to copy (via sharing) the link manually and paste it into my spreadsheet. Not sure, if it is completely impossible to be done automatically, but it seems to me the permalinks are dynamically generated after you clicked share. The geographical coordinates, I couldn’t find anywhere in the list of contributions, but I don’t need those, as long I have the permalink to the place.