This version contains very few changes to HatchRelData, Reference and Habitat Restoration tables , all of which are high priorities to work on. The database has actually shrunk in the 13 months since it was last posted on-line, largely due to the removal of many tables such as the AIWP projects (now available at the CBFWA web site, http://www.cbfwa.org) and tables supporting the old river reach system or early attempts at 100K georeferencing. This edition does include many updates to Trend and count data, as well as more complete population of tables such as Waterbody.
One major change is the addition of the Qx tables, as we call them around here. While the Trend table mirrors the Data Exchange Format, it also includes a QID field at the end which contains the appropriate location code identified by the LocTypeID, i.e. LLID or SuperCode or WaterBody or PointID. The QID and LocTypeID fields will link easily to the QMaster table to provide a name for any location, the QxState table to return the State, and the QxCounty, QxRegion, QxSubbasin and QxHUC tables to return those values. The Qx tables were created because of the need to have a single field for the Web Query System to query for these lookups. Though the QID field represents some redundancy within the Trend table, it eliminates the need to have LLIDxState, WaterbodyXState, CountyXState, etc. Given that we already have the LocTypeID coding and only one logical location per TrendID, we may want to remove some of the redundancy in the future, after careful assessment of any required reprogramming costs with user interface tools and agency database structures. For many needs, we find the Qx tables and the QMaster table much easier to use than linking to various location tables, so we've included them for you to use as well. If you need an LLIDxState table, etc., you can create one with the Build an LLIDxState table example "make table query" included. If you would want just one state, add that StateID to the criteria. Additional LLIDx tables such as LLIDxCounty would be made in a similar way using the QxCounty table.