geo:json for everyone about ngsi-timeseries-api HOT 2 CLOSED

some pointers that could be useful:

• https://github.com/DenisCarriere/geocoder
• https://github.com/datasets/geo-nuts-administrative-boundaries/tree/master/data

let's suppose that for some data we can do this in a easier way

for example, for country names and country codes, we could create a separate table
with the associated geo:json, and when running ngsi geo queries, do a merge on the field in the background.

for things like street address, we would definitively need a geocoding service but then, instead of querying the service every time i would cache the data

in relation to NGSI Data Models, when you import the Location-Commons definition in a schema, that schema will have geo:json and/or address, address object includes properties that allows us for some resolution, so if you have only addressCountry, we would do a resolution based on table merge (see above), if it has also an addressStreet, we would use an external service to obtain a geo:point
and cache it.
similar approach for entities with only these fields would be possible:

"addressLocality": {
   "type": "string"
},
"addressRegion": {
   "type": "string"
}, 

from ngsi-timeseries-api.

First version of this already implemented.

from ngsi-timeseries-api.