-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update example with more data #326
Merged
Merged
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
- cameraID: MICA uses camera numbers, but unknown which ones are used for these deployments specifically. Numbers were chosen that do correspond with the numbers used for the corresponding area - cameraModel: Reconyx-HF2X - cameraTilt: no data available, but all tilting down at about -15 degrees - cameraHeading: derived from looking at Google maps (285 west, 350 north, 20 north, 55 northeast) Co-Authored-By: EmmaCartuyvels1 <[email protected]>
- detectionDistance: values as recorded in Agouti, converted to meters - featureType we chose trailGame over waterSource, since the target species (Ondatra) uses the water ways as trails Co-Authored-By: EmmaCartuyvels1 <[email protected]>
Habitat is derived from the location descriptions in the MICA project report Co-Authored-By: EmmaCartuyvels1 <[email protected]>
- deploymentGroups: area codes + season (somewhat artificial, but shows use of |) - deploymentTags: position of camera along river (also moved) - deploymentComments: translate to English Co-Authored-By: EmmaCartuyvels1 <[email protected]>
One anonymized cf. Agouti approach, one empty Co-Authored-By: EmmaCartuyvels1 <[email protected]>
For the second event it is not possible to annotate at media level, since it concerns a group
- Ardea cinerea to Ardea - Remove lifeStage - add classificationTimestamp - add classificationProbability
Original bounding box is x1,y1,x2,y2 scaled to 640 width. The scaling factor is thus 0.3125 rel_x1 = x1/scale/2048 = bboxX rel_y1 = y1/scale/1440 = bboxY rel_x2 = x2/scale/2048 rel_y2 = y2/scale/1440 bboxWidth = rel_x2/rel_x1 bboxHeight = rel_y2/rel_y1 All are rounded to 5 decimals
The originalBoundingBox is in an format (see eaafce9) that is no longer used in Agouti. It would confuse users if we include it in the example dataset (it confused me)
673adc7
to
8ee79c7
Compare
@kbubnicki ready for review. Note the Thanks to @EmmaCartuyvels1 for providing all the deployment information. The example page now looks like this (includes more deployment info + shows bounding box where available): |
Even for the unclassified, there is setup information, meaning someone classified that
kbubnicki
approved these changes
Jun 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Fix #325
Make example data more complete
individual
originalBoundingBox
. I currently can't do this, because the original values don't seem to be absolute (too low) nor relative valuesUpdate example pages layout
https://tdwg.github.io/camtrap-dp/example/
and link to itUpdate schema
The EXIF data is expected to be JSON, so we indicated this as
type=object
. In a CSV file however, it is only possible to this as a string (where"
need to be escaped to""
). If we however settype=string
, it will fail data provided as JSON (where it is possible to express the EXIF data as an object). I therefore opted fortype=any