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
{{ message }}
This repository has been archived by the owner on Jan 8, 2020. It is now read-only.
To implement the call to the grasshopper geocoder we would like to get access to a test instance so we can judge de impact of latency and validate that we properly implement the calls.
Could you publish the url to a test api? (it can be heavily throttled. )
Thanks
The text was updated successfully, but these errors were encountered:
@FilipDeVos sorry for the delay in responding. we don't have a test site up yet. we expect to in the next calendar quarter or two. there are some fed compliance issues we are working through right now. can you describe your interest/need?
Thanks for the reply. We would like to call grasshopper to compare geocoder results with the geocoder that we are currently using. Later on we would like to allow the user to choose which geocoder to use (if your EULA allows that).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To implement the call to the grasshopper geocoder we would like to get access to a test instance so we can judge de impact of latency and validate that we properly implement the calls.
Could you publish the url to a test api? (it can be heavily throttled. )
Thanks
The text was updated successfully, but these errors were encountered: