Iowa Flood Center Iowa Department of Natural Resources 20160106 Vector Digital Data Set (Polyline) http://programs.iowadnr.gov/nrgislibx/ Small stream centerlines were developed for a dual purpose. The first was to be used to create hydrography for the Iowa DNR's statewide floodplain mapping project in accordance with the Rebuild Iowa Advisory Commission’s 120-Day report to the Governor in November of 2008. The second was to be used to conflate data from the National Hydrography Dataset (NHD) to a more accurate resolution stream network in order to be consistent with the already existing NHD framework. For this reason streams start at 24 acres of flow accumulation where there is a visible channel in the surface of a Digital Elevation Model (DEM) based on the State of Iowa’s LiDAR collection. This linework was the basis for creating hydrologically corrected DEMs that were used to determine the one square mile starting point for modeling flood plains, per FEMA standards and specifications. The linework has been collected using the State of Iowa’s Statewide LiDAR product as the main determination for flow as this surface was used when carrying out Iowa’s Statewide Flood Plain Mapping Project. In cases where LiDAR was insufficient for capture, aerial photography from various years for the State of Iowa was referenced. The NRCSs Eight-Digit Hydrologic Unit boundaries (HUC8) is the Federal Emergency Management Agencies (FEMA) specified unit of study for flood plain mapping designations. Rather than studying by county, FEMA realized that more accurate products resulted from considering an entire HUC8 and gave a more complete look at what contributed/minimized flood damage. Therefore all data was initially compiled into HUC8s, then further compiled into this statewide dataset. This digital, geographically referenced data set was developed by the Iowa Department of Natural Resources to carry out agency responsibilities related to management, protection, and development of Iowa's natural resources. 20070101 20150101 ground condition Complete As needed -96.685270386 -90.072192847 43.557490325 40.332152846 ISO 19115 Topic Category inlandWaters Iowa DNR waters streams stream centerlines GNIS Iowa There are no access constraints for this dataset There are no use constraints for this dataset Iowa Department of Natural Resources Chris Kahle 319-335-2068 ckahle@dnr.iowa.gov State of Iowa Enterprise Data Classification Standard This data is publicly available for distribution. public Esri ArcGIS 10.2 (Build 3348) Service Pack N/A (Build N/A) No formal attribute accuracy tests were conducted. No formal logical accuracy tests were conducted. Data set is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details. Positional accuracy conforms to the LiDAR data standard used as a source for this project. A formal accuracy assessment of the vertical positional information in the data set has either not been conducted, or is not applicable. USDA-FSA Aerial Photography Field Office 20081021 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 24 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20061106 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 22 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20041025 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 20 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20060101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 18 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20100929 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 28 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20100910 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 27 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20091030 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 25 Source information used in support of the development of the data set. U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency, USDA Forest Service, and other Federal, State and local partners (see dataset specific metadata under Data_Set_Credit for details) withheld Digital and/or Hardcopy Resources Source Input 8 Source information used in support of the development of the data set. Iowa Department of Natural Resources unpublished material Digital and/or Hardcopy Resources Source Input 7 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20120101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 16 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20090101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 14 Source information used in support of the development of the data set. Federal Emergency Management Agency http://msc.fema.gov/portal Digital and/or Hardcopy Resources Source Input 12 Source information used in support of the development of the data set. U.S. Department of Agriculture, Natural Resources Conservation Service 20020101 withheld Digital and/or Hardcopy Resources Source Input 10 Source information used in support of the development of the data set. Iowa Department of Natural Resources unpublished material withheld Digital and/or Hardcopy Resources Source Input 9 Source information used in support of the development of the data set. Iowa Department of Natural Resources, US Fish and Wildlife Service 20090603 withheld Digital and/or Hardcopy Resources Source Input 4 Source information used in support of the development of the data set. NRCS-Iowa, Des Moines, Iowa and EPA Region 5, Chicago, Illinois. 20080101 withheld Digital and/or Hardcopy Resources Source Input 3 Source information used in support of the development of the data set. NRCS-Iowa, Des Moines, Iowa and EPA Region 5, Chicago, Illinois. 20080101 withheld Digital and/or Hardcopy Resources Source Input 2 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20110101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 17 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20060101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 13 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20071003 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 23 Source information used in support of the development of the data set. Iowa 2002 Digital Orthophoto Update Project unknown http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 19 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20110818 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 29 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20120101 http://www.igsb.uiowa.edu/nrgislibx/ Digital and/or Hardcopy Resources Source Input 15 Source information used in support of the development of the data set. Brian Gelder unpublished material withheld Digital and/or Hardcopy Resources Source Input 11 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20050911 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 21 Source information used in support of the development of the data set. USDA-FSA Aerial Photography Field Office 20130912 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 30 Source information used in support of the development of the data set. Iowa Department of Natural Resources 20100910 http://www.igsb.uiowa.edu/nrgislibx Digital and/or Hardcopy Resources Source Input 26 Source information used in support of the development of the data set. U.S. Department of Commerce, U.S. Census Bureau, Geography Division 20100101 withheld Digital and/or Hardcopy Resources Source Input 6 Source information used in support of the development of the data set. Iowa Geological Survey of the Iowa Department of Natural Resources 20060420 withheld Digital and/or Hardcopy Resources Source Input 5 Source information used in support of the development of the data set. James D. Giglierano and Madhukar Mohan 19901101 withheld Digital and/or Hardcopy Resources Source Input 1 Source information used in support of the development of the data set. The hydrological streamline network was created using the State of Iowa’s Statewide LiDAR product as the main determination for flow as this surface was used when carrying out Iowa’s Statewide Flood Plain Mapping Project. In cases where LiDAR was insufficient for capture, aerial photography from various years for the State of Iowa was referenced. In order to create the 24 acre linework, two classifications of streams were distinguished: Small Stream Centerlines (SCC) and Wide Stream Centerlines (WSC). Depending on this distinction, collection was performed in different ways detailed below. Unknown Next was to determine when WSC began. WSC were collected by NRCS Eight-Digit Hydrologic Unit boundaries (HUC8) and are defined for this project as consistently shown as 7m wide or greater on the LiDAR (does not go between 7m and narrower). When a watercourse became 7m or wider it was treated differently and small stream digitization was not collected for these reaches. WSC were captured using an entirely different process. Initially capture was done by hand. A methodology was developed where slopes (from LiDAR) were used to determine areas where the percent slope was 20 or greater, these areas were extracted. ESRIs Raster to line was performed on the extracted areas to get rough top of bank (TOB) and edge of water (EOW) lines. These lines were then hand edited to detail the TOB and EOW for a stream for usage in floodplain modeling data capture. The EOW lines were also used to generate Wide Stream centerlines by running ESRIs collapse dual lines to centerline tool. The Centerlines were smoothed and edited to make it more visually aesthetic. Next, the WSC and SCC were combined to create a HUC8 wide stream network. After determining the SSC start points and stop points, collection could begin. Work was performed to collect stream networks by NRCS Twelve-Digit Hydrologic Unit boundaries (HUC 12) area designations in order to more easily process and collect data. Initially streams were hand digitized, while we worked on developing an automated process to get linework from the LiDAR DEMs, as manual digitization was tedious. Ultimately, a code (Gelder Code) was used to get initial linework for creating a HUC12 wide stream network. Water surfaces can be very TIN-y, and this method looked for pits and connected low points when obstacles in the water surface occurred. Run against the LiDAR, this code used NHD linework to determine initial flow networks by filling in pits and punching in holes where needed on the DEM to make flow happen. The output from this was then smoothed to remove some of the roughness of the resulting linework. Editing was also performed when the code output was incorrect and strayed from the streambed in order to assure the linework was accurate. There were cases where the conditions were met for a defined stream (24 acre FAC, scar on DEM) that were not captured by the code as it was dependent on the NHD linework which might not have features for the area. In these cases, hand digitization was performed. Editing for both WSC and SCC was performed in the same way after initial collection of each. Linework was checked to make sure the lines were drawn in a downstream direction and linework around confluences were logical in flow (lines didn’t meet perpendicular or going upstream) as this interfered with ArcHydro when processing the final product later for flood plain mapping needs. As other checking was being completed, the linework was also split at various key locations to determine the character of the streamline. Classifications were given to the streamlines as they were split. These classifications were developed in line with the NHDs FTYPE field and were: 1. Stream or River – regular stream or river segment. 2. Culvert or under bridge - road culvert or bridge (manmade structure) on DEM. 3. Artificial Path - ponds or reservoirs, also connects SSC to WSC. (see below) 4. Connector - connection from artificial path to stream, use for earth dam. 5. Municipality Supplied Pipeline Infrastructure - municipality supplied info. (see below) 6. Drainage Extension - drawn to correct flow. (see below) 7. DFIRM Extension – when inundation on effective FIRM but not in the initial linework. (see below) 8. NULL Value – Used to connect stream segments where definition was temporarily lost. (see below) Artificial Path (continued) - In addition to its “normal” usage (routing flow through ponds/reservoirs and connecting SSC to WSC), it could be said that is has a third area of usage (though it’s basically just a subtle variation of usage for waterbodies)used in wetland areas where there is no significant channel definition or an obvious “waterbody” (with visible standing water), however, there appears to be some presence of wetland vegetation, so flow through the area is attributed as artificial path (it’s just a little bit drier-type of artificial path). The basic standard followed for differences in these stream segments attribution were: 1.Really wet, standing water = artificial path. 2.Somewhatf wet, with unique signs like subtle depressions, moisture-loving vegetation = artificial path. 3.Not wet at all (or maybe just a tiny bit damp) and not much of any definition in DEM = NULL value. Municipality Supplied Pipeline Infrastructure (continued) - A clear flow path on LiDAR was often lacking in larger, older metropolitan areas in the state as well due to storm sewer projects. In the case of larger older municipalities, an effort was made to obtain any data the municipality might have showing the course of storm sewers. While not used for flood plain mapping, this information was used to connect the network when it was interrupted by development to ensure flow accumulations and the flow path followed were as accurate as possible. In some cases the storm sewer network was evident through photography so the city was not contacted. Areas of new development could be captured by referencing aerial photography from predevelopment years. Cities supplying data for this effort were: Burlington, Cedar Rapids, Coralville, Davenport, Des Moines, Dubuque, Iowa City, Johnston, Keokuk, Muscatine, Sioux City, Waterloo. As this was a project to supply streamline data for flood plain mapping, consideration was taken in capturing areas where effective flood determinations existed regardless of whether or not the area met the criteria of 1sq mile flow accumulation (FEMA spec) or a flow path shown on the LiDAR-derived DEM. Drainage Extension (continued) - Drawn in to correct flow. Always added to upstream end of stream segments. Directs flow that is significantly misrouted due to large road embankment (or other obstruction), where there was not already a proper stream/culvert line drawn through culvert in road embankment (criteria for digitizing a proper stream was not fulfilled). DFIRM Extensions (continued) - were incorporated into the linework to capture these instances in order to ensure consideration of existing effective Special Flood Hazard Areas (SFHA). These may not represent a stream, in these cases they most likely were areas that experienced a flooding event in the past and were requested to be included on a Flood Insurance Rate Map (FIRM) for risk awareness by community officials. NULL Value (continued) - Disappearing streams, or the lack of a clear flow path in the LiDAR surface, caused problems in creating a stream network as there was nothing to guide streamline collection. In order to connect the network and ensure flow a segment with NULL value was added. As best as possible, these approximated where overland flow occurred using various years of aerial photography to show where water went during high and low water events. After editing, splitting and attributing SSC and WSC the data was thoroughly reviewed for QAQC in order to assure the accuracy of the product. The individual HUC12 networks and WSCs then needed to be joined together in order to create a HUC8-wide stream network. WSC were first split into individual HUC8 designation areas. Then joining began by connecting all HUC12s that did not have WSC to consider. Where WSC existed in a HUC12 or throughout a HUC8, connections were made by adding a segment to the terminus of a HUC12 or any stream entering a Wide Stream area; this was attributed as an artificial path as per NHD standards. Connections were made with the same criteria used above for confluences assuring the lines were drawn in a downstream direction and linework around confluences were logical in flow (lines didn’t meet perpendicular or going upstream). Names were attributed to the streamline network using Modeled Stream Centerlines from the modeling effort for Statewide Floodplains. These models required naming for logical storage and directory structure for each HUC8 and were typically only for segments of streams draining more than 1sqmi. Names were also used for development of Flood Insurance Rate Map (FIRM) datasets. Only streams with a proper name (not reach codes or unnamed streams) had their attribution transferred to the 24acre linework. A hierarchy for the datasets referenced was followed to determine a stream name. In order of weight, these were: Effective FIRM, NHD Name, USGS TopoBureau of Geographic Names. The effective FIRMs had priority due to this project being related to floodplain mapping, names should match between versions of FIRMs for a county. In most cases sources agreed; however, there were times when the names disagreed or were incorrect in one source or another. When sources disagreed, the name that was shared by most sources was used. The named (modeled stream centerlines) data was spatially joined to the 24 acre streamline network by HUC8. Segments that did not spatially join were added and attributed to make sure of connectivity. Also, since the named streams were only typically to the extent of 1sq mile of drainage, the NAME attribute needed to be added to the upstream segments of the network where named streams existed. The Mississippi and Missouri river segments were not modeled; therefore, there was no effort in the modeling preparation process to collect centerlines. Centerlines for these were added to the overall dataset by heads up digitizing using the NHD as a guide to create connectivity. Attribution is identical to the STREAM_TYPE values for these rivers to offer consistency. Vector Simple FALSE 0 TRUE TRUE North_American_Vertical_Datum_1988 1.0 Meter Explicit elevation coordinate included with horizontal coordinates Attribute Table Table containing attribute information associated with the data set. Producer defined Feature Class 0 OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. Name Name of Stream FEMA, USGS Name of the Stream or River. Name String 150 0 0 Stream_Order Stream_Order SmallInteger 2 0 0 Stream_Type Type of Stream Segment FCode list for NHD Flowline, USGS; producer defined. 1 Stream or River – regular stream or river segment. USGS 2 Culvert or under bridge - road culvert or bridge (manmade structure) on DEM. USGS 3 Artificial Path - ponds or reservoirs, also connects SSC to WSC. USGS 4 Connector - connection from artificial path to stream, use for earth dam. Producer defined 5 Municipality Supplied Pipeline Infrastructure - municipality supplied info. Producer defined 6 Drainage Extension - drawn to correct flow. Producer defined 7 DFIRM Extension – when inundation on effective FIRM but not in the initial linework. Producer defined 8 NULL Value – Used to connect stream segments where definition was temporarily lost. Producer defined Stream_Type String 5 0 0 Label Label String 75 0 0 Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. As other checking was being completed, the linework was also split at various key locations to determine the character of the streamline. Classifications were given to the streamlines as they were split. These classifications were developed in line with the NHDs FTYPE field and were: 1. Stream or River – regular stream or river segment. 2. Culvert or under bridge - road culvert or bridge (manmade structure) on DEM. 3. Artificial Path - ponds or reservoirs, also connects SSC to WSC. (see below) 4. Connector - connection from artificial path to stream, use for earth dam. 5. Municipality Supplied Pipeline Infrastructure - municipality supplied info. (see below) 6. Drainage Extension - drawn to correct flow. (see below) 7. DFIRM Extension – when inundation on effective FIRM but not in the initial linework. (see below) 8. NULL Value – Used to connect stream segments where definition was temporarily lost. (see below) Artificial Path (continued) - In addition to its “normal” usage (routing flow through ponds/reservoirs and connecting SSC to WSC), it could be said that is has a third area of usage (though it’s basically just a subtle variation of usage for waterbodies)used in wetland areas where there is no significant channel definition or an obvious “waterbody” (with visible standing water), however, there appears to be some presence of wetland vegetation, so flow through the area is attributed as artificial path (it’s just a little bit drier-type of artificial path). The basic standard followed for differences in these stream segments attribution were: 1.Really wet, standing water = artificial path. 2.Somewhatf wet, with unique signs like subtle depressions, moisture-loving vegetation = artificial path. 3.Not wet at all (or maybe just a tiny bit damp) and not much of any definition in DEM = NULL value. Municipality Supplied Pipeline Infrastructure (continued) - A clear flow path on LiDAR was often lacking in larger, older metropolitan areas in the state as well due to storm sewer projects. In the case of larger older municipalities, an effort was made to obtain any data the municipality might have showing the course of storm sewers. While not used for flood plain mapping, this information was used to connect the network when it was interrupted by development to ensure flow accumulations and the flow path followed were as accurate as possible. In some cases the storm sewer network was evident through photography so the city was not contacted. Areas of new development could be captured by referencing aerial photography from predevelopment years. Cities supplying data for this effort were: Burlington, Cedar Rapids, Coralville, Davenport, Des Moines, Dubuque, Iowa City, Johnston, Keokuk, Muscatine, Sioux City, Waterloo. As this was a project to supply streamline data for flood plain mapping, consideration was taken in capturing areas where effective flood determinations existed regardless of whether or not the area met the criteria of 1sq mile flow accumulation (FEMA spec) or a flow path shown on the LiDAR-derived DEM. Drainage Extension (continued) - Drawn in to correct flow. Always added to upstream end of stream segments. Directs flow that is significantly misrouted due to large road embankment (or other obstruction), where there was not already a proper stream/culvert line drawn through culvert in road embankment (criteria for digitizing a proper stream was not fulfilled). DFIRM Extensions (continued) - were incorporated into the linework to capture these instances in order to ensure consideration of existing effective Special Flood Hazard Areas (SFHA). These may not represent a stream, in these cases they most likely were areas that experienced a flooding event in the past and were requested to be included on a Flood Insurance Rate Map (FIRM) for risk awareness by community officials. NULL Value (continued) - Disappearing streams, or the lack of a clear flow path in the LiDAR surface, caused problems in creating a stream network as there was nothing to guide streamline collection. In order to connect the network and ensure flow a segment with NULL value was added. As best as possible, these approximated where overland flow occurred using various years of aerial photography to show where water went during high and low water events. The entity and attribute information was generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information. Iowa Department of Natural Resources 319-335-1353 casey.kohrt@dnr.iowa.gov Downloadable Data This digital, geographically referenced data set was developed by the Iowa Department of Natural Resources to carry out agency responsibilities related to management, protection, and development of Iowa's natural resources. It resides in the Natural Resources Geographic Information System library. Although efforts have been made to make it useful to the Department, the Department assumes no responsibility for errors in the information. Similarly the Department assumes no responsibility for the consequences of inappropriate uses or interpretations of the data made by anyone to whom this data has been made available. The Department bears no responsibility to inform users of any changes made to this data. Anyone using this data is advised that precision implied by the coverage may far exceed actual precision. Comments on this data are invited and the Department would appreciate that documented errors be brought to staff attention. The development of the coverages in the NRGIS Library represents a major investment of staff time and effort. As a professional responsibility, we expect that the Iowa DNR will receive proper credit when you utilize these data, and that the original documentation should be included if this data is redistributed. Vector Digital Data Set (Polyline) zip withheld click on link provided None Click on ftp link provided. Immediate 20160121 20160104 Iowa DNR Mailing and Physical

309B Trowbridge Hall

Iowa City IA IA 319-335-1353 NRGIS Librarian casey.kohrt@dnr.iowa.gov FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time There are no access constraints. There are no use constraints. Version 6.2 (Build 9200) ; Esri ArcGIS 10.9.1.28388 Stream_Centerlines 0.000000 0.000000 1 -91.842271 -91.354781 41.867425 41.421873 Stream_Centerlines 002 2094973.805651 2224758.268837 525195.449210 684750.249007 1 Projected GCS_NAD_1983_2011 Linear Unit: Foot_US (0.304801) NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS[&quot;NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US&quot;,GEOGCS[&quot;GCS_NAD_1983_2011&quot;,DATUM[&quot;D_NAD_1983_2011&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Lambert_Conformal_Conic&quot;],PARAMETER[&quot;False_Easting&quot;,1640416.666666667],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-93.5],PARAMETER[&quot;Standard_Parallel_1&quot;,40.61666666666667],PARAMETER[&quot;Standard_Parallel_2&quot;,41.78333333333333],PARAMETER[&quot;Latitude_Of_Origin&quot;,40.0],UNIT[&quot;Foot_US&quot;,0.3048006096012192],AUTHORITY[&quot;EPSG&quot;,6465]]</WKT><XOrigin>-119240500</XOrigin><YOrigin>-96507600</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>2</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>103046</WKID><LatestWKID>6465</LatestWKID></ProjectedCoordinateSystem> 20260504 06485600 20260504 06485600 20220105 08173900 1.0 FGDC CSDGM Metadata FALSE File Geodatabase Feature Class dataset EPSG 8.2.10(10.3.1) 0 20260504