This layer is a component of 2007_NAIP_COVERAGE_3.mxd.

This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

This dataset contains geographic information concerning cities and towns in the United States, Puerto Rico, and the U.S. Virgin Islands. A city or town is a place with a recorded population, usually with at least one central area that provides commercial activities. Cities are generally larger than towns; no distinction is made between cities and towns in this map layer.

This map layer includes cities and towns in Oregon. These cities were clipped from a larger dataset of cities collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December 2003 map layer.

This data set includes cities in the United States, Puerto Rico and the U.S. Virgin Islands. These cities were collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December, 2003, data set.

This layer is sourced from maps.bts.dot.gov.

The United States is a country located in North America. It is made up of 50 states and the capital district of Washington. The US federal republic has its capital in Washington D.C., which means this dataset can be used to study demographics, geography, and population density for different cities across the United States. This information can help researchers, policymakers and businesses understand how people live and work within different geographical areas in the USA

This dataset comes from simplemaps.com, check out the dataset at https://simplemaps.com/data/us-cities

Thumbnail from https://www.vecteezy.com/vector-art/3798082-red-square-map-of-united-states-of-america-with-long-shadow

This layer presents the locations of major cities within the United States with populations of approximately 10,000 or more, state capitals, and the national capital. Major Cities are locations containing population totals from the 2020 Census. The points represent U.S. Census Places polygons sourced from U.S. Census Bureau 2020 TIGER FGDB (National Sub-State). Attribute fields include 2020 total population from the U.S. Census Public Law 94 data that symbolize the city points using these six classifications: Class Population Range 5 2,500 – 9,999 6 10,000 – 49,999 7 50,000 – 99,999 8 100,000 – 249,999 9 250,000 – 499,999 10 500,000 and over This ready-to-use layer can be used in ArcGIS Pro and in ArcGIS Online and its configurable apps, dashboards, StoryMaps, custom apps, and mobile apps. The data can also be exported for offline workflows. Cite the 'U.S. Census Bureau' when using this data.

This layer is a component of Transborder.

The Digital City Map (DCM) data represents street lines and other features shown on the City Map, which is the official street map of the City of New York. The City Map consists of 5 different sets of maps, one for each borough, totaling over 8000 individual paper maps. The DCM datasets were created in an ongoing effort to digitize official street records and bring them together with other street information to make them easily accessible to the public. The Digital City Map (DCM) is comprised of seven datasets; Digital City Map, Street Center Line, City Map Alterations, Arterial Highways and Major Streets, Street Name Changes (areas), Street Name Changes (lines), and Street Name Changes (points). All of the Digital City Map (DCM) datasets are featured on the Streets App All previously released versions of this data are available at BYTES of the BIG APPLE- Archive

Many of the U.S.’s most populated areas are within miles of the coast. As the sea level rises in many areas, these cities are being exposed to more and more nuisance floods - not just from extreme events like Hurricane Sandy, but also when routine rain storms occur. This map plots data from NOAA showing the results of an analysis of tide gauge and satellite data from around the country. City locations colored in blue-green are experiencing positive sea level rise, whereas areas colored in light brown are experiencing negative sea level rise. This feature service includes pop-ups that indicate the city, the rate of sea level rise (feet per century) and the statistical 95% confidence level. The latter gives an indication of how much more or less rise can be expected from the average. Original data from NOAA: https://tidesandcurrents.noaa.gov/sltrends/

The 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. The generalized boundaries of the consolidated cities in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

This point shapefile includes Global Map data showing cities and towns in the United States, Puerto Rico, and the U.S. Virgin Islands. The data are a modified version of the National Atlas of the United States 1:1,000,000-scale cities and towns of the United States; those source data were derived from the Geographic Names Information System (GNIS) and the U.S. Census Bureau National Places Gazetteer files. Global Map refers to these locations as Built-up Area (point) and defines them as areas containing a concentration of buildings and other structures (smaller than Built-up Area (face)). National Atlas cities or towns are defined as places with a recorded population, usually with at least one central area that provides commercial activities. Cities are generally larger than towns; no distinction is made between cities and towns in this map layer. No attempt has been made to reconcile the Global Map and National Atlas feature definitions. This layer is part of the 1997-2014 edition of the National Atlas of the United States.

Dataset of Iowa's counties, including boundaries, county seats, major cities, and downloadable map resources. This lightweight version includes a representative sample of five Iowa counties.

Publication Date: May 2025.

Mature Support Notice: This item is in mature support as of June 2021. A replacement item has not been identified at this time.This map presents land cover and detailed topographic maps for the United States. It uses the USA Topographic Map service. The map includes the National Park Service (NPS) Natural Earth physical map at 1.24km per pixel for the world at small scales, i-cubed eTOPO 1:250,000-scale maps for the contiguous United States at medium scales, and National Geographic TOPO! 1:100,000 and 1:24,000-scale maps (1:250,000 and 1:63,000 in Alaska) for the United States at large scales. The TOPO! maps are seamless, scanned images of United States Geological Survey (USGS) paper topographic maps.The maps provide a very useful basemap for a variety of applications, particularly in rural areas where the topographic maps provide unique detail and features from other basemaps.To add this map service into a desktop application directly, go to the entry for the USA Topo Maps map service. Tip: Here are some famous locations as they appear in this web map, accessed by including their location in the URL that launches the map:Grand Canyon, ArizonaGolden Gate, CaliforniaThe Statue of Liberty, New YorkWashington DCCanyon De Chelly, ArizonaYellowstone National Park, WyomingArea 51, Nevada

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

Dataset

This dataset was created by viswachaitanyasai

Released under MIT

Contents

USGS Structures from The National Map (TNM) consists of data to include the name, function, location, and other core information and characteristics of selected manmade facilities across all US states and territories. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations. Structures currently included are: School, School:Elementary, School:Middle, School:High, College/University, Technical/Trade School, Ambulance Service, Fire Station/EMS Station, Law Enforcement, Prison/Correctional Facility, Post Office, Hospital/Medical Center, Cabin, Campground, Cemetery, Historic Site/Point of Interest, Picnic Area, Trailhead, Vistor/Information Center, US Capitol, State Capitol, US Supreme Court, State Supreme Court, Court House, Headquarters, Ranger Station, White House, and City/Town Hall. Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. Included is a feature class of preliminary building polygons provided by FEMA, USA Structures. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain structures data in either Esri File Geodatabase or Shapefile formats. For additional information on the structures data model, go to https://www.usgs.gov/ngp-standards-and-specifications/national-map-structures-content.

The Digital Geologic-GIS Map of City of Rocks National Reserve and Vicinity, Idaho is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (ciro_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (ciro_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (ciro_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (ciro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (ciro_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (ciro_geology_metadata_faq.pdf). Please read the ciro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (ciro_geology_metadata.txt or ciro_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Dataset of Kansas counties, including county seats, cities, establishment dates, and downloadable map resources.