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

[rcavaliere]

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

• OSM, address, etc.
• OTP (objects of transportation services)
• Open Data Hub - tourist POIs

[ch-routerank]

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]

@ch-routerank Sure, we can have a chat. Just shoot me a mail at [email protected] and we'll set something up.

[rcavaliere]

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

Reference API calls:

• Accomodations (hotels):
  https://tourism.api.opendatahub.com/v1/STA/Accommodation?language=en&referer=SuedtirolMobilWeb&fields=Id%2CAccoDetail.en.Name%2CAccoDetail.en.City&pagesize=10000
• Andere POIs: https://tourism.api.opendatahub.com/v1/STA/ODHActivityPoi?language=en&referer=SuedtirolMobilWeb&fields=Id%2CDetail.en.Title%2CContactInfos.en.City&pagesize=20000

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.:

• https://tourism.api.opendatahub.com/v1/ODHActivityPoi/smgpoi107?language=en&referer=SuedtirolMobilWeb
• https://tourism.api.opendatahub.com/v1/Accommodation/5CEA544EE34639034F07B79D4AEEB603_REDUCED?language=en&referer=SuedtirolMobilWeb

[rcavaliere]

@clezag @ch-routerank @nl-routerank can you please get in contact on that topic, so that we can start configure this?

[ch-routerank]

Hello, my colleague finished the initial version setup and I've started to test it. I'll create a PR for this as soon as possible. It'll be easier to discuss on this basis.

[ch-routerank]

Please see #216

[ch-routerank]

When hooked with the web-demo, here's some example search outputs:

Merano while the map is focused on Bolzano shows "merano related" station in Bolzano:

Closer to Merano, Merano Stazione comes first, the more important the stations the higher in the list also:

Here's Bolzano airport result, however in OTP it doesn't have the full airport name and this could potentially be improved.

Here's a couple example POI, label could be potentially improved as there are some rather large poi names as well as potentially lowercase/uppercase issue. This could likely be improved as post processing.

The way the data has been inserted in Pelias already makes this split station/other that we discussed

For addresses, the content is properly integrated to, I see however some duplication between openstreetmap streets and openaddresses (one seems to have them in IT-DE language which seems to disturb pelias deduplication mechanism)

here's an example duplicated entry

[rcavaliere]

@ch-routerank @nl-routerank as discussed today, following tasks are the main ones to be considered for the next steps:

• work on addresses duplicated in OSM (@ch-routerank @nl-routerank) [warning: consider multilingual fields!]
• improve quality of flight metadata (@rcavaliere) in GTFS export (i.e. names of airports are provided as codes)
• set up Pelias enviroment in Open Data Hub instance with @clezag

For the first MVP related to the other front-end developments (see #210 (comment)) we have agreed to have a PR of the application to a routeRank Pelias implementation, so to avoid to have this dependency for integrating the new application version in our environment.