Closed mobb closed 7 years ago
this table is for general info that does not change very much
so if there is info related to eg, water depth, or height of a tower, or depth of a soil core, it has to go in event. Here is the note from Corinna. Now I have tricked myself again the same way that the ODM has problems with water depth. The sampling_location_anillary can’t handle the third dimension – up or down at one site. Of course, I could stuff it all into the sampling_location_ancillary_id, but I am not sure that’s a good idea.
sample dataset with some ancillary info left in the original format knb-lter-ntl.344
Things that belong in this table: depth of the ocean at a location, area of a lake
"timestamp without time zone" is the correct typing for postgres. see https://www.postgresql.org/docs/9.1/static/datatype-datetime.html
Table sampling_location_ancillary sampling_location_id varchar not integer check to make sure that datetime is typed correctly in posgres, (eg, should it be datetime not timestamp)