Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CDDA app-schemas #5

Closed
tkardi opened this Issue May 20, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@tkardi
Copy link
Contributor

tkardi commented May 20, 2017

The European Environmental Agency (EEA) is redesigning it's core data flows and in 2018 the reporting obligation on CDDA (Common Database on Designated Areas) will be done using Inspire ProtectedSites application schema.

The idea behind is to take PS data that is already Inspire compliant and couple that with CDDA specific data. Data will be (at least for the first year) delivered as two files - a GML file consisting of an extract of the relevant Inspire PS data and a XML file with CDDA data based on the xsds provided by the EEA. This is called the "linked data approach", though it has nothing much to do with THE linked data

As we're already using GeoServer app-schemas for Inspire PS data transformation we'll use the same technologies for setting up CDDA data transformation aswell.

This issue serves as a placeholder (reminder) for collecting tasks that need to be done.

The bulk of work is planned to be undertaken during the FOSS4GE Code Sprint.

@tkardi tkardi self-assigned this May 20, 2017

@tkardi

This comment has been minimized.

Copy link
Contributor Author

tkardi commented Jul 22, 2017

Some update information on the EEA EIONET forums

@tkardi

This comment has been minimized.

Copy link
Contributor Author

tkardi commented Aug 31, 2017

CDDA reporting issues now in a separate branch

@tkardi

This comment has been minimized.

Copy link
Contributor Author

tkardi commented Nov 30, 2017

The current setup for 2018 reporting requires xml+gml files, no download service (or type2 data for that matter) service harvesting will take place. And since our current output from a WFS service is a wfs FeatureCollection for Type2 data (see this comment), we'll need a separate tool to query data, fix namespaces and do a xpath query to save the right portion of data as an xml file.

@tkardi tkardi closed this Jan 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.