> GLOBE's data is point data collected at sites that are geo-referenced > (using the WGS-84 datum). Sites have associated metadata which depends > on the site type. Sites are associated with schools. Time series > measurements of defined data sets (air temp, humidity, etc.) are taken > at sites, and there are dependencies which are enforced between the > data. Dependencies can relate data set, time, and location, e.g. to > report measurement X at a site you must also report measurement Y taken > at the same time and measurement Z taken within an hour, at the same > site. Dependencies can be between sites - some site types require or > allow supporting data to be taken at an Atmosphere site located not more > than a certain distance from the site. The data needs to be searchable > by school(s), country(ies), lat, lon, elevation, type and amount of data > reported within specified date ranges. Data collected within specified > time and location windows may need to be returned as if it were a single > record. For many data sets, it is necessary to distinguish between > data collected in and out of the "local solar noon window" (one hour > before to one hour after local solar noon) in the application that uses > the data. I can describe how the data is/would be structured in a > relational database if that would help. The ice phenology data that we > will need to add includes numeric+text data as described above, plus > photo sets that are actually point data as well - located at sites and > taken as a time series. It sounds to me like you need a relational database for this. Im not sure where the TDS fits in. Ticket Details =================== Ticket ID: CLT-133772 Department: Support THREDDS Priority: Normal Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.