street2coordinates return order, version number?

[Lance Crumbliss]

How is the returned list order determined when batch geocoding?  I've tested a list of about 600 addresses (which takes about 5 seconds on our internal VM) and the order is completely different than what was POSTed.  I need to be able to reconcile the input address list with the geocoded results.  It looks as though the root of a particular JSON object is the address returned, correct?  If so, I can use that as a Key.

Also, although we download an spun up http://static.datasciencetoolkit.org/dstk_0.41.box, it says v0.40 (March 2012) on the about page.  It also references a VMWare image in the documentation instead of Vagrant.  I just want to be clear what version we've actually go up and running.

Lance

[Pete Warden]

Hi Lance,

              you're correct, the key in the returned object is the input address, and any geo information found is attached as the value for that key, or null if the address didn't yield anything. I'm actually fond of Javascript's defacto behavior of ordering objects, where the output order is the same as the declaration order, but Ruby doesn't preserve the order, which is why the API output gets jumbled.

Sorry about the stale documentation, you have the correct 0.41 version. Because I don't get an AMI id from Amazon until *after* I've created the VM, I can't include the up to date information on that in the internal documentation. I do normally try to update the rest of the information (version number, date, etc) though before I package it up, but I must have skipped that this last time through.

Does that help?

cheers,

           Pete

Lance

--
You received this message because you are subscribed to the Google Groups "dstk-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dstk-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Jetpac

You should get the app for your iPad!