-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default postprocessors on EsriWGS are too strict. #19
Comments
I ran into this again, trying to geocode localities and wondering why it doesn't return anything for e.g. "Philadelphia, PA". Seems preferable to me to have the default postprocessors be permissive and let users refine them if necessary. As it is, it's easy to assume that the underlying service is failing in cases where it's actually doing exactly what's desired but the results are getting dropped by the postprocessors. The list of possibilities is here, but I'm not sure it makes sense to pick a subset to allow by default. Dropping the |
Be default, if doing a gazetteer style search, the defautl postprocessors filter out everything.
To test:
Set up and run a new geocoder with EsriWSG:
You should get a few responses from the raw response:
But they get filtered out in /services/base.py
The text was updated successfully, but these errors were encountered: