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.
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.