| Version 20 (modified by cedric, 15 years ago) (diff) |
|---|
back to first page ..
Obstacle pressure
The obstacle pressure (characteristics, Steinbach rank…) comes from the National list of obstacles to river flows (ROE) from the ONEMA
The data set are in two database : ROE and MIGANG
Describing the ROE database
To download and load the data into postgreSQL you must follow ROE download and load
The data referential is here : http://sandre.eaufrance.fr/spip.php?article695&id_rubrique=177
Extract the data within the french boundaries
- With ArcGis
Use the french limits (see French boundaries) in RGF93
In !QuantumGis, connect the ROE database and add the obstacle_referentiel layer
Clic right on the layer "Sauvegarder comme shapefile" with Fichiers de type : Shapefiles (*.shp), Codage=UTF-8 > ok
and choose "Système de coordonnées de référence" = RGF93/Lambert93 (because the french boundary layer is in this system).
In !ArcGis, add the two layers :
- ROE_EDA.shape
- GEOFLADept_FR_Corse_AV_L93\DEPARTEMENT.shp
Use Analysis Tools > Extract > Clip
Input Features : ROE_EDA
Clip Features : DEPARTEMENT
If you want you can choose a "XY Tolerance", because some points in the ROE are in France but they are at the limit.
(maybe 300meters?).
- With QGis
You have to reproject the data
C:\
OSGeo4W\bin\ogr2ogr -- help
Usage: ogr2ogr [--help-general] [-skipfailures] [-append] [-update] [-gt n]
[-select field_list] [-where restricted_where]
[-sql <sql statement>]
[-spat xmin ymin xmax ymax] [-preserve_fid] [-fid FID]
[-a_srs srs_def] [-t_srs srs_def] [-s_srs srs_def]
[-f format_name] [-overwrite] [[-dsco NAME=VALUE] ...]
dst_datasource_name src_datasource_name
[-lco NAME=VALUE] [-nln name] [-nlt type] [layer [layer ...]]
-f format_name: output file format name, possible values are:
-f "ESRI Shapefile"
-f "MapInfo File"
-f "TIGER"
-f "S57"
-f "DGN"
-f "Memory"
-f "BNA"
-f "CSV"
-f "GML"
-f "GPX"
-f "KML"
-f "GeoJSON"
-f "Interlis 1"
-f "Interlis 2"
-f "GMT"
-f "SQLite"
-f "ODBC"
-f "PostgreSQL"
-f "MySQL"
-append: Append to existing layer instead of creating new if it exists
-overwrite: delete the output layer and recreate it empty
-update: Open existing output datasource in update mode
-select field_list: Comma-delimited list of fields from input layer to
copy to the new layer (defaults to all)
-where restricted_where: Attribute query (like SQL WHERE)
-sql statement: Execute given SQL statement and save result.
-skipfailures: skip features or layers that fail to convert
-gt n: group n features per transaction (default 200)
-spat xmin ymin xmax ymax: spatial query extents
-dsco NAME=VALUE: Dataset creation option (format specific)
-lco NAME=VALUE: Layer creation option (format specific)
-nln name: Assign an alternate name to the new layer
-nlt type: Force a geometry type for new layer. One of NONE, GEOMETRY,
POINT, LINESTRING, POLYGON, GEOMETRYCOLLECTION, MULTIPOINT, MULTILINE,
MULTIPOLYGON, or MULTILINESTRING. Add "25D" for 3D layers.
Default is type of source layer.
-a_srs srs_def: Assign an output SRS
-t_srs srs_def: Reproject/transform to this SRS on output
-s_srs srs_def: Override source SRS
Srs_def can be a full WKT definition (hard to escape properly),
or a well known definition (ie. EPSG:4326) or a file with a WKT
definition.
CD C:\Documents and Settings\cedric\Mes documents\Migrateur\eda\couches_SIG\ROE C:\OSGeo4W\bin\ogr2ogr -f "ESRI Shapefile"
Connect the ROE database and add the obstacle_referentiel layer
Add the file GEOFLADept_FR_Corse_AV_L93\DEPARTEMENT.shp (layer>add a vector layer)
Right clic on the layer> properties> redefine projection RGF93/lambert93 ESPG id =2154
How do we reproject ?
Tools > Geoprocessing tools > Clip
The Physical Data Model PDM
Is in : EDAData\dataEDAcommun\barrage\SchemaGeobs?.zip
view: geobs.obstacle
obs_id: identifiant de l'obstacle
obs_position_locale: projection
obs_original:
obs_table:
obs_nom:
obs_id_source:
obs_nom_source:
obs_id_etat:
table: geobs.franchissabilite_piscicole
fra_id:
fra_ref_id:
fra_note: note attribuée
fra_esp_id:
Describing the MIGANG database
Several tables and views are used
t_ouvrage_ouv : information de base (coordonnées géographique, nom de l'ouvrage, identifiant...)
tj_onatureouvrage_nao : un ouvrage peut avoir une nature principale et une ou plusieurs natures secondaires
tj_ouvrageusage_ouu : usage principal du barrage
t_turbine_turb : information sur les turbines
t_franchisbar_fba : évaluation des classes de franchissabilités à la montaison par espèces cible (saumon, lamproie, alose, truite de mer et anguille)
t_passe_passe : dispositif de franchissement et type
t_denivele_den : dénivelé à débite caractéristique
t_devalaison_deval : dispositif de dévalaison et ses caractéristiques
t_infocompl_inc : informations complémentaires
tables: t_ouvrage_ouv, t_franchisbar_fba, view: v_ouv_fba
Seulement le Bassin versant de la Loire et la Bretagne.
ouv_id: obstacle identifier
ouv_ouv_id:
ouv_baraval:
ouv_codegenerique:
ouv_distancesource: distance à la source de l'ouvrage (km?)
ouv_distancemer: distance à la mer de l'ouvrage (km?)
ouv_distancemareedyn: distance à la marée dynamique de l'ouvrage (km?)
ouv_sbv: surface bassin versant ?
ouv_bassin:
ouv_rinom:
ouv_abscisse:
ouv_ordonnee:
ouv_libelle:
ouv_commentaires:
ouv_zone_geo: zone géographique (BV Loire, Bretagne)
fba_id:
fba_ouv_id:
fba_tax_code:
fba_valeurnote: note attribuée
fba_tyn_typenote: type de notes (expertise, berge, diversite, hauteur, mortalite devalaison, profil, rugosite, score, score2
fba_datedebut:
fba_datefin:
fba_commentaire:
Classe de Franchissabilité
| Classe de franchissabilité | Appréciation du franchissement |
| 0 | Libre circulation |
| 1 | Franchissable (sans difficulté apparente) |
| 2 | Franchissable temporairement |
| 3 | Difficilement franchissable |
| 4 | Très difficilement franchissable |
| 5 | Infranchissable |
Difference between ROE and MIGANG database
"En utilisant la base "Obstacle France", on obtient une liste d'ouvrages beaucoup plus exhaustive. En revanche, cette donnée est moins fiable et n'est pas assortie d'évaluation de franchissabilité sur les ouvrages." (Marion, 2008).
