https://github.com/r-geoflow/geoflow

Orchestrate Geospatial (Meta)Data Management Workflows and Manage FAIR Services
https://github.com/r-geoflow/geoflow

data dataverse fair geospatial inspire iso metadata ocs ogc orchestrator postgis r spatial workflow zenodo

Last synced: 3 months ago
JSON representation

Orchestrate Geospatial (Meta)Data Management Workflows and Manage FAIR Services

• Host: GitHub
• URL: https://github.com/r-geoflow/geoflow
• Owner: r-geoflow
• License: other
• Created: 2018-09-25T09:28:30.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2025-10-09T10:24:06.000Z (3 months ago)
• Last Synced: 2025-10-22T04:52:53.219Z (3 months ago)
• Topics: data, dataverse, fair, geospatial, inspire, iso, metadata, ocs, ogc, orchestrator, postgis, r, spatial, workflow, zenodo
• Language: R
• Homepage: https://github.com/r-geoflow/geoflow/wiki
• Size: 2.35 MB
• Stars: 48
• Watchers: 6
• Forks: 16
• Open Issues: 24
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
# geoflow 

[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)

[![Build Status](https://github.com/r-geoflow/geoflow/actions/workflows/r-cmd-check.yml/badge.svg?branch=master)](https://github.com/r-geoflow/geoflow/actions/workflows/r-cmd-check.yml)

[![CRAN_Status_Badge](https://www.r-pkg.org/badges/version/geoflow)](https://cran.r-project.org/package=geoflow)

[![Github_Status_Badge](https://img.shields.io/badge/Github-1.0.0-blue.svg)](https://github.com/r-geoflow/geoflow)

[![DOI](https://zenodo.org/badge/DOI//10.5281/zenodo.3138920.svg)](https://doi.org//10.5281/zenodo.3138920)

**Orchestrate Geospatial (Meta)Data Management Workflows and Manage FAIR Services**

``geoflow`` provides an engine to facilitate the orchestration and execution of metadata-driven data management workflows, in compliance with FAIR (Findable, Accessible, Interoperable and Reusable) data management principles. By means of a pivot metadata model, relying on the [DublinCore](https://dublincore.org/) standard, a unique source of metadata can be used to operate multiple and inter-connected data management actions. Users can also customise their own workflows by creating specific actions but the library comes with a set of native actions that have been identified as key steps most data managers, in particular actions oriented to the publication on the web of metadata and data resources to provide standard discovery and access services. 

At first, default actions of the library were meant to focus on providing turn-key actions for geospatial (meta)data:

* by creating manage geospatial (meta)data complying with [ISO/TC211](https://committee.iso.org/home/tc211) and [OGC](https://www.ogc.org/standards/) geographic information standards (eg 19115/19119/19110/19139) and related best practices (eg. INSPIRE); and

* by facilitating extraction, reading and publishing of standard geospatial (meta)data within widely used software that compound a Spatial Data Infrastructure (SDI), including spatial databases (eg. 'PostGIS'), metadata catalogues (eg. 'GeoNetwork', CSW servers), data servers (eg. GeoServer). 

The library was then extended to actions for other domains:

* biodiversity (meta)data standard management including handling of EML metadata, and their management with DataOne servers,

* in situ sensors, remote sensing and model outputs  (meta)data standard management by handling part of CF conventions, 'NetCDF' data format and OPeNDAP access protocol, and their management with Thredds servers, 

* generic / domain agnostic (meta)data standard managers (Dublin Core, DataCite), to facilitate the publication of data within (meta)data repositories such as [Zenodo](https://zenodo.org) or [DataVerse](https://dataverse.org/). 

The execution of several actions will then allow to cross-reference (meta)data resources in each action performed, offering a way to bind resources between each other (eg. reference 'Zenodo' DOIs in 'GeoNetwork'/'Geoserver' metadata, or vice versa reference 'Geonetwork'/Geoserver' links in 'Zenodo' or EML metadata). The use of standardized configuration files (JSON format) allows fully reproducible workflows to facilitate the work of data and information managers.

Please check the [online documentation](https://github.com/r-geoflow/geoflow/wiki) for more details! **(documentation in preparation)**

For questions about using or contributing to geoflow, you can ask them in the discussions panel: https://github.com/r-geoflow/geoflow/discussions

## Sponsors

Many thanks to the following organizations that have provided fundings for strenghtening the ``geoflow`` package:



  



  








  

  

  



The following projects have contributed to strenghten ``geoflow``:

* **Blue-Cloud** _Blue-Cloud has received funding from the European Union's Horizon programme call BG-07-2019-2020, topic: [A] 2019 - Blue Cloud services, Grant Agreement No.862409._

* **CCSAFE** 

* **G2OI** project, cofinanced by the European Union, the Reunion region, and the French Republic.







  

## Sponsoring


For geoflow sponsoring/funding new developments, enhancements, support requests, please contact me by [e-mail](mailto:eblondel.pro@gmail.com)

## Citation

We thank in advance people that use ``geoflow`` for citing it in their work / publication(s). For this, please use the citation provided at this link [![DOI](https://zenodo.org/badge/DOI//10.5281/zenodo.3138920.svg)](https://doi.org//10.5281/zenodo.3138920)