Releases: CartoDB/dataservices-api
Releases · CartoDB/dataservices-api
Log for geocoding, refactor and renaming of old functions
- Renamed the python library metrics functions
- Create old version's folder to store the last versions
- Refactor: Move redis and DB config logic to the python library
- Generate the metrics log file
Mapzen routing capabilities
- Mapzen routing functions to calculate a route point to point
- Use of Sentinel transparently
Mapzen routing capabilities
- Added cdb_routing_point_to_point function using Mapzen as provider
[Server] Routing isolines
- Added routing isolines capabilities
[Client] Routing isolines
- Added routing isolines capabilities to the client and public API
Internal api metrics and refactor
- 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
Google geocoder
- 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
Geocoder API
- 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
Geocoder API
0.0.1 Current version 0.0.1 in production
Geocoder API beta 1
0.0.1-beta Added the organization public user to the api key check