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

Defining a schema with incomplete 1st record. #8

Open
njkim opened this issue Jan 12, 2021 · 0 comments
Open

Defining a schema with incomplete 1st record. #8

njkim opened this issue Jan 12, 2021 · 0 comments
Assignees

Comments

@njkim
Copy link
Collaborator

njkim commented Jan 12, 2021

Currently the geojson endpoint returns with only the properties that is not Null and the Koop will create a schema based on the first one passing.
So, even if the service is supposed to have 5 columns, if the first record happens to have 2 columns all other record that has more the 2 columns seems to have some issues (including of not displaying the attribute values though geometry shows up).

Also, some of geometry collection have {nodeId} inside geojson as a property which makes things more complicated.

So, it would be great if the Koop service can define schema before the 1st actual record or ways to clean up the incoming geojson.

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

No branches or pull requests

2 participants