Loving Dato so far and the continued efforts of the team to improve the platform!
One thing my team thinks is missing (and could desperately do with!) is filtering Geolocation fields by a bounding box. This would open up the ability to efficiently filter by the “view” of a map, allowing developers to implement an Airbnb-style maps.
Good idea (please remember to vote on it in the upper left!), and this would help make our geo field more powerful, for sure. I don’t think there are any current plans for it, unfortunately, but hopefully someday!
In the meantime, just as a workaround, you can use the Computed Fields plugin to derive the selected location into separate lng and lat float fields, like this:
Alternatively, if you don’t have too many locations to begin with (< a few hundred, maybe?), I might consider fetching ALL of them upfront (or at least within a huge radius) and then just filtering them clientside. POI data isn’t usually that big over the wire (especially gzipped), and it can make the map browsing/searching/filtering a lot faster if the client already has all of them cached locally.
(But again, this doesn’t in any way take away from the validity of the original request… I agree that it’d be a useful thing for us to support serverside, instead of making you jump through hoops like these!)