Update NEWS.md
This commit is contained in:
37
NEWS.md
37
NEWS.md
@@ -1 +1,38 @@
|
||||
Feb 26, 2016: https://github.com/CartoDB/dataservices-api/releases/tag/0.4.0-server
|
||||
===========
|
||||
Feb 11, 2016: https://github.com/CartoDB/dataservices-api/releases/tag/0.3.0-server
|
||||
===========
|
||||
* Release server 0.3.0
|
||||
* Extension refactor, now is called cdb_dataservices_[client|server] in order to include more services aside the geocoder.
|
||||
* Add logic to save the metrics for the internal geocoder services as we have for the nokia and google geocoders
|
||||
* Trimmed all the inputs to avoid empty results
|
||||
|
||||
Feb 4, 2016: https://github.com/CartoDB/dataservices-api/releases/tag/0.2.0-server
|
||||
===========
|
||||
* Release server 0.2.0
|
||||
* Logic for the google geocoder so the users with this geocoder setted up can use street level geocoding too
|
||||
* Refactor of the python library in order to reflect the change to a services extension more than only geocoder
|
||||
|
||||
Jan 25, 2016: https://github.com/CartoDB/dataservices-api/releases/tag/0.1.0
|
||||
===========
|
||||
* Release Geocoder API 0.1.0
|
||||
* Street geocoding available through the cdb_geocoder_street_point_v2 function (only working Heremaps geocoder)
|
||||
* User config comes from Redis database
|
||||
* Increment of usage metrics for the cdb_geocoder_street_v2
|
||||
|
||||
Jan 25, 2016: https://github.com/CartoDB/dataservices-api/releases/tag/0.0.1
|
||||
===========
|
||||
* Release Geocoder API 0.0.1 production ready
|
||||
|
||||
Dec 23, 2015: https://github.com/CartoDB/dataservices-api/releases/tag/0.0.2
|
||||
===========
|
||||
* Release Geocoder API 0.0.2 beta
|
||||
|
||||
Dec 3, 2015: https://github.com/CartoDB/dataservices-api/releases/tag/0.0.1-beta2
|
||||
===========
|
||||
* Release Geocoder API 0.0.1 Beta2
|
||||
|
||||
Nov 27, 2015: https://github.com/CartoDB/dataservices-api/releases/tag/0.0.1-beta
|
||||
===========
|
||||
* Release Geocoder API BETA 1
|
||||
* Added the organization public user to the api key check
|
||||
|
||||
Reference in New Issue
Block a user