<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:r="https://r-universe.dev"><channel><title>r-geoflow.r-universe.dev</title><link>https://r-geoflow.r-universe.dev</link><description>Recent package updates in r-geoflow</description><generator>R-universe</generator><image><url>https://github.com/r-geoflow.png</url><title>R packages by r-geoflow</title><link>https://r-geoflow.r-universe.dev</link></image><lastBuildDate>Sun, 10 May 2026 07:33:49 GMT</lastBuildDate><item><title>[r-geoflow] geoflow 1.2.9004</title><author>emmanuel.blondel1@gmail.com (Emmanuel Blondel)</author><description>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' standard
(&lt;https://dublincore.org/&gt;), 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 targeting common geographic information and data
management, 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: 1) by creating manage geospatial
(meta)data complying with 'ISO/TC211'
(&lt;https://committee.iso.org/home/tc211&gt;) and 'OGC'
(&lt;https://www.ogc.org/standards/&gt;) geographic information
standards (eg 19115/19119/19110/19139) and related best
practices (eg. 'INSPIRE'); and 2) 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: 1) biodiversity
(meta)data standard management including handling of 'EML'
metadata, and their management with 'DataOne' servers, 2) 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, 3) generic / domain agnostic
(meta)data standard managers ('DublinCore', 'DataCite'), to
facilitate the publication of data within (meta)data
repositories such as 'Zenodo' (&lt;https://zenodo.org&gt;) or
DataVerse (&lt;https://dataverse.org/&gt;). 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' 'DOI' in
'GeoNetwork'/'GeoServer' metadata, or vice versa reference
'GeoNetwork'/'GeoServer' links in 'Zenodo' or 'EML' metadata).
The use of standardized configuration files ('JSON' or 'YAML'
formats) allow fully reproducible workflows to facilitate the
work of data and information managers.</description><link>https://github.com/r-universe/r-geoflow/actions/runs/25623723908</link><pubDate>Sun, 10 May 2026 07:33:49 GMT</pubDate><r:package>geoflow</r:package><r:version>1.2.9004</r:version><r:status>success</r:status><r:repository>https://r-geoflow.r-universe.dev</r:repository><r:upstream>https://github.com/r-geoflow/geoflow</r:upstream></item></channel></rss>