River unions by commune — Département du Loiret

Open data API in a single place

Provided by Département du Loiret

Get early access to River unions by commune — Département du Loiret API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.02.15 23:00
Created
Available languages
English
Keywords
environnement-loiret, reseaux-humides, hydrographie
Quality scoring

Dataset description

Membership of a commune in one or more river unions in the Loiret **Collection context** A river union is an EPCI and is competent for the consistent management of a river and its tributaries over all or part of a watershed. The actions carried out include ensuring the free flow of water while preserving biodiversity (restoration of the environment, maintenance work, etc.), respecting water uses and rights while transcribing national and European guidelines on the ground. **Collection method** The layer “syndicates of rivers per commune” is built from the common layer of the IGN BDTopo. In the Loiret, a municipality may belong to 0, 1 or 2 trade unions. Also, the winning table is structured to provide all the useful information of one or two trade unions. A field “SYN1_SYN2” summarises a commune’s membership of one or two trade unions. The database is fed by the publication of orders for the creation, dissolution or modification of the perimeter of a trade union. Please note: a municipality may belong to two trade unions. The database also has duplicated fields. **Attributes** | Champ | Alias | Type | | — | — | | — | | ‘CODE_INS_N’ | Digital INSEE Code | ‘double’ | | ‘SYNDICAT1’ | Trade Union Name | ‘char’ | | ‘COURS_EAU’ | Watercourses | ‘char’ | | ‘VILLE2’ | Common 2 | ‘char’ | | ‘BASSIN_1’ | Basin Agency | ‘char’ | ‘BASSIN_1’ | ‘OVERRIDE’ | ‘blob’ | | ‘NOM_SYND’ | Acronym | ‘char’ | | ‘DATE_MAJ’ | Update Date | ‘date’ | | ‘TITRE_PR_1’ | Title President 2 | ‘char’ | | ‘CODE_POSTA’ | Postal code | ‘double’ | | ‘PRESIDENT2’ | President 2 | ‘char’ | | ‘SHAPE.AREA’ | ‘double’ | | ‘MAIL_TECH2’ | Technician Mail 2 | ‘char’ | | ‘SYND_1’ | Short union | ‘char’ | ‘SYND_1’ | ‘ADR_TECH2’ | Technician Address 2 | ‘char’ | | ‘PRESIDENT’ | President | ‘char’ | ‘PRESIDENT’ | | ‘MAIL_TECH’ | Technician Mail | ‘char’ | | ‘CODE_INSEE’ | INSEE Code | ‘char’ | | ‘TEL_TECH’ | Technician Phone | ‘char’ | ‘TEL_TECH’ | ‘SHAPE.LEN’ | ‘double’ | | ‘VILLE’ | Common | ‘char’ | ‘City’ | ‘RULEID’ | ‘integer’ | | ‘BASSIN_2’ | Basin Agency 2 | ‘char’ | ‘BASSIN_2’ | | ‘TECH_BIS’ | Other Phone | ‘char’ | | ‘Secretaria’ | Secretariat | ‘char’ | ‘Secretaria’ | ‘ObjectID’ | ‘double’ | | ‘NOM_SYND2’ | Acronym | ‘char’ | | ‘SECRETAR_1’ | Secretariat 2 | ‘char’ | | ‘TECHNICIAN’ | ‘char’ | | ‘NOM_MAJ’ | Common | ‘char’ | ‘NOM_MAJ’ | | ‘TEL_SECR2’ | Telephone secretariat 2 | ‘char’ | | ‘TITRE_PRES’ | Title President | ‘char’ | | ‘TEL_SECR’ | Phone Secretariat | ‘char’ | ‘TEL_SECR’ | | ‘FAX_SECR’ | Fax secretariat | ‘char’ | | ‘ADR_SYND’ | Address | ‘char’ | ‘ADR_SYND’ | | ‘ADR_TECH’ | Technician Address | ‘char’ | ‘ADR_TECH’ | ‘CODE_POS_1’ | Postal Code 2 | ‘double’ | | ‘COORD_PRES’ | President Contact Information | ‘char’ | | ‘TEL_TECH2’ | Technician Phone 2 | ‘char’ | | ‘MAIL_SECR’ | Mail Secretariat | ‘char’ | | ‘OBJECTID_1’ | ‘integer’ | | ‘TECH_B2’ | Other Technicians 2 | ‘char’ | | ‘SUPERFICIE’ | ‘double’ | | ‘COORD_PR_1’ | President’s contact details 2 | ‘char’ | | ‘TECHNICI_1’ | Technian 2 | ‘char’ | | ‘FAX_SECR2’ | Fax secretariat 2 | ‘char’ | | ‘ADR_AUTRE’ | Additional address | ‘char’ | ‘ADR_AUTRE’ | | ‘SYND_2’ | Short union | ‘char’ | ‘SYND_2’ | ‘MAIL_SECR2’ | Secretariat Mail 2 | ‘char’ | | ‘ADR_AUT2’ | Add address 2 | ‘char’ | ‘ADR_AUT2’ | | ‘NOM_MIN’ | Common | ‘char’ | ‘NOM_MIN’ | ‘ADR_SYND2’ | Address 2 | ‘char’ | | ‘SYN1_SYN2’ | Trade Union(s) Name | ‘char’ | | ‘SYNDICAT2’ | Union Name | ‘char’ | ‘SYNDICAT2’ For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/1742fb942d7b4756b9778c3b3cbc992e/HWglEr-z4Bry_rKQOTINX9gAH4Yu0/r/8a0e35b907fa4d448a599c8aefb7e4ed).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks