No, you delete the data that's on the server. That's the reasonable way to handle a revocation of consent from the user.
This is a bad assumption and why you would ruin a product like google maps if given the opportunity.
Google already had this problem for years with Contacts. I had local contacts on my phone, and contacts stored in my google account. It was a complete clusterfuck of duplicates, stale data, etc. Years later after I had this problem, Google added a fairly complicated power-user tool that let you reconcile this data. And then years after that, the tool became not-a-power-user tool and wasn't bad.
But we're still talking years of issues, for data that is probably a hell of a lot less complicated than what maps stores.
edit: And that said, I still have issues every now and then with that contact reconciler tool, it doesn't always do the right thing.
I'm sure you've got it all figured out. You should go work at google and implement it.
I think you are ridiculously underestimating the complexity and issues that would arise with two separate mechanisms for saving the same kind of data, and an option to switch between the two. Do you download account-saved locations locally when changing to local storage? What if there are conflicting pieces of data?
I bet there would be a lot more outraged people about the bugs and limitations that would arise with this system than there are today with your complaints.