Hackathon Challenge: Difference between revisions

Jump to navigation Jump to search
Line 68: Line 68:


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)
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)
Inconsistency in the Gold Parsed labels for Country.  If a US State is listed as the state, the label doesn't always say the name of the country, though it is obviously the USA.  Some Gold parsed results leave it blank, some fill it in with "USA", or "United States", though neither of these are on the label.  I think it is valid to fill it in, but it should be consistent.


== Parameters ==
== Parameters ==

Navigation menu