|Sent on:||Friday, January 31, 2014 11:07 AM|
Nice work as usual John! Good to know about the geocode rate for the collision data. I was planning on running a test.
My code is nowhere near as clean as John’s but if might be of interest that I ran @3millions records through the NYC GeoClient in December. Overall, the services worked great and was able to make @1,500 calls per min. I was geocoding the parking ticket data on nyc open data.
I've been messing around with NYC's geoclient API. It's quite powerful! I wrapped the REST calls in a Python module, which is accessible for all on PyPI. You can check it out here:
And the documentation here:
Unfortunately, you need to register an app with DoITT (and sign it up for the Geoclient API) then wait a few days before being able to use the API. So get registered ASAP!
On a side-note, according to Geoclient, almost 20% of the intersections in the city's own collision statistics releases are ambiguous or invalid.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by John Krauss ([address removed]) from #betaNYC, a Code for America Brigade for NYC.
To learn more about John Krauss, visit his/her member profile
To report this message or block the sender, please click here
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
| [address removed]