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

Task splitting fails if flatgeobuf data extract is uploaded #1145

Closed
spwoodcock opened this issue Jan 30, 2024 · 1 comment · Fixed by #1255
Closed

Task splitting fails if flatgeobuf data extract is uploaded #1145

spwoodcock opened this issue Jan 30, 2024 · 1 comment · Fixed by #1255
Labels
bug Something isn't working priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

Describe the bug

  • The task splitting algorithm works if a data extract is generated, or uploaded as geojson.
  • The task splitting algorithm returns no features if a data extract is uploaded in flatgeobuf format.
    • The flatgeobuf successfully loads, is parsed as geojson and displayed on the map.
    • I assume an empty geojson (or the fgb file) is passed to the task_split endpoint, instead of the geojson generated from it.

To Reproduce

  • Project creation with an uploaded flatgeobuf, attached.

Expected behavior

  • The task splitting returns splits, not a geojson with no geometries.

Screenshots

Uploading the flatgeobuf works, displaying as custom_extract.geojson (after conversion):

image

After splitting:

image

Returned data:

image

@spwoodcock
Copy link
Member Author

The PR fixes geojson parsing, plus cases with nested GeometryCollection.

Part if the issue was attempting to use a custom data extract containing only buildings, so there were not roads and rivers for splitting.

I will make another issue about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:low Backlog of tasks that will be addressed in time
Projects
Development

Successfully merging a pull request may close this issue.

1 participant