Ah, abruzzi, thanks for the update on needs. I'm also rather fanatic about location. Indeed, I switched TO Aperture a bazillion years ago when it first got geolocation abilities, and didn't switch back to Lr until much later.
So lemme expound at (too much) length on what's worked for me, and maybe it will help.
A primary reason to use geolocation is to
find stuff. One way is browsing a map, and both Aperture, Lr and Photos will do that. I find Photos kind of irritating to go back and forth, and it's organizational tools kinda lag for bulk geo work and stuff, so I'll ignore it. But it does some stuff. Both Aperture and Lr use only one map, a big limitation IMHO. But I do prefer Google maps in Lr over Apple Maps in Aperture. For just one reason, Google tends to show more trails in parks near me and I do a LOT of hiking; Apple maps doesn't show the trails at all. So if I want to see photos on X trail, tough in Photos or Aperture.
Lr however has that modular approach. So it doesn't have quite the tools immediately available in its map view as Aperture. And it can't make a smart album for proximity like Aperture does; instead it has the abiility to save map locations, and modify them more easily. Lr has reverse geocoding built in, Aperture doesn't do that as well if at all. And I find using location info (location, sub-location, city, state) quite useful for searching, as well as use externally. And I much prefer how Lr can write that metadata to files more easily.
I dunno how you get GPS coordinates in, but I mostly use either my camera, or Houdah Geo combined with gps4cam, the best iOS app for tracking and GPS coding of photos. While Lr can use synching via a GPS track, Houdah Geo/gps4cam are much easier. And Houdah Geo can also reverse geocode. It also can make use of several maps, like MapBox, which not only shows trails but their names in places. So I prefer it when there's some ambiguity in GPS data. BTW, Houdah Geo is also excellent for exporting to KML so you can send both pictures and route to say Dropbox and publish it to Google, or view the coordinates in say Google Maps or Google Earth in a browser, etc. As well as manipulate other data.
And while Lr does do reverse geocoding, sometimes I use Houdah Geo. It has ways to customize what info you use, like its own database, or Apple, etc. It can also do altitude lookups.
For images that I already have coordinates for, now I use a wonderful Lr plugin, Jeffrey Friedl's "Geoencoding support" plugin,
Jeffrey Friedl's Blog » Jeffrey’s “Geoencoding Support” Plugin for Lightroom. It not only does better geoencoding than Lr does, but also allows for customization. And better track synching. It can also show the images in a ton of other maps, from Apple's to say OpenStreetMap to Google Earth. I find it really helpful for fine tuning location and also using the coordinates for other work outside Lr. You can also copy incoordinates. And in reverse geoencoding, it allows you to mess more with the data, which is especially helpful with locations outside existing cities, like national parks and such. Like Houdah Geo, you can use it to fill altitude. You can even embed a map url in the image's metadata. Finally, it allows for customizable proximity searches in Lr. For people using GPS a lot, it's a must-have.
There are times though that I use Photo Mechanic for location data. I have a ton of stationary pads set up for various locales I visited a lot of times, and since PM is also great with keywords and templates, if it's a common location for me I just may use PM to fill in the location data aside from GPS coordinates. Like say the array you cited, since that would have some unique keywords as well.