Skip to content

SQL Scripts to automatically populate GeoNature synthesis from VisioNature datas

Notifications You must be signed in to change notification settings

lpoaura/gn_vn2synthese

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

67 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

VisionNature database to GeoNature database continuous integration

GeoNature PostgreSQL

Continuous integration of Visionature data into a GeoNature database.

Process

  1. Transfer of Visionature JSON data to the GeoNature database with Client_API_VN
  2. Execute triggers on JSON data tables to populate GeoNature database with some default values when there is no correspondances (e.g. new species without any match with TaxRef repository):
  • roles
  • metadata such as acquisition frameworks, datasets and actors)
  • sources
  • observations

Triggers will populate to different tables in GeoNature database:

  • gn_synthese.synthese, main synthesis table
  • gn_synthese.t_sources
  • src_lpodatas.t_c_synthese_extended, child table with specific job data, linked by foreign key (gn_synthese.synthese.id_synthese)
  • gn_meta.t_acquisition_framework
  • gn_meta.t_datasets
  • gn_meta.cor_dataset_actor
  • utilisateurs.t_roles
  • utilisateurs.bib_organismes

Logos

Team

Project developped by LPO Auvergne-Rhône-Alpes

Contributors are:

  • Frédéric CLOITRE (@lpofredc) : Development
  • Elsa GUILLEY (@eguilley) : Development
  • Julien GIRARD-CLAUDON (@lpojgc) : Project coordination

About

SQL Scripts to automatically populate GeoNature synthesis from VisioNature datas

Resources

Stars

Watchers

Forks

Packages

No packages published