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

Get the pipeline running in a basic form #15

Merged
merged 8 commits into from
Jul 9, 2024
Merged

Get the pipeline running in a basic form #15

merged 8 commits into from
Jul 9, 2024

Conversation

rogup
Copy link
Contributor

@rogup rogup commented Jul 4, 2024

This must be deployed to production at the same time as DigitalCommons/land-explorer-back-end#60 to ensure API compatibility

These changes get the INSPIRE pipeline running a basic form. These initial steps of the pipeline work fine (although time will tell how reliable they are):

  • updating company ownership data
  • downloading the latest INSPIRE data
  • backing up raw INSPIRE data to the Hetzner storage box
  • transforming the raw GML data and inserting it into the pending_inspire_polygons table

The end result is that the new ownership data is visible to all LX users, and the pending polygons can be viewed by LX super users.

The following stages of the pipeline are very unreliable so shouldn't be run, since they will almost definitely crash the Node app:

  • analyse each of the pending_inspire_polygons and find a match
  • decide which of the pending_inspire_polygons to accept
  • write accepted polygons into the main DB table so the changes are visible to all LX users
    In order to skip these steps, add the stopBeforeTask=analyseInspire query param when running the pipeline using the /run-pipeline API

@rogup rogup changed the title Get the INSPIRE pipeline running Get the pipeline running in a basic form Jul 9, 2024
@rogup rogup merged commit 418b979 into main Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant