{"action":"create","ckan_id":null,"date_created":"Mon, 26 Jan 2026 20:22:15 GMT","date_finished":null,"harvest_job_id":"a13d164e-f418-4cf7-8735-a8eaa1bbccaa","harvest_source_id":"4c62556f-0fa3-402d-90f6-6a46cd80a117","id":"abf1a77e-b6e1-4ca5-8ee1-c69299a20490","identifier":"https://hazards.fema.gov/filedownload/metadata/R10/631012-AcquireBaseMap.xml","parent_identifier":null,"source_hash":"f1a497a0d1b8ce66315afeb44475212eca1f440d5a689454fe0feb6ca26caee4","source_raw":"\r\n\r\n \r\n \r\n \r\n AK Department of Community and Econmic Development\r\n Alaska Department of Natural Resources-Land Records Information Section\r\n United States Geological Survey\r\n U.S. Dept. of Interior, Bureau of Land Management, Division of Cadastral Survey and Geomatics, Branch of Spatial Records\r\n NOAA, National Geodetic Survey\r\n U.S. Army Corps of Engineers\r\n 200712\r\n BASEMAP, CITY OF NOME, ALASKA, USA\r\n FGDC-Framework-Basemap\r\n \r\n Washington, DC\r\n Federal Emergency Management Agency\r\n \r\n http://hazards.fema.gov\r\n \r\n \r\n Federal Emergency Management Agency\r\n Unknown\r\n FEMA CASE 08-10-0130S\r\n \r\n \r\n \r\n \r\n \r\n This FEMA Framework Basemap dataset comprises the seven FGDC themes of geospatial data that are used by most GIS applications: cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines), and orthoimagery. The vector data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)\r\n Also included is a digital orthographic imagery dataset. Digital orthographic imagery datasets contain georeferenced images of the Earth's surface, collected by a sensor in which object displacement has been removed for sensor distortions and orientation, and terrain relief. Digital orthoimages have the geometric characteristics of a map, and image qualities of a photograph.\r\n The Basemap datasets reflect the reference features (i.e., roads, streets, hydrographic features, political jurisdiction boundaries) needed by users to locate properties on FIRMs. (Source: Guidelines and Specifications Vol 1, p. 68)\r\n \r\n \r\n \r\n \r\n 20071201\r\n \r\n \r\n MIP Submission Date\r\n \r\n \r\n In work\r\n Unknown\r\n \r\n \r\n \r\n -165.516792\r\n -165.322363\r\n 64.56066\r\n 64.463772\r\n \r\n \r\n \r\n \r\n ISO 19115 Topic Category\r\n Transportation\r\n Hydrography\r\n Corporate boundaries\r\n Permanent benchmarks\r\n PLSS\r\n Quad boundaries\r\n imageryBaseMapsEarthCover\r\n \r\n \r\n FEMA NFIP Topic Category\r\n Basemap\r\n Orthoimage\r\n DOQ\r\n DOQQ\r\n FGDC Framework\r\n Digital Orthophoto Quad\r\n Orthophoto\r\n \r\n \r\n None\r\n REGION 10\r\n STATE AK\r\n COUNTY NOME DIVISION\r\n COUNTY-FIPS 180\r\n FEMA-CID 020069\r\n COMMUNITY CITY OF NOME\r\n \r\n \r\n None\r\n Acknowledgement of FEMA would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database.\r\n Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722\r\n \r\n \r\n Polygons intersecting the neatline are closed along the border. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. Line segments are a set of sequentially numbered coordinate pairs. No duplicate features exist nor duplicate points in a data string. Intersecting lines are separated into individual line segments at the point of intersection. Point data are represented by two sets of coordinate pairs, each with the same coordinate values. Tests for logical consistency are performed by DFIRM tools topology verification software.\r\n Orthoimagery is named according to (7.5 x 15) and\r\n (7.5 x 11.25) minute file naming conventions provided by USGS.\r\n The Basemap datasets represent all the features utilized during the study mapping process to spatially position the DFIRM information. Orthoimagery covers all affected study areas. The best available vector datasets were assembled for the remaining areas.\r\n \r\n \r\n The NSSDA is used to report the horizontal accuracy of the base map data used by FEMA to produce a FIRM. The NSSDA uses radial accuracy (Accuracy) to report the radius of a circle of uncertainty, such that the true or theoretical location of a point falls within that circle 95 percent of the time. (Guidelines and Specifications Vol 1, p. 70)\r\n See source citations for accuracy specifications of individual datasets.\r\n \r\n 11.5824\r\n The minimum horizontal positional accuracy for new FIRM base map data is that of the default base map - the USGS DOQs, which have an NSSDA radial accuracy of 38 feet. Data that meet higher accuracy standards are also acceptable. Accuracy of 38 feet is the same as radial root mean square error (RMSEr) of 22 feet. (Guidelines and Specifications Vol 1, p. 70)\r\n See source citations for accuracy specifications of individual datasets.\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n U.S. Geological Survey\r\n 1989\r\n USGS 7.5-Minute Series Topographic Maps\r\n digital vector data\r\n \r\n Reston, VA\r\n U.S. Geological Survey\r\n \r\n USGS has mapped the county with 1:24,000 scale topographic maps (also referred to as 7.5-minute quadrangles). The entire county was mapped by the late 1980s. From the raster topographic maps, a vector index of the USGS topographic maps with its corresponding tile identification number and name was created.\r\n \r\n \r\n 24000\r\n online\r\n \r\n \r\n \r\n 1989\r\n \r\n \r\n publication date\r\n \r\n BASE1\r\n Spatial and attribute information for the index of USGS 7.5-Minute Series Topographic Map boundaries.\r\n \r\n \r\n \r\n \r\n AK Department of Community and Econmic Development\r\n 2003\r\n Incorporated City Boundaries of Alaska\r\n vector digital data\r\n \r\n Anchorage, AK\r\n AK Department of Community and Econmic Development\r\n \r\n This data contains the boundaries of incorporated cities according to the State of Alaska Department of Community and Economic Development (DECED). The city boundaries were updated from an older version of the data by various means. The primary source of information that was used for the creation of new boundaries was the legal descriptions found within the city certificates. Other means used included rectifying status plats, digitizing features found on USGS Topographic Quadrangle maps, and digital data availible for download from borough web sites.\r\n This data set was created using the Web Extraction Tool (WET) coverage offset, region.b_city as a base data set. With information provided by the State of Alaska Department of Community and Economic Development (DCED) the city boundaries coverage was created with new updates (i.e. dissolved cities, newly incorporated city boundaries, and city boundary changes). The editing and creation of the data set was mainly performed by the legal descriptions found in the city certificate. In the event that the legal description was absent and/or means of locating areas described in the legal description was not available, other actions of editing and creating the boundaries were taken (i.e. rectification and digitizing BLM and DNR Status Plats, digitizing known boundaries and features found on USGS Topographic Quadrangle maps, and simple edits of existing boundaries such as merge, join, delete, etc.).\r\n \r\n \r\n 63360\r\n online\r\n \r\n \r\n \r\n 2003\r\n \r\n \r\n publication date\r\n \r\n BASE2\r\n Spatial and attribute information for political boundaries.\r\n \r\n \r\n \r\n \r\n U.S. Dept. of Interior, Bureau of Land Management, Division of Cadastral Survey and Geomatics, Branch of Spatial Records\r\n 20010207\r\n secgrid\r\n vector digital data\r\n \r\n Washington, DC\r\n U.S. Dept. of Interior, Bureau of Land Management, Division of Cadastral Survey and Geomatics, Branch of Spatial Records\r\n \r\n Township boundaries were generated from geodetic latitude and longitude coordinate pairs as recorded on BLM's official protraction diagrams of the state of Alaska. Section positions are computed from BLM official protraction diagrams based on township positions, subdivision shape codes, and parenthetical distances. The values used for this data were initially obtained from U.S., Department of the Interior, Bureau of Land Management, Alaska State Office, Division of Cadastral Survey and Geomatics's (BLM) AEH (acronym unknown) coordinate files.\r\n \r\n \r\n 63360\r\n online\r\n \r\n \r\n \r\n 20010207\r\n \r\n \r\n publication date\r\n \r\n BASE3\r\n Spatial and attribute information for PLSS boundaries.\r\n \r\n \r\n \r\n \r\n NOAA, National Geodetic Survey\r\n 2007\r\n Horizontal and Vertical Geodetic Control Data for the United States\r\n vector digital data\r\n \r\n NOAA Campus, Siver Spring, MD\r\n NOAA, National Geodetic Survey\r\n \r\n Geodetic data comprise the results of geodetic surveys to determine among other things, latitude, longitude, height, scale, and orientation control. The NGS final product is the geodetic data sheet. Geodetic data sheets are comprehensive summaries of all the published information for a given geodetic reference point, including: the geographic position and/or height based on the current reference datum, condition of the survey mark when it was last visited, a description of where the point is located and how to reach it, and an explanation of the terms used in the data sheet.\r\n \r\n \r\n 12000\r\n online\r\n \r\n \r\n \r\n 2007\r\n \r\n \r\n retrieval date\r\n \r\n BASE4\r\n Spatial and attribute information for permanent benchmarks.\r\n \r\n \r\n \r\n \r\n Alaska Department of Natural Resources-Land Records Information Section\r\n 20071119\r\n Alaska Roads 1:63,360\r\n vector digital data\r\n \r\n Anchorage, AK\r\n Alaska Department of Natural Resources-Land Records Information Section\r\n \r\n This data depicts road locations in Alaska as digitized primarily from 1:24,000, 1:63,360, and 1:250,000 USGS quadrangles. The source document that represented the newest information and best geographic location was used to capture the data. All infrastructure from the primary source document was digitized and then supplemented with the information from other source documents for additional or updated infrastructure or attributes\r\n Unknown\r\n \r\n \r\n 63360\r\n online\r\n \r\n \r\n \r\n 20071119\r\n \r\n \r\n date of data extraction\r\n \r\n BASE5\r\n Spatial and attribute information for transportation features.\r\n \r\n \r\n \r\n \r\n Alaska Department of Natural Resources - Land Records Information Section\r\n 20071119\r\n Alaska Airstrips 1:63,360\r\n vector digital data\r\n \r\n Anchorage, AK\r\n Alaska Department of Natural Resources - Land Records Information Section\r\n \r\n This data depicts airstrip and runway locations in Alaska as digitized primarily from 1:24,000, 1:63,360, and 1:250,000 USGS quadrangles. The source document that represented the newest information and best geographic location was used to capture the data. All infrastructure from the primary source document was digitized and then supplemented with the information from other source documents for additional or updated infrastructure or attributes.\r\n \r\n \r\n 63360\r\n online\r\n \r\n \r\n \r\n 20071119\r\n \r\n \r\n date of data extraction\r\n \r\n BASE7\r\n Spatial and attribute information transportation features.\r\n \r\n \r\n \r\n \r\n Alaska Department of Natural Resources-Land Records Information Section\r\n 20070129\r\n Alaska Hydrography 1:63360\r\n vector digital data\r\n \r\n Anchorage, AK\r\n Alaska Department of Natural Resources-Land Records Information Section\r\n \r\n DNR, LRIS, Status Graphics Unit (SGU) maintains a hydrography coverage consisting of data that was digitized by SGU staff, primarily from 1:63,360 USGS quadrangles photo-revised by BLM from aerial high altitude photography flown between 1978-1985. In addition, data from other sources was digitized or obtained in digital format if BLM data was not available..\r\n Unknown\r\n \r\n \r\n 63360\r\n online\r\n \r\n \r\n \r\n 20070129\r\n \r\n \r\n date of data extraction\r\n \r\n BASE8\r\n Spatial and attribute information for water features.\r\n \r\n \r\n \r\n \r\n U.S. Army Corps of Engineers\r\n 2006\r\n Plan Drawing of New Harbor Entrance for Nome, AK\r\n vector digital data\r\n \r\n Anchorage, AK\r\n U.S. Army Corps of Engineers\r\n \r\n Plan drawing of new harbor entrance after completion of construction of September 2006.\r\n \r\n \r\n 2400\r\n CD-ROM\r\n \r\n \r\n \r\n 2006\r\n \r\n \r\n publication date\r\n \r\n BASE10\r\n Spatial and attribute information for general structure features.\r\n \r\n \r\n All Flood Map Projects that will result in a digital FIRM require a digital base map that reflects reference features (i.e., roads, streets, hydrographic features, political jurisdiction boundaries) needed by users to locate properties on FIRMs. During the Project Scoping phase, the Project Team identified the base map to be used and assign the Mapping Partner responsible for obtaining the base map for use by FEMA for FIRM production. Early coordination with all communities affected by a Flood Map Project is an important part of the Project Scoping Process described in Section 1.3 of these Guidelines. Therefore, the Section 1.4 1-68 Guidelines and Specifications for Flood Hazard Mapping Partners [April 2003] Mapping Partner responsible for preparing the Preliminary version of the FIRM or another assigned Mapping Partner shall send a letter to each affected community that: Describes the FIRM product; Requests pertinent information (pertinent information that is requested includes base map data; a current corporate limits map; elevation data [either electronic or hardcopy] and any engineering information that needs to be updated or added to the FIRM); Describes the minimum requirements for the submittal of data to be included in the new FIRM product, and Identifies the base map source that will be used if community data are not available or suitable. A sample version of this letter and other correspondence that may be generated during the Map Production phase of the project are presented in the FEMA Document Control Procedures Manual (FEMA, 2000).\r\n 20071201\r\n \r\n \r\n \r\n \r\n Vector\r\n \r\n \r\n \r\n \r\n \r\n State Plane Coordinate System 1983\r\n \r\n 5008\r\n \r\n 0.999900\r\n -166.000000\r\n 54.000000\r\n 1640416.7\r\n 0.000000\r\n \r\n \r\n \r\n \r\n coordinate pair\r\n \r\n 0.000064\r\n 0.000064\r\n \r\n survey feet\r\n \r\n \r\n \r\n North American Datum of 1983\r\n Geodetic Reference System 80\r\n 6378137.0\r\n 298.257222\r\n \r\n \r\n \r\n \r\n \r\n The Basemap submission is made up of several data themes containing both spatial and attribute information. These data together represent the current basemap layers for the subject area as identified by FEMA.\r\n Appendix L of FEMA Guidelines and Specifications for FEMA Flood Hazard Mapping Partners contains a detailed description of the data themes and references 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 address\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@mapmodteam.com\r\n Data requests must include the full name of the community or county and the FIRM panel number(s) or the 7.5- minute series quadrangle sheet area(s) covered by the request.\r\n \r\n \r\n Downloadable Data\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 ARCE\r\n 2.116\r\n \r\n \r\n \r\n \r\n \r\n http://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 20080811\r\n \r\n \r\n \r\n John Doe\r\n Federal Emergency Management Agency\r\n \r\n \r\n mailing address\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@mapmodteam.com\r\n \r\n \r\n FGDC Content Standards for Digital Geospatial Metadata\r\n FGDC-STD-001-1998\r\n local time\r\n \r\n http://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"}