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

Spatial coverage index compiled by East View Geospatial of set "Gitashenasi Tourist Maps (City Maps)". Source data from GS (publisher). Type: Thematic - Tourist. Scale: Varies. Region: Middle East.

Spatial coverage index compiled by East View Geospatial of set "Cameroon City Maps". Source data from INC (publisher). Type: Thematic - Tourist. Scale: Varies. Region: Africa.

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

Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.

This map provides the base layers to create your own maps. Layers included are the City of Long Beach Boundary, Major Freeways, Major Streets, and Waterways.

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.

Spatial coverage index compiled by East View Geospatial of set "Israel Topographic City Maps (1:3,000 - 1:5,000 scale)". Source data from SI (publisher). Type: Topographic - City Plan. Scale: Varies. Region: Middle East.

Collection of static general Bloomington and city street maps of various sizes.

The Official City Map poster is a general reference map for the City of Kerrville. The main purpose of the map is to show where the current city limits and extraterritorial jurisdiction area are located at. The map also includes reference information such as streets, rivers, lakes, and points of interest. The map is designed to be printed as a poster at ANSI E page size.This map is updated every time there is an annexation or de-annexation.

It is estimated that more than 8 billion people live on Earth and the population is likely to hit more than 9 billion by 2050. Approximately 55 percent of Earth’s human population currently live in areas classified as urban. That number is expected to grow by 2050 to 68 percent, according to the United Nations (UN).The largest cities in the world include Tōkyō, Japan; New Delhi, India; Shanghai, China; México City, Mexico; and São Paulo, Brazil. Each of these cities classifies as a megacity, a city with more than 10 million people. The UN estimates the world will have 43 megacities by 2030.Most cities' populations are growing as people move in for greater economic, educational, and healthcare opportunities. But not all cities are expanding. Those cities whose populations are declining may be experiencing declining fertility rates (the number of births is lower than the number of deaths), shrinking economies, emigration, or have experienced a natural disaster that resulted in fatalities or forced people to leave the region.This Global Cities map layer contains data published in 2018 by the Population Division of the United Nations Department of Economic and Social Affairs (UN DESA). It shows urban agglomerations. The UN DESA defines an urban agglomeration as a continuous area where population is classified at urban levels (by the country in which the city resides) regardless of what local government systems manage the area. Since not all places record data the same way, some populations may be calculated using the city population as defined by its boundary and the metropolitan area. If a reliable estimate for the urban agglomeration was unable to be determined, the population of the city or metropolitan area is used.Data Citation: United Nations Department of Economic and Social Affairs. World Urbanization Prospects: The 2018 Revision. Statistical Papers - United Nations (ser. A), Population and Vital Statistics Report, 2019, https://doi.org/10.18356/b9e995fe-en.

This web map depicts GIS data for known Stormwater Infrastructure in the City of SeaTac, Washington. The information is based on the best available knowledge collected from construction as-builts and field inspections, with a focus on mapping features in the public right-of-way. The stormwater infrastructure contains the following datasets: discharge points, catch basins and manholes, pipes and ditches, misc structures, water quality facilities points and polygons, and access risers. The data is being continually updated as newer information becomes available.Incorporated in February 1990, the City of SeaTac is located in the Pacific Northwest, approximately midway between the cities of Seattle and Tacoma in the State of Washington. SeaTac is a vibrant community, economically strong, environmentally sensitive, and people-oriented. The City boundaries surround the Seattle-Tacoma International Airport, (approximately 3 square miles in area) which is owned and operated by the Port of Seattle. For additional information regarding the City of SeaTac, its people, or services, please visit https://www.seatacwa.gov. For additional information regarding City GIS data or maps, please visit https://www.seatacwa.gov/our-city/maps-and-gis.

This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/

VDOT collaborated with the Virginia Tourism Corporation to develop the state map, which features Virginia's beaches and encourages travelers to head to the coast and visit the many attractions across the Commonwealth. This link provides access to detailed city maps.

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 Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.

City of Sioux Falls open data Maps and Apps home page.

This dataset includes a total of 635 annotated image patches from historical city maps. It is designed for the semantic segmentation of the maps into 5 semantic classes (building blocks, non-built, water, road network, background frame). 330 patches are taken from maps of the city of Paris, while the 305 others are taken from a balanced corpus of city maps from 90 countries all around the world.

Please read the detailed informations about data collection methodology, associated metadata and annotation ontology in README.md hereunder :

The dataset and the validation are fully described in a Nature Scientific Data Descriptor https://www.nature.com/articles/s41597-019-0265-5

If you want to use this dataset in an interactive environment, then use this link https://mybinder.org/v2/gh/GeographerAtLarge/TravelTime/HEAD

The following text is a summary of the information in the above Data Descriptor.

The dataset is a suite of global travel-time accessibility indicators for the year 2015, at approximately one-kilometre spatial resolution for the entire globe. The indicators show an estimated (and validated), land-based travel time to the nearest city and nearest port for a range of city and port sizes.

The datasets are in GeoTIFF format and are suitable for use in Geographic Information Systems and statistical packages for mapping access to cities and ports and for spatial and statistical analysis of the inequalities in access by different segments of the population.

These maps represent a unique global representation of physical access to essential services offered by cities and ports.

The datasets travel_time_to_cities_x.tif (where x has values from 1 to 12) The value of each pixel is the estimated travel time in minutes to the nearest urban area in 2015. There are 12 data layers based on different sets of urban areas, defined by their population in year 2015 (see PDF report).

travel_time_to_ports_x (x ranges from 1 to 5)

The value of each pixel is the estimated travel time to the nearest port in 2015. There are 5 data layers based on different port sizes.

Format Raster Dataset, GeoTIFF, LZW compressed Unit Minutes

Data type Byte (16 bit Unsigned Integer)

No data value 65535

Flags None

Spatial resolution 30 arc seconds

Spatial extent

Upper left -180, 85

Lower left -180, -60 Upper right 180, 85 Lower right 180, -60 Spatial Reference System (SRS) EPSG:4326 - WGS84 - Geographic Coordinate System (lat/long)

Temporal resolution 2015

Temporal extent Updates may follow for future years, but these are dependent on the availability of updated inputs on travel times and city locations and populations.

Methodology Travel time to the nearest city or port was estimated using an accumulated cost function (accCost) in the gdistance R package (van Etten, 2018). This function requires two input datasets: (i) a set of locations to estimate travel time to and (ii) a transition matrix that represents the cost or time to travel across a surface.

The set of locations were based on populated urban areas in the 2016 version of the Joint Research Centre’s Global Human Settlement Layers (GHSL) datasets (Pesaresi and Freire, 2016) that represent low density (LDC) urban clusters and high density (HDC) urban areas (https://ghsl.jrc.ec.europa.eu/datasets.php). These urban areas were represented by points, spaced at 1km distance around the perimeter of each urban area.

Marine ports were extracted from the 26th edition of the World Port Index (NGA, 2017) which contains the location and physical characteristics of approximately 3,700 major ports and terminals. Ports are represented as single points

The transition matrix was based on the friction surface (https://map.ox.ac.uk/research-project/accessibility_to_cities) from the 2015 global accessibility map (Weiss et al, 2018).

Code The R code used to generate the 12 travel time maps is included in the zip file that can be downloaded with these data layers. The processing zones are also available.

Validation The underlying friction surface was validated by comparing travel times between 47,893 pairs of locations against journey times from a Google API. Our estimated journey times were generally shorter than those from the Google API. Across the tiles, the median journey time from our estimates was 88 minutes within an interquartile range of 48 to 143 minutes while the median journey time estimated by the Google API was 106 minutes within an interquartile range of 61 to 167 minutes. Across all tiles, the differences were skewed to the left and our travel time estimates were shorter than those reported by the Google API in 72% of the tiles. The median difference was −13.7 minutes within an interquartile range of −35.5 to 2.0 minutes while the absolute difference was 30 minutes or less for 60% of the tiles and 60 minutes or less for 80% of the tiles. The median percentage difference was −16.9% within an interquartile range of −30.6% to 2.7% while the absolute percentage difference was 20% or less in 43% of the tiles and 40% or less in 80% of the tiles.

This process and results are included in the validation zip file.

Usage Notes The accessibility layers can be visualised and analysed in many Geographic Information Systems or remote sensing software such as QGIS, GRASS, ENVI, ERDAS or ArcMap, and also by statistical and modelling packages such as R or MATLAB. They can also be used in cloud-based tools for geospatial analysis such as Google Earth Engine.

The nine layers represent travel times to human settlements of different population ranges. Two or more layers can be combined into one layer by recording the minimum pixel value across the layers. For example, a map of travel time to the nearest settlement of 5,000 to 50,000 people could be generated by taking the minimum of the three layers that represent the travel time to settlements with populations between 5,000 and 10,000, 10,000 and 20,000 and, 20,000 and 50,000 people.

The accessibility layers also permit user-defined hierarchies that go beyond computing the minimum pixel value across layers. A user-defined complete hierarchy can be generated when the union of all categories adds up to the global population, and the intersection of any two categories is empty. Everything else is up to the user in terms of logical consistency with the problem at hand.

The accessibility layers are relative measures of the ease of access from a given location to the nearest target. While the validation demonstrates that they do correspond to typical journey times, they cannot be taken to represent actual travel times. Errors in the friction surface will be accumulated as part of the accumulative cost function and it is likely that locations that are further away from targets will have greater a divergence from a plausible travel time than those that are closer to the targets. Care should be taken when referring to travel time to the larger cities when the locations of interest are extremely remote, although they will still be plausible representations of relative accessibility. Furthermore, a key assumption of the model is that all journeys will use the fastest mode of transport and take the shortest path.

City Boundary

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 Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the 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).