Revision 13149
Added by Aaron Marcuse-Kubitza almost 11 years ago
trunk/inputs/NY/Ecatalog_all/postprocess.sql | ||
---|---|---|
16 | 16 |
SELECT mk_derived_col((:table_str, 'maximumElevationInMeters'), $$map_nulls__num("maximumElevationInMeters_verbatim")$$); -- runtime: 40 s ("Time: 38766.181 ms") @starscream |
17 | 17 |
|
18 | 18 |
|
19 |
SELECT mk_derived_col((:table_str, 'locality'),
|
|
20 |
$$_join("locality__main", _label('substrate', "substrate"), _label('vegetation', "vegetation"))$$)
|
|
19 |
SELECT mk_derived_col((:table_str, 'locationRemarks'),
|
|
20 |
$$_join(_label('substrate', "substrate"), _label('vegetation', "vegetation"))$$) |
|
21 | 21 |
; -- runtime: 45 s ("Time: 47353.897 ms") @starscream |
22 | 22 |
|
23 | 23 |
SELECT mk_derived_col((:table_str, 'occurrenceRemarks'), |
trunk/inputs/NY/Ecatalog_all/map.csv | ||
---|---|---|
33 | 33 |
Country,country,, |
34 | 34 |
StateProvince,stateProvince,, |
35 | 35 |
County,county,, |
36 |
Locality,locality__main,,
|
|
36 |
Locality,locality,, |
|
37 | 37 |
Longitude,decimalLongitude,, |
38 | 38 |
Latitude,decimalLatitude,, |
39 | 39 |
CoordinatePrecision,coordinateUncertaintyInMeters,,"Usage inconsistent with DwC definition, which only allows degrees. Assuming units based on the range and precision of values." |
trunk/inputs/NY/Ecatalog_all/test.xml.ref | ||
---|---|---|
249 | 249 |
<value>$habitat</value> |
250 | 250 |
</_label> |
251 | 251 |
</3> |
252 |
<4>$locationRemarks</4> |
|
252 | 253 |
</_merge> |
253 | 254 |
</locationnarrative> |
254 | 255 |
<locationplace> |
trunk/inputs/NY/Ecatalog_all/unmapped_terms.csv | ||
---|---|---|
3 | 3 |
typeStatus |
4 | 4 |
dayOfYear |
5 | 5 |
eventTime |
6 |
locality__main |
|
7 | 6 |
minimumElevationInMeters_verbatim |
8 | 7 |
maximumElevationInMeters_verbatim |
9 | 8 |
preparations |
Also available in: Unified diff
fix: inputs/NY/Ecatalog_all/map.csv, postprocess.sql: remapped substrate, vegetation to locationRemarks