Open MatthewJA opened 3 years ago
Hey @MatthewJA
Thanks for the suggestion, can you perhaps just expand how you'd envisage this working?
Thanks, Rowan
Hi @rowanwins, sure thing. The search box could take geohash queries: which would resolve as locations:
Here's an image of a dataset that makes use of geohashes already as identifiers:
The current workflow for using geohashes is to first convert them with a service like http://geohash.co/ into lat/lon and then search for that instead, which resolves to a coordinate location.
Yeah cool, the search box was the easy (ier) thing that came to mind. Thanks for the clarification.
We should be able to support this relatively easily using the new Web Feature Service search provider since there's a WFS version of this layer.
Or pull in an npm package like ngeohash or latlon-geohash which does the decoding clientside
@rowanwins I like your idea better, because it's much more generic. The WFS search provider approach is layer-specific, but decoding a geohash isn't.
Feature request to support spatial queries by geohash. This would be really useful for projects which name polygons or points by their location.