forked from geopy/geopy
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
277 lines (177 loc) · 9.64 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
0.99 - March 18, 2014
=====================
ADDED: GeocodeFarm geocoder added with support for geocoding and reverse
geocoding. Contributed by Eric Palakovich Carr.
0.98.3 - March 7, 2014
======================
ADDED: Queries are encoded as unicode in Python 2.7 by the geocoder.
Contributed by Rocky Meza.
FIXED: YahooPlaceFinder `count` parameter fixed.
FIXED: Point.__repr__ fixed. Contributed by Paweł Mandera.
0.98.2 - February 28, 2014
==========================
ADDED: GoogleV3 now accepts an `api_key` parameter. Contributed
by Andrea Tosatto.
CHANGED: GoogleV3's deprecated `protocol` argument has been removed.
0.98.1 - February 22, 2014
==========================
FIXED: Mapquest geocoder did not use format_string in the creation
of its queries. Contributed by Danny Finkelstein.
FIXED: Geocoders incorrectly raised a GeocoderTimedOut exception for all
`SSLError` exceptions. Contributed by David Gilman.
0.98 - February 5, 2014
=======================
CHANGED: Geocoders' `geocode` and `reverse` method return types have changed
from None, a tuple, or a list of tuples, to None, a `geopy.Location`
object, or a list of `geopy.Location` objects.
`Location` objects can be iterated over the same as
the previous tuples for backwards compatibility, returning
(address<String>, (latitude<float>, longitude<Float)).
`geopy.Location` objects also make returned data available as
properties. Existing attributes are `address`, `longitude`, and
`latitude`. Now available are the geocoder's raw response as `raw`,
and the location's altitude as `altitude`.
0.97.1 - February 1, 2014
=========================
FIXED: YahooPlaceFinder geocoder authentication and response parsing fixed.
Contributed by petergx.
ADDED: GoogleV3 geocoding now supports a `components` parameter, which
is a filter for location criteria such as administrative area,
country, etc. Contributed by crccheck.
0.97 - December 26, 2013
========================
CHANGED: SSL connections are used by default for services with support.
These geocoders accept a new 'scheme' argument in their init,
which may be 'https' or 'http'. Users desiring unencrypted
connections must now specify 'http'. Note that SSL connections'
certificates are not verified.
CHANGED: Geocoders accept a `timeout` argument which specifies the number of
seconds to wait before raising a `GeocoderTimedOut` exception. This
can be specified in the init, or specified one-off in each `geocode`
or `reverse` call. There is now a default of 1 second.
CHANGED: geopy now supports Python 2 and Python 3 on a single codebase.
Support for Python 2.5 is also dropped.
CHANGED: GoogleV3's `protocol` argument is deprecated in favor of `scheme`.
ADDED: ESRI's ArcGIS geocoder implemented. Contributed by Arsen Mamikonyan.
ADDED: Geocoders accept a `proxies` argument which specifies a proxy to
route its geocoder requests through. It uses urllib, and accepts
proxies in the form of a dictionary of {scheme: proxy address}, e.g.,
{"https": "192.0.2.0"}. This was present but undocumented in 0.96.
ADDED: Geocoders check a new method, `_geocoder_exception_handler`, if
defined, when the HTTP call to the geocoder's service raises an
exception. See LiveStreets for an example. Users can define or
override this method.
ADDED: LiveStreets throws a `GeocoderQuotaExceeded` exception when
appropriate.
ADDED: `Point` can parse a greater variety of coordinate strings. Contributed
by nucflash.
FIXED: GeocodersDotUS now authenticates with an `Authorization` HTTP header.
Contributed by Arsen Mamikonyan.
REMOVED: MediaWiki and SemanticMediaWiki geocoders removed.
REMOVED: Geohash module has been removed.
0.96.3 - December 26, 2013
==========================
ADDED: Documentation warning that the Vincenty distance implementation fails
to converge for some valid points. Reported by mkeller-upb.
FIXED: Geocoder proxying fixed. Contributed by Marc-Olivier Titeux.
0.96.2 - November 20, 2013
==========================
FIXED: MANIFEST.in exclusions broke builds under `buildout`. Contributed by
James Mills.
0.96.1 - October 31, 2013
=========================
FIXED: GoogleV3 returns `None` when the service returns an error status of
`ZERO_RESULTS`. Contributed by Ian A Wilson.
0.96 - October 25, 2013
=======================
CHANGED: GoogleV3's reverse geocoder now returns one result by default. Set
`exactly_one` to False for a list.
CHANGED: GoogleV3 returns new exception types:
`geopy.geocoders.base.GQueryError` -> `geopy.exc.GeocoderQueryError`
`geopy.geocoders.base.GeocoderResultError` -> `geopy.exc.GeocoderQueryError`
`geopy.geocoders.base.GTooManyQueriesError` -> `geopy.exc.GeocoderQuotaExceeded`
ADDED: OpenStreetMap Nominatim geocoder implemented. Contributed by
Alessandro Pasotti.
ADDED: Yahoo! BOSS Geo PlaceFinder geocoder implemented. Contributed by
jhmaddox and Philip Kimmey.
ADDED: SmartyStreets LiveAddress geocoder implemented. Contributed by
Michael Whatcott.
ADDED: GeoNames geocoder is implements GeoNames' new username
requirement and `api.geonames.org` endpoint. Contributed by David
Wilson and Benoit Grégoire.
ADDED: Bing geocoder supports `user_location` (`Point`) parameter. Bing will
prefer results near the coordinates of `user_location`. Contributed by
Ryan Nagle.
FIXED: `GoogleV3.geocode_first()` no longer throws exception on multiple
results. Contributed by migajek.
FIXED: Unnecessary coercing to UTF-8 on Py3k. Contributed by akanouras.
FIXED: `format_degrees` now rounds minutes properly. Contributed by avdd.
FIXED: No longer warn if the optional dependency `BeautifulSoup` is
not present.
FIXED: Miscellaneous inconsistent behavior and errors in geolocating.
REMOVED: Google V2 geocoder has been removed as its API was shutdown.
0.95.1 - March 22, 2013
=======================
FIXED: Fix #12, where `DeprecationWarning` was showing for GoogleV2 even if
it wasn't being used (due to `geopy.geocoders` importing it).
Contributed by Dave Arter.
CHANGED: `GoogleV3.geocode` "address" kwarg renamed to "string" to match
`Google.geocode` to make updating easier.
FIXED: Geocoders now properly handle Unicode objects as input (previously
would fail on non-ASCII characters due to wanting UTF-8 strings).
0.95 - March 12, 2013
=====================
ADDED: Google Geocoding API V3 support. Contributed by Jordan Bouvier
(jbouvier). "google.Google()" should be replaced by
"googlev3.GoogleV3()", with no `api_key`.
Please see http://goo.gl/somDT for valid arguments.
UPDATED: setup.py updated to now automatically support Python 3+ (via 2to3
auto-compile option). Contributed by Feanil Patel.
0.94.2 - March 12, 2012
=======================
ADDED: MANIFEST.in so that LICENSE file gets included in dist packages
(per req by Debian Python Module Team)
UPDATED: Yahoo geocoder uses new PlaceFinder API instead of outdated
MapsService V1 API.
0.94.1 - March 24, 2011
=======================
ADDED: Test suite includes geocoding tests for the Google, Bing, Yahoo,
GeocoderDotUS, and GeoNames geocoders.
CHANGED: `output_format` is deprecated in backends that used it.
FIXED: Bing geocoder now works properly. Updated to use the JSON return
method rather than XML. `output_format` has always been ignored
and is now deprecated.
FIXED: GeocoderDotUS now works properly. Updated to use more compact CSV
return method rather than XMLRPC.
CHANGED: Yahoo geocoder now uses the "old" tuple return format
(address, (lat, lon)) rather than the undocumented Location()
object, for API consistency. (Object return values with rich
data will be implemented in a future release.)
FIXED: Issue 40. Fixed "print" statement in Bing backend. No more
print statements remain.
FIXED: Issue 39. In addition to checking for system `json` and `simplejson`,
geopy now looks for a system-installed `django` (which bundles a
copy of simplejson).
FIXED: Issue 45. Implement __cmp__ on Distance so that distance objects may
be compared against one another.
CHANGED: Added __repr__ and __str__ to Distance
ADDED: Issue 46. Geocoder backend for MapQuest's OpenMapQuest API,
contributed by Shashwat Anand.
0.94 - March 7, 2010
====================
ADDED: Partial test suite can now be run via "setup.py test"
FIXED: Issue 5. Converted "print" statements to logger calls to
allow compatibility with WSGI.
FIXED: Issue 16. Google geocoder backend now throws more descriptive
exceptions on certain failure statuses.
FIXED: Issue 18. Add simplejson to install_requires for setup. Use
native (Python 2.6+/3.0+) json module if available.
FIXED: Issue 21 and Issue 25. Distance calculations for values beyond
180/-180 and 90/-90 now wrap instead of raising an error.
FIXED: Issue 22. Fixed string representation of Point objects so
that they don't throw an exception.
FIXED: Issue 23. Fixed GreatCircleDistance ValueErrors due to floating
point precision on extremely close points.
Changes between 0.93 (October 8, 2006) and February 15, 2009
============================================================
See https://github.com/geopy/geopy/compare/0451a051...ffebd5f3