Itineraries and cycle loops of the Gard

Open data API in a single place

Provided by etalab

Get early access to Itineraries and cycle loops of the Gard API!

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

Dataset information

Country of origin
Updated
2022.10.31 00:00
Created
2022.08.30
Available languages
French
Keywords
deplacement, cyclable, gard, velo
Quality scoring
205

Dataset description

The Gard department maintains a repository of cycle loops and routes developed in its territory. This allows in particular to feed the [Observatoire National des Véloroutes (ON3V)](https://www.velo-territoires.org/observatoires/observatoire-national-des-veloroutes-et-voies-vertes/) in connection with [Vélo et Territoires](https://www.velo-territoires.org/lassociation/presentation/). The structure of the database is a subset of [geo-standard Véloroutes and Green Ways](http://www.geoinformations.developpement-durable.gouv.fr/geostandard-veloroutes-et-voies-vertes-3v-v1-0-a2715.html). As such: * a route consists of bicycle portions, * a portion is built by assembling cycle segments, * a segment has several attributes informing, among others, about its status (VV — Green Way, PCY — Cyclable Track, RTE — Road, etc.) and its coating (LIS — Slow, RUG — Rugueux, MEU — Furniture). To build this database, the department relies essentially on the geometries of the [BD Topo® of IGN](https://geoservices.ign.fr/bdtopo) and more specifically the class ‘troncon_of_route’. This dataset is an extraction of the repository. It gives, by loop and route, the open cycle segments. In addition to their geometry, the segments have the following attributes: * ‘NumeroItinerary’: the number of the cycle route in which the segment participates * ‘NameItinerary’: the name of the cycle route in which the segment * ‘NamePortion’ participates: the name of the cycle portion in which the segment * ‘TypePortion’ participates: the type indicates whether the portion is a _Etape_ of the route, if it is a _Provisional Port_ pending the opening of the final route or if the route is a _Variante_ of the main route * ‘StatutSegment’: the status of the segment (Green Way, Cycling Track, Road, etc.) * ‘RevetementSegment’: the type of coating of the segment (Smooth, Rugueux, Furniture) * ‘SensUniqueSegment’: indicates whether the traffic on the segment is one-way * ‘SourceGeometrieSegment’: the source of the geometry is predominantly ‘bdtopo.troncon_de_route’ * ‘IdGeometrieSegment’: the identifier of the geometry in the source It also gives for each segment: * ‘EstimationDNegatifSegment’: an estimate of the negative elevation of the segment according to its direction of digitisation * ‘EstimationDPositifSegment’: an estimate of the positive elevation of the segment according to its sense of digitisation The quality of these estimates depends directly on the altimeter information of the source geometries of the segments. It should be noted that the loops and routes identified by this repository are not only those managed by the Gard department. Other public actors (EPCI, communes, PETR) can indeed be at the initiative of the creation of cyclo-discovered loops contained in this framework. The resources associated with this dataset are updated at least every quarter to match the vintage versions of the Topo® BD. More ad hoc updates can also be made when new portions are put into service. Additional information available on the Gard website: [https://www.gard.fr/au-quotidien/optimiser-vos-deplacements/les-voies-vertes-dans-le-gard.html](https://www.gard.fr/au-quotidien/optimiser-vos-deplacements/les-voies-vertes-dans-le-gard.html).
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks