DwC Importer: Correct latitude/longitude mapping

[LocoDelAssembly]

Currently decimalLatitude and decimalLongitude are mapped into CE's verbatim_latitude and verbatim_longitude respectively (and georeferenced by Georeference::VerbatimData). DwC also has verbatimLatitude and verbatimLongitude, which are currently unmapped.

This issue is just to confirm whether the mapping is correct or the georeference should be handled differently. Using true verbatim values with TW UI is not producing a georeference:

Notice lat/long are parsed near radial button but nothing is shown in map because it is not accepting the verbatim lat/long.

Although this issue main objective is to track DwC mapping, I'm also wondering if usage of the field is consistent throughout interfaces and/or editors' use of verbatim lat/long fields?

It is also the problem of whether I will be able to successfully map verbatim DwC lat/long fields into verbatim CE fields and still use Georeference using data from the decimal DwC fields? Current mapping was to make Comprehensive specimen digitization and browse collection object tasks happy mostly.

[mjy]

Currently decimalLatitude and decimalLongitude are mapped into CE's verbatim_latitude and verbatim_longitude respectively (and georeferenced by Georeference::VerbatimData).

We should perhaps adjust this.

• decimalLatitutde and decimalLongitude should be Georeference only? Perhaps a new class of Georeference?

• DwC also has verbatimLatitude and verbatimLongitude -> these definitely should be our verbatim fields, and we should still create a verbatimGeoreference UNLESS also accompanied with the other fields?

[debpaul]

@mjy @LocoDelAssembly did we change how this is being done now? Or are changes to the mapping and import still needed to accommodate lat/lon concepts?