search

noi-techpark / odh-mentor-otp

5 stars 8 forks source link

As end-user I would like to have a geocoding mechanism implemented #209

Open rcavaliere opened 1 month ago

rcavaliere commented 1 month ago

This user story deals with the implementation of the geocoding service, to be implemented to a Pelias implementation. To be considered as sources:

ch-routerank commented 1 month ago

As discussed, @rcavaliere could you provide us with the example Touristic API POI endpoint we can use for this?

@clezag could we have a quick chat for the deployment/infra for the Pelias services? Ideally it should be based on https://github.com/pelias/docker with a new project configuration such as these: https://github.com/pelias/docker/tree/master/projects for the region.

The base repository provides the pelias cli tool that helps maintaining a docker-compose setup for the elasticsearch backend, the various pelias services as well as the various importations pipeline.

We would also provide at least two custom scripts and pelias/csv-importer configuration for the importation pipeline to import the touristic POI as well as the mobility points from OTP. The repository can be used as-is for a local setup but you might want to have potentially some different configuration in production. Happy to discuss this with you

clezag commented 4 weeks ago

@ch-routerank Sure, we can have a chat. Just shoot me a mail at c.zagler@noi.bz.it and we'll set something up.

rcavaliere commented 3 weeks ago

@ch-routerank here the information about the POIs we should integrate in this geocoding module.

Reference API calls:

With these API calls it is possible to have the full list of POI. Each POI can be then specifically requested with a different API, in order to get the reference coordinates, e.g.: