You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we could create standards (or use existing standards) for attribute field design. This will help in the future to make the map portable querable over different projects. For example select all polygons across NINA projects with NIN naturetype: V1 Åpen jordvannsmyr.
Now all projects use slightly different field names etc. so they cannot be compared. As soon as we have standards in place, @nicokant, @frafra can built in quality control checks in the api and datasets that not adhere to the standard are not excepted.
@TrondSimensen, @anders-kolstad, @VangNINA
It would be great if we could create standards (or use existing standards) for attribute field design. This will help in the future to make the map portable querable over different projects. For example select all polygons across NINA projects with NIN naturetype: V1 Åpen jordvannsmyr.
Now all projects use slightly different field names etc. so they cannot be compared. As soon as we have standards in place, @nicokant, @frafra can built in quality control checks in the api and datasets that not adhere to the standard are not excepted.
Documentation on how to adhere to these standards could for example be published here:
https://ninanor.github.io/EAguide/fair-data/naming-convention.html
The text was updated successfully, but these errors were encountered: