Hi @abermans @tony_b @AdamGT @TerryPG @JustJake @WilfriedB @MortenCopenhagen,
To be fair I didn’t make the change to improve my statistics or tidy up for Google Maps - I wanted to reduce the number of inactive images that I have to scroll through whenever I need to find something. 
One thing to remember in all of the calls for proper account management tools for Google Maps… What is the core function of Google.. complex search results!
If it wasn’t so sad it would be hilarious.
Relatively speaking, the data set for any individual Local Guide is paltry in the scheme of things. The increase in data flow or processor load probably wouldn’t register noticeably. The limit of our current ability to manage our data is to split it by media and reviews. Then to list it by date or view count. The after thought that is ‘edits’ is for anything that doesn’t fit into that mould - roads is an odd fit in there.
One of the offsets of being able to create a search set is that you would see what you need rather than having to call the data of potentially thousands of images to find one single image.
Whilst I am waiting to see if I have found a workaround to getting direct human support through the data error tool, the only way I am likely to know is if the primary issue appears fixed at the same time as the secondary road issue I used to report both.
Taking the idea of being able to intercept and correct your own errors a bit further. The error reporting tool is still missing the nuance that would make it an efficient communication channel. I had to do a double take at the “something is wrong but I don’t know what is” That’s worthy of a pay rise right there!
Efficient reporting would include the opportunity to describe what corrections are required. We have a place Glastonbury Abbey (a historically significant set of ruins which include the possible resting place of King Arthur). There photos are jammed with images of other places. The nearby St John’s Church, Wells Cathedral and moated bishop’s Palace 6 miles away, Glastonbury Tor, nearby Chalice Wells, nearby George & Pilgrims Hotel, Glastonbury Museum, and countless shops in Glastonbury High Street.
Anyone who knows anything about the area would be able to spot where the correct POI is likely to be. So it would make sense to allow this feedback and then give local LGs the option to agree or disagree. This would then help the AI to learn and be able to make the same judgements.
One thing which drives me crazy are Google Maps suggestion prompts… Why don’t you submit this image (that you have already submitted). Suggesting the location of a photo you are going to submit (this is invariably the location that you were in when you take the picture of the POI - this little idiocy results in countless misplaced photos!)
AI should be able to look at your images and feedback before it is made public - are you sure this is a picture of the correct place?.. because it looks as if it should be this place instead. Like Asda Express that I misspelt as Asda Epress - of course despite clear text in photos of the place, which have been accepted and added, it won’t make the correction. 
Why do you have to visit your account to see how many views your submissions have gained? You could add this feature to any view. When your are logged in and you see one of your photos in amongst all the others the view count should be visible to you. It would certainly make updating your latest data for T100 easier.
Note to Adam (this little rant is why I wanted to step back before responding to your suggested changes ) - I need to go and have a little lie down…
