Revision 7009
Added by Aaron Marcuse-Kubitza over 11 years ago
| VegBIEN.csv | ||
|---|---|---|
| 39 | 39 |
slopegradient,/location/slopegradient_fraction/_alt/1, |
| 40 | 40 |
maxslopegradient,/location/slopegradient_fraction/_alt/2/_avg/max, |
| 41 | 41 |
minslopegradient,/location/slopegradient_fraction/_alt/2/_avg/min, |
| 42 |
plot_id,"/location/sourceaccessioncode/_join/1/_if[@name=""if subplot and unique only within parent""]/then/_first/1",
|
|
| 43 |
authorplotcode,"/location/sourceaccessioncode/_join/1/_if[@name=""if subplot and unique only within parent""]/then/_first/2",
|
|
| 42 |
plot_id,"/location/sourceaccessioncode/_if[@name=""if locationID""]/cond/_exists",
|
|
| 43 |
plot_id,"/location/sourceaccessioncode/_if[@name=""if locationID""]/then/_if[@name=""if subplot""]/then/_join/1",
|
|
| 44 | 44 |
Geographic Name,,** No join mapping for *Geographic Name ** |
| 45 | 45 |
accessioncode,,** No join mapping for *accessioncode ** |
| 46 | 46 |
authordatum,,** No join mapping for *authordatum ** |
Also available in: Unified diff
mappings/VegCore-VegBIEN.csv: locationID/locationName + subplot -> location.sourceaccessioncode mapping: Fixed bug where subplot was incorrectly being mapped to this field even when there was no location*. (This field can only be populated if both location* and subplot are specified.) Also only map locationID for this, to avoid inconsistencies where one table supplies locationID+subplot, while another table supplies locationName+subplot, but they both get mapped to the same field, preventing plots from being matched up with their observations when creating the analytical_stem.