You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently save them as floating point numbers, by default the search form will look for an exact match within a FloatField; so often I get no results if I give the coordinates with 4 decimal points precision.
I'd like to propose a tolerance built into the search query, i.e. return all results that are with in the range of (queried coordinate - tolerance, queried coordinate + tolerance) and set the tolerance to 0.0001.
Should I do this only for the Place in my ontology that inherits from E53_Place or is this of interest to anyone else?
The text was updated successfully, but these errors were encountered:
We currently save them as floating point numbers, by default the search form will look for an exact match within a FloatField; so often I get no results if I give the coordinates with 4 decimal points precision.
I'd like to propose a tolerance built into the search query, i.e. return all results that are with in the range of (queried coordinate - tolerance, queried coordinate + tolerance) and set the tolerance to 0.0001.
Should I do this only for the Place in my ontology that inherits from E53_Place or is this of interest to anyone else?
The text was updated successfully, but these errors were encountered: