mpcaHydro 2.0.6__py3-none-any.whl → 2.1.0__py3-none-any.whl

mpcaHydro/warehouse.py

@@ -1,7 +1,6 @@
 import duckdb
 import pandas as pd
 from pathlib import Path
-from mpcaHydro import outlets
 
 def init_db(db_path: str,reset: bool = False):
     """
@@ -15,14 +14,14 @@ def init_db(db_path: str,reset: bool = False):
         # Create all schemas
         create_schemas(con)
 
-        # Create tables
-        create_outlets_tables(con)
-        create_mapping_tables(con)
-        create_analytics_tables(con)
+        # Create tables for observational data
+        # Wrapped in try/except as they depend on tables that may not exist yet
+        try:
+            create_combined_observations_view(con)
+            create_constituent_summary_report(con)
+        except duckdb.CatalogException as e:
+            print(f"Could not create observation views, likely because backing tables don't exist yet. This is safe to ignore on first run. Details: {e}")
 
-        # Create views
-        #update_views(con)
-        
 
 def create_schemas(con: duckdb.DuckDBPyConnection):
     """
@@ -31,245 +30,8 @@ def create_schemas(con: duckdb.DuckDBPyConnection):
     con.execute("CREATE SCHEMA IF NOT EXISTS staging")
     con.execute("CREATE SCHEMA IF NOT EXISTS analytics")
     con.execute("CREATE SCHEMA IF NOT EXISTS reports")
-    con.execute("CREATE SCHEMA IF NOT EXISTS outlets")
-    con.execute("CREATE SCHEMA IF NOT EXISTS mappings")
+    con.execute("CREATE SCHEMA IF NOT EXISTS hspf")
 
-def create_analytics_tables(con: duckdb.DuckDBPyConnection):
-    """
-    Create necessary tables in the analytics schema.
-    """
-    con.execute("""
-    CREATE TABLE IF NOT EXISTS analytics.equis (
-        datetime TIMESTAMP,
-        value DOUBLE,
-        station_id TEXT,
-        station_origin TEXT,
-        constituent TEXT,
-        unit TEXT
-    );
-    """)
-    con.execute("""
-    CREATE TABLE IF NOT EXISTS analytics.wiski (
-        datetime TIMESTAMP,
-        value DOUBLE,
-        station_id TEXT,
-        station_origin TEXT,
-        constituent TEXT,
-        unit TEXT
-    );
-    """)
-
-def create_mapping_tables(con: duckdb.DuckDBPyConnection):
-    """
-    Create and populate tables in the mappings schema from Python dicts and CSVs.
-    """
-    # WISKI parametertype_id -> constituent
-    wiski_parametertype_map = {
-        '11522': 'TP', 
-        '11531': 'TP', 
-        '11532': 'TSS', 
-        '11523': 'TSS',
-        '11526': 'N', 
-        '11519': 'N', 
-        '11520': 'OP', 
-        '11528': 'OP',
-        '11530': 'TKN', 
-        '11521': 'TKN', 
-        '11500': 'Q', 
-        '11504': 'WT',
-        '11533': 'DO', 
-        '11507': 'WL'
-    }
-    df_wiski_params = pd.DataFrame(wiski_parametertype_map.items(), columns=['parametertype_id', 'constituent'])
-    con.execute("CREATE TABLE IF NOT EXISTS mappings.wiski_parametertype AS SELECT * FROM df_wiski_params")
-
-    # EQuIS cas_rn -> constituent
-    equis_casrn_map = {
-        '479-61-8': 'CHLA', 
-        'CHLA-CORR': 'CHLA', 
-        'BOD': 'BOD', 
-        'NO2NO3': 'N',
-        '14797-55-8': 'NO3', 
-        '14797-65-0': 'NO2', 
-        '14265-44-2': 'OP',
-        'N-KJEL': 'TKN', 
-        'PHOSPHATE-P': 'TP', 
-        '7723-14-0': 'TP',
-        'SOLIDS-TSS': 'TSS', 
-        'TEMP-W': 'WT', 
-        '7664-41-7': 'NH3'
-    }
-    df_equis_cas = pd.DataFrame(equis_casrn_map.items(), columns=['cas_rn', 'constituent'])
-    con.execute("CREATE TABLE IF NOT EXISTS mappings.equis_casrn AS SELECT * FROM df_equis_cas")
-
-    # Load station cross-reference from CSV
-    # Assumes this script is run from a location where this relative path is valid
-    xref_csv_path = Path(__file__).parent / 'data/WISKI_EQUIS_XREF.csv'
-    if xref_csv_path.exists():
-        con.execute(f"CREATE TABLE IF NOT EXISTS mappings.station_xref AS SELECT * FROM read_csv_auto('{xref_csv_path.as_posix()}')")
-    else:
-        print(f"Warning: WISKI_EQUIS_XREF.csv not found at {xref_csv_path}")
-
-    # Load wiski_quality_codes from CSV
-    wiski_qc_csv_path = Path(__file__).parent / 'data/WISKI_QUALITY_CODES.csv'
-    if wiski_qc_csv_path.exists():
-        con.execute(f"CREATE TABLE IF NOT EXISTS mappings.wiski_quality_codes AS SELECT * FROM read_csv_auto('{wiski_qc_csv_path.as_posix()}')")
-    else:
-            print(f"Warning: WISKI_QUALITY_CODES.csv not found at {wiski_qc_csv_path}")
-
-def create_outlets_tables(con: duckdb.DuckDBPyConnection):
-    """
-    Create tables in the outlets schema to define outlet-station-reach relationships.
-    """
-    con.execute("""-- schema.sql
-            -- Simple 3-table design to manage associations between model reaches and observation stations via outlets.
-            -- Compatible with DuckDB and SQLite.
-
-            -- Table 1: outlets
-            -- Represents a logical grouping that ties stations and reaches together.
-            CREATE TABLE IF NOT EXISTS outlets.outlets (
-            outlet_id TEXT PRIMARY KEY,
-            repository_name TEXT NOT NULL,
-            outlet_name TEXT,
-            notes TEXT             -- optional: general notes about the outlet grouping
-            );
-
-            -- Table 2: outlet_stations
-            -- One-to-many: outlet -> stations
-            CREATE TABLE IF NOT EXISTS outlets.outlet_stations (
-            outlet_id TEXT NOT NULL,
-            station_id TEXT NOT NULL,
-            station_origin TEXT NOT NULL,       -- e.g., 'wiski', 'equis'
-            repository_name TEXT NOT NULL,  -- repository model the station is physically located in
-            true_opnid TEXT NOT NULL,           -- The specific reach the station physically sits on (optional)
-            comments TEXT,             -- Per-station comments, issues, etc.
-            CONSTRAINT uq_station_origin UNIQUE (station_id, station_origin),
-            FOREIGN KEY (outlet_id) REFERENCES outlets.outlets(outlet_id)
-            );
-
-            -- Table 3: outlet_reaches
-            -- One-to-many: outlet -> reaches
-            -- A reach can appear in multiple outlets, enabling many-to-many overall.
-            CREATE TABLE IF NOT EXISTS outlets.outlet_reaches (
-            outlet_id TEXT NOT NULL,
-            reach_id TEXT NOT NULL,    -- model reach identifier (aka opind)
-            repository_name TEXT NOT NULL,  -- optional: where the mapping comes from
-            exclude INTEGER DEFAULT 0, -- flag to indicate if this reach should be excluded (1) or included (0)
-            FOREIGN KEY (outlet_id) REFERENCES outlets.outlets(outlet_id)
-            );
-
-            -- Useful views:
-
-            -- View: station_reach_pairs
-            -- Derives the implicit many-to-many station <-> reach relationship via shared outlet_id
-            CREATE VIEW IF NOT EXISTS outlets.station_reach_pairs AS
-            SELECT
-            s.outlet_id,
-            s.station_id,
-            s.station_origin,
-            r.reach_id,
-            r.exclude,
-            r.repository_name,
-            FROM outlets.outlet_stations s
-            JOIN outlets.outlet_reaches r
-            ON s.outlet_id = r.outlet_id;
-
-          """)
-
-def create_normalized_wiski_view(con: duckdb.DuckDBPyConnection):
-    """
-    Create a view in the database that contains normalized WISKI data.
-    Units converted to standard units.
-    columns renamed.
-    constituents mapped.
-    """
-    con.execute("""
-    -- Create a single view with all transformations
-    CREATE OR REPLACE VIEW analytics.wiski_normalized AS
-    SELECT 
-        
-        -- Convert °C to °F and keep other values unchanged
-        CASE 
-            WHEN LOWER(ts_unitsymbol) = '°c' THEN (value * 9.0 / 5.0) + 32
-            WHEN ts_unitsymbol = 'kg' THEN value * 2.20462    -- Convert kg to lb
-            ELSE value
-        END AS value,
-
-        -- Normalize units
-        CASE 
-            WHEN LOWER(ts_unitsymbol) = '°c' THEN 'degf'      -- Normalize °C to degF
-            WHEN ts_unitsymbol = 'kg' THEN 'lb'              -- Normalize kg to lb
-            WHEN ts_unitsymbol = 'ft³/s' THEN 'cfs'          -- Rename ft³/s to cfs
-            ELSE ts_unitsymbol
-        END AS unit,
-
-        -- Normalize column names
-        station_no AS station_id,                             -- Rename station_no to station_id
-        Timestamp AS datetime,                                -- Rename Timestamp to datetime
-        "Quality Code" AS quality_code,                      -- Rename Quality Code to quality_code
-        "Quality Code Name" AS quality_code_name,            -- Rename Quality Code Name to quality_code_name
-        parametertype_id,                                    -- Keeps parametertype_id as is
-        constituent                                          -- Keeps constituent as is
-    FROM staging.wiski_raw;""")
-
-
-def create_filtered_wiski_view(con: duckdb.DuckDBPyConnection, data_codes: list):
-    """
-    Create a view in the database that filters WISKI data based on specified data codes.
-    """
-    query = f"""
-    CREATE OR REPLACE VIEW analytics.wiski_filtered AS
-    SELECT *
-    FROM analytics.wiski_normalized
-    WHERE quality_code IN ({placeholders});
-    """
-
-    placeholders = ', '.join(['?'] * len(data_codes))
-    query = query.format(placeholders=placeholders)
-    con.execute(query, data_codes)
-
-
-def create_aggregated_wiski_view(con: duckdb.DuckDBPyConnection):
-    """
-    Create a view in the database that aggregates WISKI data by hour, station, and constituent.
-    """
-    con.execute("""
-    CREATE OR REPLACE Table analytics.wiski_aggregated AS
-    SELECT 
-        station_id,
-        constituent,
-        time_bucket(INTERVAL '1 hour', datetime) AS hour_start,
-        AVG(value) AS value,
-        unit
-    FROM analytics.wiski_normalized
-    GROUP BY 
-        station_id, 
-        constituent, 
-        hour_start,
-        unit;
-    """)
-
-def create_staging_qc_count_view(con: duckdb.DuckDBPyConnection):
-    """
-    Create a view in staging schema that counts quality codes for each station and constituent.
-    """
-    con.execute("""
-    CREATE OR REPLACE VIEW staging.wiski_qc_count AS (
-        SELECT 
-            w.station_no,
-            w.parametertype_name,
-            w."Quality Code",
-            w."Quality Code Name",
-            COUNT(w."Quality Code") AS count
-        FROM staging.wiski_raw w 
-        GROUP BY
-            w."Quality Code",w."Quality Code Name",w.parametertype_name, w.station_no
-                );
-        """)
-    # ORDER BY
-    #         w.station_no,w.parametertype_name, w."Quality Code"
-    #         )
-    # """)
 
 def create_combined_observations_view(con: duckdb.DuckDBPyConnection):
     """
@@ -285,87 +47,6 @@ def create_combined_observations_view(con: duckdb.DuckDBPyConnection):
     """)
 
 
-def create_outlet_observations_view(con: duckdb.DuckDBPyConnection):
-    """
-    Create a view in analytics schema that links observations to model reaches via outlets.
-    """
-    con.execute("""
-    CREATE OR REPLACE VIEW analytics.outlet_observations AS 
-    SELECT
-        o.datetime,
-        os.outlet_id,
-        o.constituent,
-        AVG(o.value) AS value,
-        COUNT(o.value) AS count
-    FROM
-        analytics.observations AS o
-    LEFT JOIN
-        outlets.outlet_stations AS os ON o.station_id = os.station_id AND o.station_origin = os.station_origin
-    GROUP BY
-        os.outlet_id,
-        o.constituent,
-        o.datetime; -- Group by the truncated date
-    """)
-    # ORDER BY
-    #     os.outlet_id,
-    #     o.constituent,
-    #     datetime);
-
-
-
-def create_outlet_observations_with_flow_view(con: duckdb.DuckDBPyConnection):
-    
-    con.execute("""
-    CREATE OR REPLACE VIEW analytics.outlet_observations_with_flow AS 
-        WITH baseflow_data AS (
-            SELECT
-                outlet_id,
-                datetime,
-                "value" AS baseflow_value
-            FROM
-                analytics.outlet_observations
-            WHERE
-                (constituent = 'QB')),
-        flow_data AS (
-            SELECT
-                outlet_id,
-                datetime,
-                "value" AS flow_value
-            FROM
-                analytics.outlet_observations
-            WHERE
-                (constituent = 'Q')),
-        constituent_data AS (
-            SELECT
-                outlet_id,
-                datetime,
-                constituent,
-                "value",
-                count
-            FROM
-                analytics.outlet_observations
-            WHERE
-                (constituent NOT IN ('Q', 'QB')))
-        SELECT
-            constituent_data.outlet_id,
-            constituent_data.constituent,
-            constituent_data.datetime,
-            constituent_data."value",
-            flow_data.flow_value,
-            baseflow_data.baseflow_value
-        FROM
-            constituent_data
-        FULL JOIN flow_data ON
-            (((constituent_data.outlet_id = flow_data.outlet_id)
-                AND (constituent_data.datetime = flow_data.datetime)))
-        LEFT JOIN baseflow_data ON
-            (((constituent_data.outlet_id = baseflow_data.outlet_id)
-                AND (constituent_data.datetime = baseflow_data.datetime)));""")
-    # ORDER BY
-    #     constituent_data.outlet_id,
-    #     constituent_data.datetime;
-    # 
-
 def create_constituent_summary_report(con: duckdb.DuckDBPyConnection):
     """
     Create a constituent summary report in the reports schema that groups observations by constituent and station.
@@ -385,54 +66,11 @@ def create_constituent_summary_report(con: duckdb.DuckDBPyConnection):
             FROM
             analytics.observations
             GROUP BY
-            constituent,station_id,station_origin;
-            ''')
-                
-            # ORDER BY
-            # constituent,sample_count;''')
-
-def create_outlet_summary_report(con: duckdb.DuckDBPyConnection):
-    con.execute("""
-        CREATE VIEW reports.outlet_constituent_summary AS
-    SELECT
-        outlet_id,
-        constituent,
-        count_star() AS sample_count,
-        avg("value") AS average_value,
-        min("value") AS min_value,
-        max("value") AS max_value,
-        "year"(min(datetime)) AS start_date,
-        "year"(max(datetime)) AS end_date
-    FROM
-        analytics.outlet_observations
-    GROUP BY
-        constituent,
-        outlet_id
-    """)
+            constituent,station_id,station_origin
+            ORDER BY
+            constituent,sample_count;''')
 
-    
-       
-def drop_station_id(con: duckdb.DuckDBPyConnection, station_id: str,station_origin: str):
-    """
-    Drop all data for a specific station from staging and analytics schemas.
-    """
-    con.execute(f"DELETE FROM staging.equis_raw WHERE station_id = '{station_id}' AND station_origin = '{station_origin}'")
-    con.execute(f"DELETE FROM staging.wiski_raw WHERE station_id = '{station_id}' AND station_origin = '{station_origin}'")
-    con.execute(f"DELETE FROM analytics.equis WHERE station_id = '{station_id}' AND station_origin = '{station_origin}'")
-    con.execute(f"DELETE FROM analytics.wiski WHERE station_id = '{station_id}' AND station_origin = '{station_origin}'")
-    update_views(con)
 
-def update_views(con: duckdb.DuckDBPyConnection):
-    """
-    Update all views in the database.
-    """
-    create_staging_qc_count_view(con)
-    create_combined_observations_view(con)
-    create_constituent_summary_report(con)
-    create_outlet_observations_view(con)
-    create_outlet_observations_with_flow_view(con)
-    create_outlet_summary_report(con)
-    
 def connect(db_path: str, read_only: bool = False) -> duckdb.DuckDBPyConnection:
     """
     Returns a DuckDB connection to the given database path.
@@ -468,22 +106,6 @@ def load_df_to_staging(con: duckdb.DuckDBPyConnection, df: pd.DataFrame, table_n
     con.execute(f"CREATE TABLE staging.{table_name} AS SELECT * FROM tmp_df")
     con.unregister("tmp_df")
 
-def add_df_to_staging(con: duckdb.DuckDBPyConnection, df: pd.DataFrame, table_name: str):
-    """
-    Append a pandas DataFrame into a staging table. This will create the staging
-    table if it does not exist.
-    """
-    # register pandas DF and create table if not exists
-    con.register("tmp_df", df)
-    con.execute(f"""
-        CREATE TABLE IF NOT EXISTS staging.{table_name} AS 
-        SELECT * FROM tmp_df
-    """)
-    con.execute(f"""
-        INSERT INTO staging.{table_name} 
-        SELECT * FROM tmp_df
-    """)
-    con.unregister("tmp_df")
 
 def load_csv_to_staging(con: duckdb.DuckDBPyConnection, csv_path: str, table_name: str, replace: bool = True, **read_csv_kwargs):
     """

{mpcahydro-2.0.6.dist-info → mpcahydro-2.1.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mpcaHydro
-Version: 2.0.6
+Version: 2.1.0
 Summary: Python package for downloading MPCA hydrology data
 Project-URL: Homepage, https://github.com/mfratkin1/mpcaHydro
 Author-email: Mulu Fratkin <michael.fratkin@state.mn.us>
@@ -10,9 +10,7 @@ Keywords: Hydrology,MPCA
 Classifier: Development Status :: 3 - Alpha
 Classifier: Programming Language :: Python
 Requires-Python: >=3.8
-Requires-Dist: baseflow
 Requires-Dist: duckdb
-Requires-Dist: oracledb
 Requires-Dist: pandas
 Requires-Dist: pathlib
 Requires-Dist: requests

mpcahydro-2.1.0.dist-info/RECORD

@@ -0,0 +1,15 @@
+mpcaHydro/WISKI.py,sha256=VWPwmDGv6rKFHgiQrcn4fAyx-h43Tyf8Vjtewa49yj4,11022
+mpcaHydro/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+mpcaHydro/data_manager.py,sha256=LofBoNfhfStQlzD8EK1in_15BtNv_8q8057cjK4TmbA,15611
+mpcaHydro/equis.py,sha256=R4BEAkj9I6hVhSmd4WjjMLyQXBcOL5B2YIZjwm4EtqE,17943
+mpcaHydro/etlCSG.py,sha256=5QT6V2dHvNKC9r5-dspt-NpOmECP2LFw1Lyq1zdkqps,2630
+mpcaHydro/etlSWD.py,sha256=FvFP5lIOxtzF3eEgUDGw-C2BJTRfxXxkbt3hYl8PCZQ,6367
+mpcaHydro/etlWISKI.py,sha256=S1dNUe08Y0riJNBaEJDfgmewR8CwPtIaB_3Vw8JujkM,22201
+mpcaHydro/etlWPLMN.py,sha256=avLJvWRRxsG35w--OVq0qSCrFjO6G2x0aQ31d9kcYHg,4179
+mpcaHydro/pywisk.py,sha256=kaxJCPCZHy9oEo9VnoSmFC58qm1sX9fVbtp6nXs7934,13290
+mpcaHydro/warehouse.py,sha256=Rn8onCs9R-EnU9XNA1Gy53B-PAIhW_YaCLBDO29zyMY,7786
+mpcaHydro/data/EQUIS_PARAMETER_XREF.csv,sha256=XZPrcZan9irSqFd4UasnPo_NQBcjyFodi0q3FGQphjI,5667
+mpcaHydro/data/WISKI_EQUIS_XREF.csv,sha256=bPYq-f4-Qc6jsvUgl81lwXBeFamfDe5TjohqUV1XJlg,1244704
+mpcahydro-2.1.0.dist-info/METADATA,sha256=LyNxLeMkwdtq1ox-2ygVqPjqUPk5rFCseONZfziJEwg,543
+mpcahydro-2.1.0.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
+mpcahydro-2.1.0.dist-info/RECORD,,

mpcaHydro/data/WISKI_QUALITY_CODES.csv

@@ -1,71 +0,0 @@
-quality_code,Text,Description,Active
-0,Unchecked,Unchecked data in progress or data that is not quality coded as part of the workup.  Default coding for shifts so the quality codes from Level and Ratings are used for discharges. ,1
-3,Instantaneous,Instantaneous groundwater measurements or sampled date for load stations.,1
-5,Excellent,Discharge measurements that are excellent.,1
-8,Reliable Interpolation,The value of the data point is an interpolation between adjacent points.  Code used for filling gaps less than 4 hours or with no change in data trend likely based on reference information.,1
-10,Good,Time series data that tracks well and requires no corrections or corrections of very small magnitude or  timeseries data that has been reviewed and accepted for precipitation and groundwater level. Also used for discharge measurements and rating points.  ,1
-15,Fair,Time series data that tracks fairly well and requires some corrections of relatively small magnitude. Also used for discharge measurements and rating points.  ,1
-20,Poor,Time series data that tracks poorly and requires significant or many corrections. Also used for discharge measurements and rating points. ,1
-27,Questionable,"Timeseries data or discharge measurements that are questionable due to operator error, equipment error, etc). Extra scrutiny should be used for these data. ",1
-28,Unknown data quality,"Unknown quality of time series data, ratings or discharge measurements.",1
-29,Modeled,"Time-series data, rating point or discharge from a reliable mathematical and\or computer model. ",1
-34,Estimated,"Time-series data estimated from reference traces, models or extrapolation of the rating curve using supporting data and up to two times the maximum measured discharge.",1
-35,Unreliable,Time-series data computed with a rating extrapolated without supporting data or beyond two times the maximum measured discharge without a model.,1
-36,Threshold Exceedance,"Time-series data may be beyond the measuring limits of the monitoring equipment, or outside the bounds of historical extremes.",1
-40,Default import code,WISKI default coding for gaugings. ,1
-45,Approved Ext Data,"External data that has been graded externally as ""Approved"".",1
-48,Unknown Ext Data,External data that has been graded internally as “Unknown”.,1
-49,Estimated Ext Data,External data that has been graded externally as “Estimated.”  Typically this is finalized ice data.,1
-50,Provisional Ext Data,External data that has been graded internally or externally as “Provisional”.,1
-80,Ice - Estimated,Ice affected time series data. Discharge computed with ice affected stage data is considered estimated.,1
-199,199-Logger Unknown,Initial code for data coming to the system from the logger.,1
-200,200,Initial code for data coming to the system from telemetry or default coding for WISKI timeseries. ,1
-228,Info Parameter,This parameter is collected for informational purposes only.  Data has been through a cursory check only.  This is stored in the database and available upon request.,1
-255,---,System assigned code for gaps in the data set.  Records with null values. ,1
-1,Continuous Data,~Discontinued~ Good TS data that requires no correction.,0
-2,Edited Data,~Discontinued~ TS data that has been edited.  Typically used when spikes are removed or when points are edited manual for datum corrections.,0
-3,Instantaneous Data,Final WQ data.,0
-4,Questionable data,~Discontinued~,0
-5,Excellent measurment,Used to indicated discharge measurements that are excellent as well as excellent sections of the rating.,0
-10,Good measurement,Used to indicated discharge measurements and sections of the rating that are good and time series data that tracks well and requires no corrections or corrections of very small magnitude.,0
-12,Modeled measurement,~Discontinued~ Rating point or discharge was obtained from a relizble mathematical and/or computer model. After 3/1/11 use QC148.,0
-15,Fair measurement,Used to indicated discharge measurements and sections of the rating that are fair and time series data that tracks fairly well and requires some corrections of relatively small magnitude.,0
-20,Poor measurement,Used to indicated discharge measurements and sections of the rating that are poor and time series data that tracks poorly and requires significant or many corrections.,0
-25,Unknown measurement,Measurement data not available.,0
-27,Questionable data,"Flow measurement is very poor and should be given extra scrutiny or time series data that is questionable due to operator error, equipment error, etc.",0
-30,Good Archived Daily Value,This code is used for archived daily value data that is considered “Good”.,0
-31,Fair Archived Daily Value,This code is used for archived daily value data that is considered “Fair”.,0
-32,Poor Archived Daily Value,This code is used for archived daily value data that is considered “Poor”.,0
-33,Unknown Archived Daily Value,This code is used for archived daily value data that has unknown quality based on lack of documentation.,0
-34,Estimated Archived Daily Value,This code is used for archived daily value data that has been estimated.,0
-35,Unreliable Archived Daily Value,This code is used for archived daily value data that is unreliable based on the quality of the supporting time series data and/or rating.,0
-45,Good External Data,This code is used for external data that has been graded internally as “Good”.,0
-46,Fair External Data,This code is used for external data that has been graded internally as “Fair”.,0
-47,Poor External Data,This code is used for external data that has been graded internally as “Poor”.,0
-48,Unknown External Data,This code is used for external data that has been graded internally as “Unknown”,0
-49,Estimated External Data,This code is used for external data that has been graded externally as “Estimated.”  Typically this is finalized ice data.,0
-50,Provisional External Data,This code is used for external data that has been graded internally as “Provisional”,0
-51,Telemetry data - DCP,This code is used for time-series data when imported into hydstra using an automated telemetry method that accesses a DCP through the GOES network.  The “questionable measurement” flag is set through the shef code that accompanies the DCP data.,0
-60,Above rating,~Discontinued~,0
-70,Estimated Data,Value of the data point is estimated.,0
-76,Reliable interpolation,Value of the data point is an interpolation between adjacent points. ,0
-80,Ice,"(DISCONTINUED) Used to indicate ice conditions when the data should not be exported. Use in conjunction with 80 to code 232.00 values, run USDAY to compute daily flow, then recode 232.00 80 values to 180 so unit value export cannot occur.",0
-82,Linear interpolation across a gap in records,~Discontinued~  Points that were added to fill a gap in the data record.  The points fall on a straight line between the end points of the gap. This code was changed to 8 in WISKI.,0
-103,Provisional Instantaneous Data,Provisional WQ data.,0
-130,Good Provisional Daily Value,This code is used for archived daily value data that is considered “Good” but Provisional because there is only one year of gaging measurements.,0
-131,Fair Provisional Daily Value,This code is used for archived daily value data that is considered “Fair” but Provisional because there is only one year of gaging measurements.,0
-132,Poor Provisional Daily Value,This code is used for archived daily value data that is considered “Poor” but Provisional because there is only one year of gaging measurements.,0
-133,Unknown Provisional Archived Daily Value,This code is used for archived daily value data that has unknown quality based on lack of documentation but Provisional because there is only one year of gaging measurements.,0
-134,Estimated Provisional Archived Daily Value,This code is used for archived daily value data that has been estimated but Provisional because there is only one year of gaging measurements.,0
-135,Unreliable Provisional Archived Daily Value,This code is used for archived daily value data that is unreliable based on the quality of the supporting time series data and/or rating but Provisional because there is only one year of gaging measurements.,0
-140,Data not yet checked,This code is used for time-series data when it is initially imported into hydstra using manual import methods.  ,0
-141,Telemetry data - not yet checked,This code is used for time-series data when it is imported into hydstra using an automated telemetry method.,0
-148,Modeled measurement,Rating point or discharge was obtained from a reliable mathematical and/or computer model.,0
-149,Extrapolated rating point,Rating point accurately extrapolated using supporting data and is less than two times the maxiumum measured discharge.,0
-150,Over-extrapolated rating point,Rating point extrapolated without supporting data or beyone two times the maximum measured discharge without a mathematical model.,0
-151,Data Missing,"This code is used to flag the end of a period of missing time-series data, before the next good data value.",0
-160,Above rating,~Discontinued~,0
-169,Datalogger Hardware Error Code 6999,"This code is used to indicate that a time-series point had a value of 6999 or -6999, a typical hardware error code, and the value was changed.",0
-170,Estimated Data,"Used to indicate estimated data when the data should not be exported.  Often used in conjunction with 70 to code 232.00 values, run USDAY to compute daily flow, then recode 232.00 70 values to 170 so unit value export can not occur.",0
-180,Ice,Used to indicate ice conditions.,0
-255,Data Missing,This code is used when data is exported and does not exist for a given time period.,0