Comments on: Geocoding with GeoPy http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/ a blog about GIS, CMS, agile development and design patterns Fri, 12 Mar 2010 00:18:43 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Paolo Corti http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-64454 Paolo Corti Wed, 28 Oct 2009 13:30:09 +0000 http://www.paolocorti.net/?p=151#comment-64454 Skylar, look at the 3th post before this one ;-) Skylar, look at the 3th post before this one ;-)

]]> By: Skylar Saveland http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-64340 Skylar Saveland Wed, 28 Oct 2009 04:12:19 +0000 http://www.paolocorti.net/?p=151#comment-64340 Cool, I see that you are getting into a Pinax a bit too. Ever tried GeoDjango? Cool, I see that you are getting into a Pinax a bit too. Ever tried GeoDjango?

]]> By: Greg Corradini http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-63256 Greg Corradini Sun, 18 Oct 2009 02:01:36 +0000 http://www.paolocorti.net/?p=151#comment-63256 I love GeoPy. Thanks Paolo I love GeoPy. Thanks Paolo

]]> By: Paolo Corti http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62939 Paolo Corti Thu, 15 Oct 2009 08:56:40 +0000 http://www.paolocorti.net/?p=151#comment-62939 thanks, but I have left it there because it depends from what device the user is making the request. Just like I left out my original key values, every user needs to provide its values. thanks, but I have left it there because it depends from what device the user is making the request. Just like I left out my original key values, every user needs to provide its values.

]]> By: G http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62921 G Thu, 15 Oct 2009 05:45:35 +0000 http://www.paolocorti.net/?p=151#comment-62921 All of your sample URLs have sensor=true_or_false in them. This breaks as of October 15, 2009... you'll need to set that to either "sensor=true" or "sensor=false" All of your sample URLs have sensor=true_or_false in them. This breaks as of October 15, 2009… you’ll need to set that to either “sensor=true” or “sensor=false”

]]> By: GIS-Lab Blog http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62892 GIS-Lab Blog Thu, 15 Oct 2009 00:20:06 +0000 http://www.paolocorti.net/?p=151#comment-62892 <strong>??????? ??????...</strong> SASGIS.ru сообÑ?аеÑ? об обновлении сеÑ?виса Ð?аÑ?Ñ?Ñ?@Mail.Ru (каÑ?Ñ?Ñ? СамаÑ?Ñ?, Челябинска, Ð?Ð... ??????? ??????…

SASGIS.ru сообÑ?аеÑ? об обновлении сеÑ?виса Ð?аÑ?Ñ?Ñ?@Mail.Ru (каÑ?Ñ?Ñ? СамаÑ?Ñ?, Челябинска, Ð?Ð…

]]> By: Paolo http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62871 Paolo Wed, 14 Oct 2009 21:02:42 +0000 http://www.paolocorti.net/?p=151#comment-62871 Hey Sean, I am going to remove the "REST" word between "HTTP" and "request" but: to my understanding isn't a read only access to a URL resource made by an HTTP GET, like in this case? Okthere is not PUT-DELETE etc in this case, but it is still a REST resource accessed by a GET. And why, ie Yahoo is talking about REST here: http://developer.yahoo.com/search/rest.html Thanks for your (eventual) explanation :D Hey Sean, I am going to remove the “REST” word between “HTTP” and “request” but: to my understanding isn’t a read only access to a URL resource made by an HTTP GET, like in this case? Okthere is not PUT-DELETE etc in this case, but it is still a REST resource accessed by a GET.
And why, ie Yahoo is talking about REST here: http://developer.yahoo.com/search/rest.html
Thanks for your (eventual) explanation :D

]]> By: Sean Gillies http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62853 Sean Gillies Wed, 14 Oct 2009 18:02:39 +0000 http://www.paolocorti.net/?p=151#comment-62853 Paolo, REST is an architectural style and involves constraints that don't crop up at all in the process of querying a network geocoder. One request does not an architecture make. GeoPy makes a HTTP GET request. That's all. Paolo, REST is an architectural style and involves constraints that don’t crop up at all in the process of querying a network geocoder. One request does not an architecture make. GeoPy makes a HTTP GET request. That’s all.

]]> By: Paolo Corti http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62836 Paolo Corti Wed, 14 Oct 2009 13:56:41 +0000 http://www.paolocorti.net/?p=151#comment-62836 Hi Sean, just to be sure: you mean it is not REST because it is not implement a hierarchy in the URL or because the otput format is specified in the query string? Because the data is read here, and the GET request make senses here in the REST point of view. Hi Sean, just to be sure: you mean it is not REST because it is not implement a hierarchy in the URL or because the otput format is specified in the query string? Because the data is read here, and the GET request make senses here in the REST point of view.

]]> By: Sean Gillies http://www.paolocorti.net/2009/10/14/geocoding-with-geopy/comment-page-1/#comment-62831 Sean Gillies Wed, 14 Oct 2009 12:52:51 +0000 http://www.paolocorti.net/?p=151#comment-62831 Well, HTTP *GET*, not REST, but yes, geopy is neat. I also like seeing virtualenv in the mix. Well, HTTP *GET*, not REST, but yes, geopy is neat. I also like seeing virtualenv in the mix.

]]>