This layer of data locates the organisations 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 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 considered a localised “container” (by an address and geographical coordinates) to which an “activity” described by an organisation (content) is bound.
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_organism: Identifier of the organisation
name_Use: Name of the organisation
abbreviation: Abbreviation of the organism
web: URL of the organisation’s internal website
etat_organisation: Status of the organisation (active/inactive/project)
comments: Commentary
description: Description of the organism
code_nomenclature_main: Nomenclature (Identifier of the attached main branch)
name_theme_main: Nomenclature (name of the attached theme)
main_Activity_Name: Nomenclature (name of activity attached)
name_specialite_main: Nomenclature (name of the speciality attached)
code_nomenclature_secondary: Nomenclature (Identifier of other branches attached)
id_site_main: Identifier of the main site to which the organisation relates (if empty, organisation without location = telephone number, site outside of Rennes...)
name_site_main: Name of the site to which the organisation is attached (if empty, organisation without location = telephone number, site outside of Rennes...)
id_site_pere: Identifier of the parent site to which the organisation relates
name_site_pere: Name of the parent site to which the organisation relates
code_insee: INSEE of the municipality where the main site linked to the organisation is located (if empty, organisation without location = telephone number, site outside of Rennes...)
address_postal_adr: Postal address
address_postal_bp_cs: Post Box/Special Course
address_postal_cp: Postal code
address_postal_comm: Name of the municipality
address_postal_cedex: Cedex
name_pvci: Name of the organisation on the Plan de Ville Communal et Intercommunal de Rennes Métropole
keyword: Associated Keyword(s)
is_main_organism: Indicates whether the organism is the main body associated with a site (attributes the nomenclature to the site)
e-mails: Email address(s) attached to the organisation
telephones: Telephone number(s) attached to the organisation
index_level: Body level (0 by default)
information_times: general information on the organisation’s schedules
schedule_grid: days and opening hours of the organisation
day_periode_farm: days and/or periods of closure of the organisation
variation_curricular_conges_: if so, the days and times indicated in the schedule_grid field may vary during school holidays
com_closure_conges: additional information concerning the days and periods of closure of the organisation
days_excep_farms: known exceptional closing days
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.