Update example: Remove bbox property from spatial and remove BOM character #370
+1
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is redundant with the coordinates, which is a required geojson property. See also gbif/ipt#2126)
|
Update: the version attached to the paper should not contain the BOM character. So it's only on the download page that people will get the 1.0 version with BOM character (which only affects the IPT afaik). |
yliefting
approved these changes
Dec 20, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The example dataset currently has
bboxproperty forspatial, which is redundant withcoordinates.coordinatesbasically contains the same info, but is a required geojson property. Removing it indicates to users what is necessary. See also gbif/ipt#2126The observations.csv also contained a BOM character at the start, which causes the automapping in the IPT to fail. It is a minor annoyance that it made it into the v1.0 dataset, which is attached to the paper and which people can download from https://camtrap-dp.tdwg.org/example/
One option would be to update the download page, so users can also point to the latest (development) version. @kbubnicki?