This layer of data locates the sites contained in the Sites & Organisations database managed by the Rennes Métropole services. In the long term, other actors will be able to contribute to the updating of this database (territorial communities, equipment managers, association...).
This layer is the result of merging 3 layers of data that were managed by 3 different services. To streamline their management and pool updating efforts, it was decided to consolidate them into a single database (the Sites & Organisations database) and to put in place an appropriate management tool.
The Sites & Organisations database aims to bring together public, semi-public and private facilities receiving the public as well as many associations that use them on the scale of Rennes Métropole. The Sites & Organisations described may also be provided with business data specific to the profile of these different contributors.
A “site” is a “container” geographically located (by an address and geographical coordinates) to which is bound a “activity” described by an organisation (content).
Where a site is not limited to a building but is represented by a large area (e.g. sports complex, university, hospitals...), the notion of “father site” is used.
An “organisation” represents an “activity” specified by a description, nomenclature, keywords, schedules and, where applicable, business data. Its location will result from its association with a site.
An organisation may not have a linked site (no location) when it comes to a phone number, a website...
Description of the fields awarded:
id_site: Site ID
name_site: Site name
name_pvci: Name of the site used on the Plan de Ville Communal et Intercommunal de Rennes Métropole
etat_site: Site Status (active/inactive/project)
id_level_site: Level (0 by default)
id_site_pere: Identifier of the father site
name_site_pere: Name of site father
id_org_main: Main Organizational Identifier
name_org_main: Name of the main organism
id_theme_main: Nomenclature (linked theme identifier)
name_theme_main: Nomenclature (name of the attached theme)
id_activity_main: Nomenclature (linked activity identifier)
main_Activity_Name: Nomenclature (name of activity attached)
id_specialite_main: Nomenclature (identifying the speciality attached)
name_specialite_main: Nomenclature (name of the speciality attached)
name_org_Secondary: Name of organisation(s) associated with the site
Access to the nomenclature is available below in the metadata.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.