In this field it was decided to realize a common elaboration for Point Of Interest (POI) analysis, fulfilled by the dataset identified by each partner and processed in a common structure to made them available through unique API access.
This schema describes the six different entity in which will be stored all the information about the POIs analysis, that will gather and distribute the information in these six different tables:
1. Source Dataset metadata: This table will describe the information about the dataset, like the name in original language, the URL where it can be accessible, the partner that selected them, ecc.
2. POI: This table will comprehend all the information about the description about the POIs, that will include the name, the type of place, the contact information, ecc.
3. Location: This table will localize the different POIs in a specific way, that could be an address described in a textual description or coordinate where it can be found.
4. Category: This table will be used to “standardize” the different information coming from the partner to a common format, that will be articulate in a two-level description to identify all the different type of POI that this project identifies.
5. Category Source: This table will be used in case the partner identify that all the POIs present in a specific dataset are of the same category. This will be used to “filter” the POIs information for one or more specific category (e.g. Hotel, Camping, ecc).
6. Category POI: This table will be used in case the partner identify that all the POIs present in a specific dataset can have a different category, identified for each of them. This will be used to “filter” the POIs information for one or more specific category (e.g. Hotel, Camping, ecc).
Each partner identified what datasets will be relevant and for each of them identified what specific columns will fulfil the requirement for the different tables describe before.
Starting from this analysis, it was added to them all the correct references in each table to make possible to join the different information correctly. These references are:
· A specific ID for each table (id_poi, id_category, id_location, ecc).
· (possible) ID for other tables. In case this reference is present, this one can be “joined” to the columns with the same name in the other table to have all the information elaborated (e.g. to have both the information about the POI description and his location, it is needed to “join” the table Location with the table POI on the columns id_poi, that both of them have).
Currently we received the correct documentation and agreement from Vercelli, Grand E Nov and Veneto, that are already processed and available. For Tour Data we are currently working some detail about the documentation required, but as soon as it will be completed the preparation process will be completed.
The partner involved into this pilot are Veneto, Vercelli and Grand Eno.
Below is the list of datasets for each partner to obtain the final data model:
In this project were realized in Open Data different datasets, accessible through APIs described in the following paragraph.
These datasets are published with the following information:
· Open Data License: CC BY 4.0
· Author: Grand E-nov, Biz-Up, Comune di Vercelli and Regione Veneto
· Dataset RightHolder: Grand E-nov, Biz-Up, Comune di Vercelli and Regione Veneto
· Dataset creator: CSI-Piemonte
· Organization name: CSI-Piemonte
· Organization email: firstname.lastname@example.org
This APIs will be in OData V2 format. Using his query language, it is possible to access all the data currently processed.
Some of the API that are below are limited to the first 15 row, but if more information are needed can be modify directly the condition of the query to obtain a different result (a short tutorial can be found here: https://www.odata.org/getting-started/basic-tutorial/).