DATAtourisme

Assistance with Integrating DataTourisme API into Our Platform

Hello everyone,

I hope this message finds you well. I’m reaching out because my team and I are currently working on integrating the DataTourisme API into our tourism-related platform. We’re aiming to provide users with dynamic, up-to-date data about local events, accommodations, and attractions. However, we’ve encountered a few challenges, and I was hoping to get some insights or advice from the community.

  1. Filtering Data by Region: Is there a straightforward way to filter the data so that it only retrieves information specific to a particular region? The API documentation provides general guidance, but I couldn’t find a detailed example for this specific use case.
  2. Managing Large Data Volumes: While testing, we noticed that fetching a lot of data at once slows down the performance of our platform. Has anyone implemented a system to manage large data sets efficiently, perhaps by caching or using background processing?
  3. API Rate Limits: Are there any best practices for handling API rate limits without causing disruptions for end users?

We’ve been referencing the official documentation and experimenting with different approaches, but additional perspectives or real-world solutions would be invaluable.

I check this: https://support.datatourisme.fr/t/question-agregation-datatourisdevops But I have not found any solution. Could anyone guide me about this? If you’ve tackled similar issues or have experience working with the DataTourisme API, I’d greatly appreciate your input. Feel free to share code snippets, strategies, or general advice. Thank you in advance for your help!

Looking forward to hearing from you.

1 « J'aime »

Hi @Skrak_GEVATAV
You can edit your sparql request generated in https://diffuseur.datatourisme.fr/ on the export mode and then get the used properties to query by regions
example :
CONSTRUCT {
?res http://www.w3.org/1999/02/22-rdf-syntax-ns#type urn:resource.
} WHERE {
?res http://www.w3.org/1999/02/22-rdf-syntax-ns#type https://www.datatourisme.fr/ontology/core#PointOfInterest.
?res https://www.datatourisme.fr/ontology/core#isLocatedAt ?61f14e39.
?61f14e39 http://schema.org/address ?e2dc5ce6.
?e2dc5ce6 https://www.datatourisme.fr/ontology/core#hasAddressCity ?2b7e3a94.
?2b7e3a94 https://www.datatourisme.fr/ontology/core#isPartOfDepartment ?41508c7e.
?41508c7e https://www.datatourisme.fr/ontology/core#isPartOfRegion ?318431bf.
VALUES ?318431bf {
https://www.datatourisme.fr/resource/core#France84
https://www.datatourisme.fr/resource/core#France44
}
}

You can find the regions list on the Ontology Git space : thesaurus · master · ADNtourisme / DATAtourisme / ontology · GitLab
The file is insee.ttl
Regards
Jean