{"action":"create","ckan_id":null,"date_created":"Tue, 31 Mar 2026 00:03:02 GMT","date_finished":null,"harvest_job_id":"52d231e5-aff4-4efa-8a30-b235ca584dc9","harvest_source_id":"4c62556f-0fa3-402d-90f6-6a46cd80a117","id":"44359893-2acb-4873-a499-310f8d2d5271","identifier":"https://hazards.fema.gov/filedownload/metadata/R10/2076019-DevHydrologicData.xml","parent_identifier":null,"source_hash":"3de87f857aa574d9b82c504f08882ab341e2b7ad3b2846a51fc84c5e00690256","source_raw":"\r\n\r\n \r\n \r\n \r\n Federal Emergency Management Agency\r\n 20250613\r\n DCS Hydrology Submission for Kittitas County\r\n\tVersion 2.8.5.6\r\n FEMA-DCS-Hydrology\r\n \r\n Washington, DC\r\n Federal Emergency Management Agency\r\n \r\n https://hazards.fema.gov\r\n \r\n \r\n Federal Emergency Management Agency\r\n Unknown\r\n FEMA CASE 24-10-0007S\r\n \r\n \r\n \r\n \r\n \r\n Hydrology data include spatial datasets and data tables necessary for documenting the hydrologic procedures for estimating flood discharges for a Flood Insurance Study, which include the hydrologic data expected by FEMA for new riverline studies. (Source: FEMA Guidelines and Standards for Flood Risk Analysis and Mapping.)\r\n The objective of this Hydrology data submission is to archive the hydrologic data for a study in a database such that it can be revised and used with minimum effort in future Flood Insurance Studies or map revisions.\r\n \r\n \r\n \r\n \r\n 20250613\r\n \r\n \r\n MIP Submission Date\r\n \r\n \r\n Complete\r\n Unknown\r\n \r\n \r\n \r\n -120.899609\r\n -120.197708\r\n 47.237327\r\n 46.844435\r\n \r\n \r\n \r\n \r\n ISO 19115 Topic Category\r\n environment\r\n inlandWaters\r\n \r\n \r\n FEMA NFIP Topic Category\r\n Hydrology\r\n Flood Insurance Rate Map\r\n FIRM\r\n Flood Hazard Data\r\n 0.2-Percent-Annual-Chance Flood\r\n 1-Percent-Annual-Chance Flood \r\n \t2-Percent-Annual-Chance Flood\r\n 4-Percent-Annual-Chance Flood\r\n 10-Percent-Annual-Chance Flood\r\n 1-Percent-Plus-Annual-Chance Flood\r\n 1-Percent-Minus-Annual-Chance Flood\r\n Channel\r\n Regression Equation\r\n Rainfall-runoff\r\n Imperviousness\r\n Stream\r\n Water Body\r\n Watershed/Basin\r\n Hydrologic Reach\r\n Node\r\n \r\n \r\n None\r\n REGION 10\r\n STATE WA\r\n COUNTY KITTITAS\r\n COUNTY-FIPS 53037\r\n COMMUNITY KITTITAS COUNTY UNINCORPORATED AREAS\r\n FEMA-CID \t530095\r\n\t\tCOMMUNITY CITY OF KITTITAS\r\n FEMA-CID \t530098\r\n\t\tCOMMUNITY CITY OF CLE ELUM\r\n FEMA-CID \t530096\r\n HYDROLOGIC UNIT 17030001\r\n \r\n \r\n None\r\n Acknowledgement of FEMA would be appreciated in products derived from these data. These digital data are produced for the purposes of updating/creating a FIRM Database and/or Flood Risk Products.\r\n Original data development environment may vary. Finishing of the data is done using Esri's ArcGIS software. The submitted geodatabase was created using ArcGIS version 10.3. The hydrologic modeling was performed using Regression/NFF\r\n \r\n \r\n \r\n The FIRM Database consists of vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and FIRM Database are issued as the official designation of the SFHAs. As such they are adopted by local communities and form the basis for administration of the NFIP. For these purposes they are authoritative. Provisions exist in the regulations for public review, appeals and corrections of the flood risk information shown to better match real world conditions. As with any engineering analysis of this type, variation from the estimated flood heights and floodplain boundaries is possible. Details of FEMA's requirements for the FISs and flood mapping process that produces these data are available in the Guidelines and Standards for Flood Risk Analysis and Mapping. Attribute accuracy was tested by manual comparison of source graphics with hardcopy plots and a symbolized display on an interactive computer graphic system. \r\nIndependent quality control testing of the FIRM Database was also performed.\r\n \r\n Proven hydrologic methods and/or FEMA approved models are used to compute flows at different locations and for different recurrence intervals (e.g., 1-percent-annual-chance (100-year) event, the 10-percent-annual-chance (10-year), 4-percent-annual-chance (25-year), 2-percent-annual-chance (50-year), and 0.2-percent-annual-chance (500-year) event). Computed flows are compared with historic data and flows established in previous hydrologic investigations to ensure reasonableness. Flows at the confluences are checked for the possibility of coincident peaks. Flows exiting the system and regulated by dams are carefully analyzed. At a given location flows for longer recurrence intervals are larger.\r\n Flows are computed at different locations of the study area. The method(s) and/or model(s) are described in the FIS Report. Assumptions and special considerations are also clearly stated in the report. Flows previously determined in other studies or hydrologic investigations are used for comparison. Computed flows are compared with historic flooding data. Submittal of hydrologic data in accordance with FEMA's Data Capture Technical Reference ensures completeness of the Hydrology Study submittal.\r\n \r\n \r\n The FIRM Database consists of vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and FIRM Database are issued as the official designation of the SFHAs. As such they are adopted by local communities and form the basis for administration of the NFIP. For these purposes they are authoritative. Provisions exist in the regulations for public review, appeals and corrections of the flood risk information shown to better match real world conditions. As with any engineering analysis of this type, variation from the estimated flood heights and floodplain boundaries is possible. Details of FEMA's requirements for the FIS and flood mapping process that produces these data are available in the Guidelines and Standards for Flood Risk Analysis and Mapping. Horizontal accuracy was tested by manual comparison of source graphics with hardcopy plots and a symbolized display on an interactive computer graphic system. Independent quality control testing of the FIRM Database was also performed.\r\n \r\n \r\n \r\n\r\n \r\n \r\n \r\n STARR II 2025\r\n 20250613\r\n Kittitas County Hydrology Study\r\n \r\n \r\n online\r\n \r\n \r\n \r\n 20250613\r\n \r\n \r\n publication date\r\n \r\n STUDY1\r\n STARR II used regression equations and rainfall-runoff modeling to compute peak discharges for study streams\r\n \r\n \r\n Process steps include selection of method(s) and/or model(s), preparation of input data and computing/modeling. Preparation of input data involves compilation of rain and/or flow gage data; delineation of sub-basins; and processing of topographic, landuse and soil data, if used.\r\n 20250613\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n Universal Transverse Mercator\r\n \r\n 11\r\n \r\n 0.9996\r\n -117.0\r\n 0.0\r\n 500000\r\n 0.0\r\n \r\n \r\n \r\n \r\n coordinate pair\r\n \r\n 0.000172\r\n 0.000172\r\n \r\n meters\r\n \r\n \r\n \r\n North American Datum of 1983\r\n Geodetic Reference System 80\r\n 6378137\r\n 298.25\r\n \r\n \r\n \r\n \r\n \r\n \r\n S_Hydro_Reach\r\n Location and attributes for lines that represent the connectivity between the subbasins and flow direction between nodes within the study area.\r\n FEMA FIRM Database Technical Reference (available at https://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).\r\n \r\n \r\n \r\n \r\n S_Nodes\r\n A spatial dataset consisting of points that depict locations of computed discharges for the 10-, 4-, 2-, 1-, and 0.2-percent-annual-chance floods.\r\n FEMA FIRM Database Technical Reference (available at https://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).\r\n \r\n \r\n \r\n \r\n S_Subbasins\r\n A spatial dataset consisting of polygons representing watershed or subwatershed areas contributing runoff to the discharge points used in the hydrologic analysis.\r\n FEMA FIRM Database Technical Reference (available at https://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).\r\n \r\n \r\n \r\n \r\n S_Submittal_Info\r\n A spatial dataset consisting of polygons depicting the extents of the studied area.\r\n FEMA FIRM Database Technical Reference (available at https://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).\r\n \r\n \r\n \r\n The Hydrology submission is made up of several data themes containing both spatial and attribute information. These data together represent the current hydrology for the subject area as identified by FEMA. The hydrology data may include gages, node discharges and elevations, network connectivity, basins, and other data related to the NFIP.\r\n FEMA's FIRM Database Technical Reference contains a detailed description of each attribute code and a reference to other relevant information.\r\n \r\n \r\n \r\n \r\n \r\n \r\n FEMA, Mapping Information Platform\r\n \r\n \r\n mailing\r\n
500 C Street, S.W.
\r\n Washington\r\n District of Columbia\r\n 20472\r\n USA\r\n \r\n 1-877-336-2627\r\n miphelp@riskmapcds.com\r\n \r\n \r\n No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty.\r\n \r\n \r\n \r\n FEMA-DCS-Hydrology\r\n \r\n \r\n \r\n \r\n \r\n https://hazards.fema.gov\r\n \r\n \r\n \r\n \r\n \r\n Contact Distributor\r\n \r\n \r\n \r\n 20250604\r\n \r\n \r\n \r\n MIPHelp\r\n Federal Emergency Management Agency\r\n \r\n \r\n mailing\r\n
500 C Street, S.W.
\r\n Washington\r\n District of Columbia\r\n 20472\r\n USA\r\n \r\n 1-877-336-2627\r\n miphelp@riskmapcds.com\r\n \r\n \r\n FGDC Content Standards for Digital Geospatial Metadata\r\n FGDC-STD-001-1998\r\n \r\n https://hazards.fema.gov\r\n http://www.epsg.org\r\n FEMA NFIP Metadata Content and Format Standard\r\n \r\n \r\n\r\n\r\n","source_transform":null,"status":"error"}