The Calls to open Data Hub Tourism (/api/ODHActivityPoi) to get the matched POI are done with Radius 50.000 metres ;) That is a bit high, i now have a lot of data in this table and the performance of the call is very slow, i think you can set the Radius to 500, or maximum of 1000 ........ Setting the radius at 500m it can occur that no POI will be returned (check it in the code).......... i think this is better than showing a wrong poi that is distant kilometers .
Hi Daniel
The Calls to open Data Hub Tourism (/api/ODHActivityPoi) to get the matched POI are done with Radius 50.000 metres ;) That is a bit high, i now have a lot of data in this table and the performance of the call is very slow, i think you can set the Radius to 500, or maximum of 1000 ........ Setting the radius at 500m it can occur that no POI will be returned (check it in the code).......... i think this is better than showing a wrong poi that is distant kilometers .
I mean this code
export async function getNearestTourismPOI(latitude, longitude) { var url = 'https://tourism.opendatahub.bz.it/api/ODHActivityPoi?latitude={{LAT}}&longitude={{LNG}}&radius={{RDS}}' url = url.replace('{{LAT}}', latitude) url = url.replace('{{LNG}}', longitude) url = url.replace('{{RDS}}', 50000)
thanks, Rudi