-
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
Batch geocoding #7
Comments
This is on the roadmap - details to come. Will check out the app you referenced to the exception report. |
Here's an example report for your reference. It was created for a batch job to geocode this file - open data Medicare released showing provider charge rates across the US |
Adding to 2.0.x (meaning: scheduled for an undetermined 2.0.x series release) |
Adding 'help wanted' to this enhancement to encourage interested Geoclient users to provide feedback on desired functionality, use cases, etc... |
In the meantime, you could also use programs like Open Refine, that let you call a webservice with values from each record in a spreadsheet - https://github.com/OpenRefine/OpenRefine/wiki/Geocoding Not that having batch support wouldn't be nice though- |
Hi Chris, The issue isn't the availability of batch API's; it's being able to batch geocode against Geosupport from a non-mainframe, non-Microsoft, non-user-driven environment. E.g., As geocoders go, Geoclient is nothing special itself and (except for the single-field search) just a enabler -- like a JDBC driver is to Java and a specific database product. What's truly unique is the underlying Geosupport application which aggregates data into a collection of attributes not available directly from any other single source. |
I see,
Ok, just wanted to make sure people know about Open Refine. I installed a
http request module in postgres (https://github.com/pramsey/pgsql-http),
and can now geocode directly from there, that a pretty non-user driven
approach-
…On Tue, Mar 7, 2017 at 10:04 AM, Matthew Lipper ***@***.***> wrote:
Hi Chris,
The issue isn't the availability of batch API's; it's being able to batch
geocode against Geo*support* from a non-mainframe, non-Microsoft,
non-user-driven environment. E.g., As geocoders go, Geo*client* is
nothing special itself and (except for the single-field search) just a
enabler -- like a JDBC driver is to Java and a specific database product.
What's truly unique is the underlying Geosupport application which
aggregates data into a collection of attributes not available directly from
any other single source.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYgWKUyDkisJw4_xdzfRMHDZ5cYDY9Rjks5rjXIUgaJpZM4HECjs>
.
|
Ok, thanks for the info. |
Be able to send a CSV and get geocoded results along with exception report ala SmartyStreets
The text was updated successfully, but these errors were encountered: