That was the idea, right. Even if we move the geocoding handling out of JS and into the proxy (so it's only useful to talk to the geocoding backend), that could be abused (even if the scope is restricted).

How about I make the input line depend on ROLE_USER, too? That is, guests don't get to search locations, but I think that's a good trade-off, it's just the UI that should match.