Revision 3919
Added by Aaron Marcuse-Kubitza over 12 years ago
| VegBIEN.plots.csv | ||
|---|---|---|
| 16 | 16 |
SiteCode,/location/locationevent/authorlocationcode,Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project) |
| 17 | 17 |
life_zone_code,/location/locationevent/commclass/commdetermination/*_id/commconcept/*_id/*/commname, |
| 18 | 18 |
life_zone,/location/locationevent/commclass/commdetermination/*_id/commconcept/commdescription, |
| 19 |
date_finish,/location/locationevent/obsenddate/_*/date, |
|
| 20 |
date_start,/location/locationevent/obsstartdate/_*/date, |
|
| 19 |
date_finish,/location/locationevent/obsenddate/_*/date/_dateRangeEnd/value/_*/date,
|
|
| 20 |
date_start,/location/locationevent/obsstartdate/_*/date/_dateRangeStart/value/_*/date,
|
|
| 21 | 21 |
Precip,/location/locationevent/precipitation, |
| 22 | 22 |
soil_acidity,"/location/locationevent/soilobs/acidity/_units:[default=""%"",to=]/value/_map:[""<0.05""=0,*=*]/value", |
| 23 | 23 |
soil_base,"/location/locationevent/soilobs/basesaturation/_units:[default=""%"",to=]/value", |
Also available in: Unified diff
VegBIEN mappings: Wrapped dates in _date() and _dateRangeStart()/_dateRangeEnd(), to assist in importing date and date range values that PostgreSQL cannot parse. This will increase the import time, but hopefully also decrease the # of invalid values in the errors tables. (These functions can later be optimized to reduce the impact on import time.)