Expand mappings to additional location sensor types

[sarahcd]

Eventually we will want to use the package for non-gps data, i.e., events with a different sensor-type, expected accuracy, and maybe other characteristics that we need to consider.

Here are the current location sensors, ordered by my suggested priority to include:

• bird-ring (inbo project)
• argos-doppler-shift (the most common one in mvb besides gps, and studies often contain both)
• radio-transmitter
  (note there will be little data to publish for a while with the sensor-types below, so we could start by building in the three above such that the others can be more easily integrated later.)
• gnss
• atlas-geolocation
• solar-geolocator
• sigfox-geolocation
• acoustic-telemetry
• geolocation-api
• natural-mark

(You can this list here: https://www.movebank.org/movebank/service/direct-read?entity_type=tag_type&is_location_sensor=true)

[peterdesmet]

As this is a big scope increase, let's tackle it with use cases.

If there is a need and an example dataset for a specific type, we can see how to expand add_resource() and write_dwc() for that type of data. From INBO, we'll definitely do this for the bird-ring type as part of the GULLIVER project. Separate issues will be created for that.

[sarahcd]

notes for later on integrating argos-doppler-shift data:

• ATN has decided on a procedure to translate the Argos Location Class values to coordinateUncertaintyInMeters. We should consult with them once we get to this.
• The LC attribute is being used for the new Argos/Kineis constellation. I expect researchers will be publishing updated assessments of how consistent these accuracy labels are for tracking datasets.