I’m loving the new location dimension type, but I’ve found the filters can be a bit clunky for my business users. For example, at SpotHero we spend a lot of time analyzing competitive parking garages within a certain radius (say 1/10 or 1/4 mile) of our garages. So in theory someone may ask what are the best performing garages within a 1/4 mile radius of Garage X?
Our Account Execs are extremely familiar with the names of these garages which are stored as the dimension “parking_spot_title” but don’t know the Lat/Long of every single location on our platform currently stored as “parking_spot_location”. Right now, I use a work around on one dashboard where the AE can come to the dashboard and use a dashboard filter to specify a single location and return the lat/long for that location which they can then add to a separate dashboard filter with the standard “.5 miles from lat,long” filter language.
This works, but I think it’d be really nice to add a “location_title” parameter (in addition to sql_latitude and sql_longitude) to location dimension types so my Team can have a list of locations (along with suggestions) to choose from, but can be completely unaware of the lat/long. I see the filter looking something like this:
[user specify: number] [dropdown: unit of measurement] from [user specify: location_title]
I’d love to hear some feedback about how others are using location. Let me know if this request makes sense to you, or if there are some other options I should be considering for this use case.