4,713
edits
Dataset Errata: Difference between revisions
m
→Errors noted in varioushttps://www.idigbio.org/wiki/skins/common/images/button_nowiki.png files
| Line 12: | Line 12: | ||
('''Ed''': Verbatim field contain verbatim results. No lichen labels have DwC complaint decimal coordinates. Likewise, no labels has DwC compliant event dates, thus '''you probably only want to only use verbatim fields for stats''') | ('''Ed''': Verbatim field contain verbatim results. No lichen labels have DwC complaint decimal coordinates. Likewise, no labels has DwC compliant event dates, thus '''you probably only want to only use verbatim fields for stats''') | ||
Check this with Alex --[[User:Dpaul|Dpaul]] 16:33, 12 June 2013 (EDT) | Check this with Alex --[[User:Dpaul|Dpaul]] 16:33, 12 June 2013 (EDT) | ||
<br> | |||
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''') | ||
<br> | <br> | ||