Hackathon Challenge: Difference between revisions

Jump to navigation Jump to search
Line 66: Line 66:


Many of the Lichen Gold labels have verbatimLatitude and verbatimLongitude, but the Gold Parsed files do not have the calculated decimalLatitude and decimalLongitude.  This seems especially true for the New York labels. (Daryl)
Many of the Lichen Gold labels have verbatimLatitude and verbatimLongitude, but the Gold Parsed files do not have the calculated decimalLatitude and decimalLongitude.  This seems especially true for the New York labels. (Daryl)
This is open to debate, but I think Elevation should be a pure numeric field, assumed to be in meters.  Therefore, it should not be expressed as "750 m", but rather as "750".  verbatimElevation, of course, should retain the "m" if it was present on the label.  (Note that Darwin Core apparently does not have a field called "elevation", but rather MinimumElevationInMeters, and MaximumElevationInMeters, both numeric fields.)  Not sure if this is something to change on the labels, but worth being aware of.  I think parsing programs should generate the Darwin Core fields. (Daryl)


== Parameters ==
== Parameters ==

Navigation menu