inbo/mica-occurrences

Darwin Core mapping for the aggregated Muskrat dataset

mica-occurrences's Issues

Update dataset descriptions

• http://ipt.nlbif.nl/resource?r=mica-uvw-occurrences

MICA - Muskrat and coypu occurrences collected by UVW in the Netherlands is an occurrence dataset published by the Research Institute of Nature and Forest (INBO) and the Netherlands Biodiversity Information Facility (NLBIF). It is part of the LIFE project MICA, in which innovative techniques are tested for a more efficient control of muskrat and coypu populations, both invasive species. This dataset contains muskrat and coypu counts. Here it is published as a standardized Darwin Core Archive and includes for each occurrence record an occurrenceID, date, location, the number of recorded individuals, status (present/absent) and scientific name. Issues with the dataset can be reported at https://github.com/inbo/mica-occurrences/issues

We have released this dataset to the public domain under a Creative Commons Zero waiver. We would appreciate it if you follow the INBO norms for data use (https://www.inbo.be/en/norms-data-use) when using the data. If you have any questions regarding this dataset, don't hesitate to contact us via the contact information provided in the metadata or via [email protected].

The data were collected as part of the MICA project, which received funding from the European Union’s LIFE Environment sub-programme under the grant agreement LIFE18 NAT/NL/001047.

• https://ipt.inbo.be/resource?r=mica-rato-occurrences

MICA - Muskrat occurrences collected by RATO in East Flanders, Belgium is an occurrence dataset published by the Research Institute of Nature and Forest (INBO). It is part of the LIFE project MICA, in which innovative techniques are tested for a more efficient control of muskrat and coypu populations, both invasive species. This dataset contains muskrat trap captures. Here it is published as a standardized Darwin Core Archive and includes for each occurrence record an occurrenceID, date, location, the number of recorded individuals, status (present/absent) and scientific name. Issues with the dataset can be reported at https://github.com/inbo/mica-occurrences/issues

We have released this dataset to the public domain under a Creative Commons Zero waiver. We would appreciate it if you follow the INBO norms for data use (https://www.inbo.be/en/norms-data-use) when using the data. If you have any questions regarding this dataset, don't hesitate to contact us via the contact information provided in the metadata or via [email protected].

The data were collected as part of the MICA project, which received funding from the European Union’s LIFE Environment sub-programme under the grant agreement LIFE18 NAT/NL/001047.

• https://ipt.inbo.be/resource?r=mica-legacy-occurrences

Muskrat captures in Flanders, Belgium is an occurrence dataset published by the Research Institute for Nature and Forest (INBO). It contains information on all officially registered captures of muskrat (Ondatra zibethicus) in and around Flanders, Belgium between 1991 and 2018. These data are provided by different management actors: the Flanders Environment Agency (VMM), Rattenbestrijding Oost-Vlaanderen (RATO vzw), Polders and Wateringen (vvpw), and provincial and municipal trappers, and aggregated and analyzed by the INBO since 1991. Here it is published as a standardized Darwin Core Archive and includes for each occurrence record an occurrenceID, date, location, samplingProtocol (trap) and samplingEffort (number of days or traps), scientific name, and the organization who made the capture. The original dataset contains close to 450.000 occurrences and is available on GitHub, but only presence records (over 103.000) are included in this version, which can be used to track muskrat distribution in Flanders since 1991. Issues with the dataset can be reported at https://github.com/inbo/mica-occurrences/issues

We have released this dataset to the public domain under a Creative Commons Zero waiver. We would appreciate it if you follow the INBO norms for data use (https://www.inbo.be/en/norms-data-use) when using the data. If you have any questions regarding this dataset, don't hesitate to contact us via the contact information provided in the metadata or via [email protected].

This dataset was published for the MICA project, which received funding from the European Union’s LIFE Environment sub-programme under the grant agreement LIFE18 NAT/NL/001047.

mica agouti dwc_mapping

Some of the columns are empty. I removed them from the mapped dataset.

Review of DwC data

• latitude and longitude are flipped!
• eventDate is empty for many records where year and month is available. Express in eventDate as yyyy-mm (when year and month are available) or yyyy (where year is available).
• Prov column should be renamed stateProvince
• stateProvince values should be English: https://en.wikipedia.org/wiki/Provinces_of_Belgium
• Since all records will have an eventDate then year and month could be dropped.
• samplingEffort format looks odd: 24 :daysOfwork. Would write similar to other datasets: daysOfWork: 24.
• taxonID: drop field, it is not a reference to an existing identifier and no need to generate it for an occurrence dataset
• scientificNameAuthorship: drop field, not required for a single taxon dataset. Correct value would be (Linnaeus, 1766) with parentheses.
• georeferenceRemarks: change to coordinates are centroid of municipality and exact coordinates.
• ownerInstitutionCode: drop field, we discourage the use of this term, and the same info is in rightsHolder and recordedBy
• occurrenceID: what does the L stand for in INBO:MUSK:L:OCC:1 Legacy
• samplingProtocol contains connibearclampNA, FuikenNA and NA15. These should be without NA
• samplingProtocol contains values such as connibearclamp3? What does the number stand for? Is it necessary? Would try to have a controlled, lowercase list of values. is now connibearclamp: 3 is the number of traps used
• municipality: values such as Crisn�e and H�l�cine indicate wrong encoding (not UTF-8)
• locationID: does INBO:MUSK:L:LOC:VHANA contain an NA instead of a number?
• 1% of the records contains no coordinates, is this correct? yes
• samplingEffort contains NA :daysOfwork. Has to be empty.
• rightsHolder and recordedBy: what does Gem stand for? Gemeente? Would write municipality then.
• datasetName: Muskrat occurrences in Belgium, aggregated data: "aggregated data" seems to imply data loss. In addition, most data are from Flanders and I assume captures? Can I suggest: MICA - Pre-project muskrat captures in Flanders, Belgium there is some data loss along the way I guess
• order of the columns is not Darwin Core
• type: missing
• basisOfRecord: missing

Mica Agouti location

Is there a coordinate uncertainty foreseen for this dataset. I imagine that we do not wan't to publish the exact location of the camera traps.

which location is given (is this already with an uncertainty?)
What is the coordinateUncertaintyInMeters for this dataset

What authors to include

Here's a comparison between the Agouti project contributors and current dataset authors for MICA - Muskrat and coypu camera trap observations in Belgium, the Netherlands and Germany.

@EmmaCartuyvels1, should we include all contributors as authors? And should Kristof, Sander and Dimi become Agouti project contributors?

person	agouti contributor	dataset author
Emma Cartuyvels	x	x
Tim Adriaens	x	x
Kristof Baert		x
Dimitri Brosens		x
Gust Boiten	x
Jim Casaer	x	x
Abel De Boer	x
Sander Devisscher		x
Dennis Donckers	x	x
Silke Dupont	x
Heiko Fritz	x	x
Lilja Fromme	x
Friederike Gethöffer	x
Frank Huysentruyt	x	x
Leo Kehl	x
Liam Letheren	x
Lydia Liebgott	x
Yorick Liefting	x
Jan Lodewijkx	x	x
Claudia Maistrelli	x	x
Björn Matthies	x
Kelly Meijvisch	x
Dolf Moerkens	x
Axel Neukermans	x	x
Kurt Schamp	x
Dan Slootmaekers	x	x
Danny Van der beeck	x	x
Peter Desmet	x	x

Empty sequences to be removed

Two invalid sequences were included in export:

782bfb18-e820-469c-acda-bf2c1b6f575d:seq,701956d1-c5f9-49f4-a42a-6f5f7fa77943,782bfb18-e820-469c-acda-bf2c1b6f575d,,+02:00,unclassified,motion detection,False,,,,,,,,,,,,
aa985039-918b-42d8-ab5e-bc8700736048:seq,a0441d90-467f-4e8b-875e-3e275ebccf53,aa985039-918b-42d8-ab5e-bc8700736048,,+02:00,unclassified,motion detection,False,,,,,,,,,,,,

mica-agouti eventRemarks

In dwc_occurrence we have in eventRemarks values like: 'batterijen vervangen | tags: rechteroever' and 'begin 19/06 tot 16/07 7228 foto's | tags: linkeroever'

Do we want this in the published dataset or can we just remove this column

Double author name

Kelly Meijvisch is included as contributor with two email addresses. @EmmaCartuyvels1 I assume this is the same person?

Remove mica-occurrences repo?

I noticed the repo https://github.com/inbo/mica-occurrences, which hasn't been updated in 4 months and seems to be mostly a template except for this script: https://github.com/inbo/mica-occurrences/blob/master/src/script_VMM_2016_2016.Rmd

@DimEvil, can that repo be removed, now that we have this (muskrat-occurrences) repo here?

Use same project info for all MICA datasets

• Create default MICA project description
• Update http://ipt.nlbif.nl/resource?r=mica-uvw-occurrences#project
• Update https://ipt.inbo.be/resource?r=mica-rato-occurrences#project
• Update https://ipt.inbo.be/resource?r=mica-legacy-occurrences#project
• Update https://ipt.inbo.be/resource?r=mica-agouti-occurrences#project

Title

MICA - Management of Invasive Coypu and muskrAt in Europe

Identifier

LIFE18 NAT/NL/001047

Description

Invasive alien species such as the coypu and muskrat pose a major threat to biodiversity and cost millions of euros annually. By feeding on rushes and reeds, these animals cause serious damage to the environment in which they live and endangered species suffer from habitat loss. The disappearance of reeds and digging in dikes represents a safety risk for humans in the lowland areas. With the LIFE project MICA (https://lifemica.eu/), the partners from the participating countries want to develop a transnational plan for the management of coypu and muskrat populations in Europe and aim to reduce their population. The objective of an effective population control of coypu and muskrat is to protect lowlands from flooding, to prevent crop damage and loss of biodiversity. The objective of the project is to serve as a pilot and demonstration project in which ‘best practices’ are tested and new techniques are developed for a more efficient control of muskrat and coypu populations. By involving organisations from Belgium, Germany and the Netherlands, the project also promotes international cooperation and knowledge exchange in the field of muskrat and coypu management.

Funding

LIFE programme

Study area description

Belgium, the Netherlands, Germany

Design description

Verify UTC vs local timestamps for Agouti dataset

Have better datasetName for Agouti occurrences

@EmmaCartuyvels1 the current title for this dataset is:

MICA - Muskrat and Coypu camera trap occurrences collected in Belgium, the Netherlands and Germany

But the dataset obviously contains much more. Is there a better name we could give to this dataset? The structure of the title should be something like:

MICA - ... in location

Canis lupus vs Canis familiaris

We have 'Canis familiaris' in occurrenceREmarks when the scientificName is 'Canis lupus'. (dab4021f-a26d-4127-9559-bc6a6833d870)

We cant' publish records of wolves when we are not absolutely sure. And Canis familiaris is not a valid name for Agouti it seems..

Some occurrenceRemarks annotate the scientificName like in the case of the wolf, but also Rattus norvegicus in scientificName and Gedeeltelijk zichtbaar. Harig => Zeker soort rat in occurrenceRemarks (3cd7759c-6c1d-414f-a90a-2c161a5e2aeb)

What license to choose for the images

The license for the data will be CC0 as usual, but what license to we want to use for the images? Also CC0 or rather CC-BY?

@EmmaCartuyvels1 @jimcasaer let me know if you need more guidance for this decision

Validation errors for MICA Agouti dataset

The Agouti export for the MICA project has the following validation errors:

Deployments

• 0c70e239-63ee-4341-8f7f-8f7c968c4970 missing timestamp
• 11eb24ac-cd35-4013-9285-beab3be78106 empty
• 1d2289eb-8d16-4c11-8ff0-a528ba2d6e5a empty
• 2cb981b3-c02e-4d1c-a299-93960a75ffd0 empty
• 8282f845-90d0-40ed-9675-6e9577751b31 empty
• a49f35e7-5492-48c0-90ea-85d46e04df82 empty
• cbe8eabf-77ea-43ed-8070-0ad5980b32da empty
• fcf79945-f30d-46d9-9ed1-b59cc34447a3 empty
• fe0a5692-7bea-44f7-9549-af64095607e4 empty

Observations

observationID,deploymentID,eventID

• 71d10e66-8189-452b-b911-b45560fa5221,380077a1-389f-4ddb-bd6d-9c5e40ce1c56,208d0088-57fe-4314-9949-4de1b3cc0fcd: missing timestamp sequence found
• aaf1e84f-90c0-4087-a546-8243c0f458b5,8520f7c9-15db-4274-ac11-7f9b42df6551,,74de0d1d-e88c-4155-8377-76dff068a4b3: missing timestamp sequence not found
• 8fbe1381-897d-4b02-9e26-dce85f26d538,994f124a-dba8-4d1d-9f62-7c0c9aaf2981,,8fbe1381-897d-4b02-9e26-dce85f26d538: missing timestamp sequence not found
• 25e5417e-cd3b-4c57-ae19-319f3bf67a41,d247656d-cb58-4fb1-b860-7e7f863646ee,,fe0dfaae-d65c-4320-bbce-4df960bdec94: missing timestamp sequence found
• 501aac62-c647-44d4-8904-daf352e3fc46,f34058ce-aba3-4599-b1e3-b41e5a4739e6,,501aac62-c647-44d4-8904-daf352e3fc46: missing timestamp sequence not found
• d27a6b66-f3c6-47e5-8da9-cdb427fa8d58,f34058ce-aba3-4599-b1e3-b41e5a4739e6,,d27a6b66-f3c6-47e5-8da9-cdb427fa8d58: missing timestamp sequence not found

Full log

───────────────────────────────────────────────────────────────────── Dataset ─────────────────────────────────────────────────────────────────────
                       dataset                       
┏━━━━━━━━━━━━━━┳━━━━━━━┳━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┓
┃ name         ┃ type  ┃ path             ┃ status  ┃
┡━━━━━━━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━━━━━━╇━━━━━━━━━┩
│ deployments  │ table │ deployments.csv  │ INVALID │
│ media        │ table │ media.csv        │ VALID   │
│ observations │ table │ observations.csv │ INVALID │
└──────────────┴───────┴──────────────────┴─────────┘
───────────────────────────────────────────────────────────────────── Tables ──────────────────────────────────────────────────────────────────────
                                                                    deployments                                                                    
┏━━━━━━┳━━━━━━━┳━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Row  ┃ Field ┃ Type             ┃ Message                                                                                                       ┃
┡━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ 86   │ 7     │ type-error       │ Type error in the cell "+01:00" in row "86" and field "deploymentStart" at position "7": type is              │
│      │       │                  │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                │
│ 86   │ 8     │ type-error       │ Type error in the cell "+01:00" in row "86" and field "deploymentEnd" at position "8": type is                │
│      │       │                  │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                │
│ 122  │ 4     │ constraint-error │ The cell "" in row at position "122" and field "latitude" at position "4" does not conform to a constraint:   │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 122  │ 5     │ constraint-error │ The cell "" in row at position "122" and field "longitude" at position "5" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 122  │ 7     │ constraint-error │ The cell "" in row at position "122" and field "deploymentStart" at position "7" does not conform to a        │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 122  │ 8     │ constraint-error │ The cell "" in row at position "122" and field "deploymentEnd" at position "8" does not conform to a          │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 204  │ 4     │ constraint-error │ The cell "" in row at position "204" and field "latitude" at position "4" does not conform to a constraint:   │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 204  │ 5     │ constraint-error │ The cell "" in row at position "204" and field "longitude" at position "5" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 204  │ 7     │ constraint-error │ The cell "" in row at position "204" and field "deploymentStart" at position "7" does not conform to a        │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 204  │ 8     │ constraint-error │ The cell "" in row at position "204" and field "deploymentEnd" at position "8" does not conform to a          │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 314  │ 4     │ constraint-error │ The cell "" in row at position "314" and field "latitude" at position "4" does not conform to a constraint:   │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 314  │ 5     │ constraint-error │ The cell "" in row at position "314" and field "longitude" at position "5" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 314  │ 7     │ constraint-error │ The cell "" in row at position "314" and field "deploymentStart" at position "7" does not conform to a        │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 314  │ 8     │ constraint-error │ The cell "" in row at position "314" and field "deploymentEnd" at position "8" does not conform to a          │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 827  │ 4     │ constraint-error │ The cell "" in row at position "827" and field "latitude" at position "4" does not conform to a constraint:   │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 827  │ 5     │ constraint-error │ The cell "" in row at position "827" and field "longitude" at position "5" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 827  │ 7     │ constraint-error │ The cell "" in row at position "827" and field "deploymentStart" at position "7" does not conform to a        │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 827  │ 8     │ constraint-error │ The cell "" in row at position "827" and field "deploymentEnd" at position "8" does not conform to a          │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1025 │ 4     │ constraint-error │ The cell "" in row at position "1025" and field "latitude" at position "4" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1025 │ 5     │ constraint-error │ The cell "" in row at position "1025" and field "longitude" at position "5" does not conform to a constraint: │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1025 │ 7     │ constraint-error │ The cell "" in row at position "1025" and field "deploymentStart" at position "7" does not conform to a       │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1025 │ 8     │ constraint-error │ The cell "" in row at position "1025" and field "deploymentEnd" at position "8" does not conform to a         │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1236 │ 4     │ constraint-error │ The cell "" in row at position "1236" and field "latitude" at position "4" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1236 │ 5     │ constraint-error │ The cell "" in row at position "1236" and field "longitude" at position "5" does not conform to a constraint: │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1236 │ 7     │ constraint-error │ The cell "" in row at position "1236" and field "deploymentStart" at position "7" does not conform to a       │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1236 │ 8     │ constraint-error │ The cell "" in row at position "1236" and field "deploymentEnd" at position "8" does not conform to a         │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1534 │ 4     │ constraint-error │ The cell "" in row at position "1534" and field "latitude" at position "4" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1534 │ 5     │ constraint-error │ The cell "" in row at position "1534" and field "longitude" at position "5" does not conform to a constraint: │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1534 │ 7     │ constraint-error │ The cell "" in row at position "1534" and field "deploymentStart" at position "7" does not conform to a       │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1534 │ 8     │ constraint-error │ The cell "" in row at position "1534" and field "deploymentEnd" at position "8" does not conform to a         │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1540 │ 4     │ constraint-error │ The cell "" in row at position "1540" and field "latitude" at position "4" does not conform to a constraint:  │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1540 │ 5     │ constraint-error │ The cell "" in row at position "1540" and field "longitude" at position "5" does not conform to a constraint: │
│      │       │                  │ constraint "required" is "True"                                                                               │
│ 1540 │ 7     │ constraint-error │ The cell "" in row at position "1540" and field "deploymentStart" at position "7" does not conform to a       │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
│ 1540 │ 8     │ constraint-error │ The cell "" in row at position "1540" and field "deploymentEnd" at position "8" does not conform to a         │
│      │       │                  │ constraint: constraint "required" is "True"                                                                   │
└──────┴───────┴──────────────────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
                                                                   observations                                                                    
┏━━━━━━━━┳━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Row    ┃ Field ┃ Type       ┃ Message                                                                                                           ┃
┡━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ 47884  │ 5     │ type-error │ Type error in the cell "+02:00" in row "47884" and field "eventStart" at position "5": type is                    │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 47884  │ 6     │ type-error │ Type error in the cell "+02:00" in row "47884" and field "eventEnd" at position "6": type is                      │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 100011 │ 5     │ type-error │ Type error in the cell "+01:00" in row "100011" and field "eventStart" at position "5": type is                   │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 100011 │ 6     │ type-error │ Type error in the cell "+01:00" in row "100011" and field "eventEnd" at position "6": type is                     │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 114907 │ 5     │ type-error │ Type error in the cell "+01:00" in row "114907" and field "eventStart" at position "5": type is                   │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 114907 │ 6     │ type-error │ Type error in the cell "+01:00" in row "114907" and field "eventEnd" at position "6": type is                     │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 151170 │ 5     │ type-error │ Type error in the cell "+01:00" in row "151170" and field "eventStart" at position "5": type is                   │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 151170 │ 6     │ type-error │ Type error in the cell "+01:00" in row "151170" and field "eventEnd" at position "6": type is                     │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 176577 │ 5     │ type-error │ Type error in the cell "+01:00" in row "176577" and field "eventStart" at position "5": type is                   │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 176577 │ 6     │ type-error │ Type error in the cell "+01:00" in row "176577" and field "eventEnd" at position "6": type is                     │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 176578 │ 5     │ type-error │ Type error in the cell "+01:00" in row "176578" and field "eventStart" at position "5": type is                   │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
│ 176578 │ 6     │ type-error │ Type error in the cell "+01:00" in row "176578" and field "eventEnd" at position "6": type is                     │
│        │       │            │ "datetime/%Y-%m-%dT%H:%M:%S%z"                                                                                    │
└────────┴───────┴────────────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Whip mica-vmm-occurrences

• occurrenceID: duplicates
• samplingProtocol: write as rat trap
• eventDate: full dates with day possible?
• recordedBy: would write as VMM team BENEDENSCHELDE rather than VMM:team:BENEDENSCHELDE
• locationRemark: correct value to CAT3 - not navigable cat. 3
• stateProvince: use English names, see https://en.wikipedia.org/wiki/Provinces_of_Belgium
• stateProvince / municipality: leave Onbekend empty
• decimalLatitude: three values below 50.67
• decimalLongitude: two values below 2.53
• geodeticDatum: field is listed twice, keep the second one
• identifiedBy: RATO: drop this field, probably incorrect?
• vernacularName: technically, this should appear after taxonRank
• vernacularName: Tachybaptus ruficollis should be Dodaars
• taxonRank: Zapornia pusilla intermedia (Hermann, 1804) should have subspecies

identifiedBy

Do we keep the names of the identifiers (identifiedBy)? Of do we anonymise them?

individualCount, sex and occurrenceRemarks doesn't always add up

The numbers doesn't always count up. For example I have
occurrenceRemarks: Moeder en 2 kindjes individualCount: 3 & occurrenceRemarks: Moeder en 2 kindjes individualCount: 1

What to do here?

I would suggest to skip occurrenceRemarks, (as this is only given for like 250 records) and it also contains stuff like 'mooie foto'.

But also important information is sometimes to be found there: 'staart bever volgens Kristof' and discussion on the validation of the record. We have 'Canis familiaris' when the scientificName is 'Canis lupus'. We cant' publish records of wolves when we are not absolutely sure. And Canis familiaris is not a valid name for Agouti it seems..