Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the... Visit https://dataone.org/datasets/sha256%3A3e3f055bf6281f979484f847d0ed5eeb96143a369592149328c370fe5776742b for complete metadata about this dataset.

The Residential Schools Locations Dataset in Geodatabase format (IRS_Locations.gbd) contains a feature layer "IRS_Locations" that contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Residential Schools Settlement Agreement are included in this dataset, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The dataset was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this dataset,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School.When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. Access Instructions: there are 47 files in this data package. Please download the entire data package by selecting all the 47 files and click on download. Two files will be downloaded, IRS_Locations.gbd.zip and IRS_LocFields.csv. Uncompress the IRS_Locations.gbd.zip. Use QGIS, ArcGIS Pro, and ArcMap to open the feature layer IRS_Locations that is contained within the IRS_Locations.gbd data package. The feature layer is in WGS 1984 coordinate system. There is also detailed file level metadata included in this feature layer file. The IRS_locations.csv provides the full description of the fields and codes used in this dataset.

The 2023 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2023 Tax Year.
This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.
Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here.

Update Frequency:
This dataset is updated on a yearly basis.

This is a collection of maps, layers, apps and dashboards that show population access to essential retail locations, such as grocery stores. Data sourcesPopulation data is from the 2010 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer.Grocery store locations are from SafeGraph, reflecting what was in the data as of October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters.The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Alternative versions of these layers are available. These pairs use different colors but are otherwise identical in content.Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis.The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels.The SafeGraph grocery store locations were created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 records. In this map, this layer is included as a vector tile layer.MethodologyEvery census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway.A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in.The results for each analysis were captured in the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle).The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step.Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool uses a 200 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect.Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point.Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes

Parcels affected by the adoption of the 2015 International Wildland Urban-Interface Code (WUIC), which was adopted by Austin City Council April9, 2020, and implementation beginning January 1st, 2021. Parcels that are within 1.5 miles of a wildland area greater than 750 acres and parcels within 150 feet of a wildland area greater than 40 acres are wildland_urban_interface_code parcels. Parcels designated as "preserves" have been removed and are not subject to the WUI code.Dataset was created in 2020 by Austin Fire Department Wildfire Division. It was derived from the most recent Travis County Appraisal District (TCAD) Parcels, and queried based upon their planar distance to wildland areas. Wildlands are defined as undeveloped continuous areas,. The wildlands feature class is maintained by the Austin Fire Department and is derived from the City of Austin Planimetric dataset, also known as impervious cover data, and are updated every two years. ArcGIS Pro version 2 software was used to create this dataset. The data is meant to be ingested by a GIS system. Changes to the City of Austin & LTD jurisdiction warrant an update to this dataset. The data is scheduled to be updated every two years.Included in the attributes are parcel condition variables that determine the parcel's "fire hazard severity' class. These include the composite score of three variables: slope score, fuel score, and WUI class (proximity). Slope score was determined by the average degree slope of the area within each parcel and classified as less than 10%, 10% to 25%, or greater then 25%. Fuel score was determined by the average fuel class area within each parcels as defined by the Austin Travis County Community Wildfire Protection Plan (CWPP) and classified as light, medium, or heavy fuels. Proximity class was defined by the proximity of each parcel to wildlands, either as within 1.5 miles of wildlands greater than 750 acres, or within 150 feet of wildlands greater than 40 acres.Description of data fieldsGLOBALID_1 = Used for Global IdentificationOBJECTID = Object IdentificationSLOPE_DEGREE = The average slope of each parcel in degreesFIRE_HAZARD_SEVERITY = The "fire hazard severity" class of each parcelPROXIMITY_CLASS = The proximity class of each parcelSLOPE_CLASS = The slope classification of each parcelFUEL_CLASS = The fuel class of each parcelCREATED_BY = Creators nameCREATED_DATE = Date createdMODIFIED_BY = Modifiers nameMODIFIED_DATE = Date modifiedUNIQUE_ID = Unique Identification number (mirror object id)Shape_Area = Shape areaShape_Length = Shape lengthIteration ID: Parcels_AustinLTD4 2020Contact: Steven Casebeer at Steven.casebeer@austintexas.gov | Austin Fire Department Wildfire Division

In the United States, the federal government manages approximately 28% of the land in the United States. Most federal lands are west of the Mississippi River, where almost half of the land by area is managed by the federal government. Federal lands include 193 million acres managed by the US Forest Service in 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service, and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources. The agencies included in this layer are:Bureau of Land ManagementDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States federal lands managed by six federal agenciesGeographic Extent: 50 United States and the District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Data Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DOD, USFS, USFWS, NPS, PADUS 3.0Publication Date: Various - Esri compiled and published this layer in May 2025. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This layer is a time series of the annual ESA CCI (Climate Change Initiative) land cover maps of the world. ESA has produced land cover maps for the years since 1992. These are available at the European Space Agency Climate Change Initiative website.Time Extent: 1992-2019Cell Size: 300 meterSource Type: ThematicPixel Type: 8 Bit UnsignedData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: GlobalSource: ESA Climate Change InitiativeUpdate Cycle: AnnualWhat can you do with this layer?This layer may be added to ArcGIS Online maps and applications and shown in a time series to watch a "time lapse" view of land cover change since 1992 for any part of the world. The same behavior exists when the layer is added to ArcGIS Pro.In addition to displaying all layers in a series, this layer may be queried so that only one year is displayed in a map. This layer can be used in analysis. For example, the layer may be added to ArcGIS Pro with a query set to display just one year. Then, an area count of land cover types may be produced for a feature dataset using the zonal statistics tool. Statistics may be compared with the statistics from other years to show a trend.To sum up area by land cover using this service, or any other analysis, be sure to use an equal area projection, such as Albers or Equal Earth.Different Classifications Available to MapFive processing templates are included in this layer. The processing templates may be used to display a smaller set of land cover classes.Cartographic Renderer (Default Template)Displays all ESA CCI land cover classes.*Forested lands TemplateThe forested lands template shows only forested lands (classes 50-90).Urban Lands TemplateThe urban lands template shows only urban areas (class 190).Converted Lands TemplateThe converted lands template shows only urban lands and lands converted to agriculture (classes 10-40 and 190).Simplified RendererDisplays the map in ten simple classes which match the ten simplified classes used in 2050 Land Cover projections from Clark University.Any of these variables can be displayed or analyzed by selecting their processing template. In ArcGIS Online, select the Image Display Options on the layer. Then pull down the list of variables from the Renderer options. Click Apply and Close. In ArcGIS Pro, go into the Layer Properties. Select Processing Templates from the left hand menu. From the Processing Template pull down menu, select the variable to display.Using TimeBy default, the map will display as a time series animation, one year per frame. A time slider will appear when you add this layer to your map. To see the most current data, move the time slider until you see the most current year.In addition to displaying the past quarter century of land cover maps as an animation, this time series can also display just one year of data by use of a definition query. For a step by step example using ArcGIS Pro on how to display just one year of this layer, as well as to compare one year to another, see the blog called Calculating Impervious Surface Change.Hierarchical ClassificationLand cover types are defined using the land cover classification (LCCS) developed by the United Nations, FAO. It is designed to be as compatible as possible with other products, namely GLCC2000, GlobCover 2005 and 2009.This is a heirarchical classification system. For example, class 60 means "closed to open" canopy broadleaved deciduous tree cover. But in some places a more specific type of broadleaved deciduous tree cover may be available. In that case, a more specific code 61 or 62 may be used which specifies "open" (61) or "closed" (62) cover.Land Cover ProcessingTo provide consistency over time, these maps are produced from baseline land cover maps, and are revised for changes each year depending on the best available satellite data from each period in time. These revisions were made from AVHRR 1km time series from 1992 to 1999, SPOT-VGT time series between 1999 and 2013, and PROBA-V data for years 2013, 2014 and 2015. When MERIS FR or PROBA-V time series are available, changes detected at 1 km are re-mapped at 300 m. The last step consists in back- and up-dating the 10-year baseline LC map to produce the 24 annual LC maps from 1992 to 2015.Source dataThe datasets behind this layer were extracted from NetCDF files and TIFF files produced by ESA. Years 1992-2015 were acquired from ESA CCI LC version 2.0.7 in TIFF format, and years 2016-2018 were acquired from version 2.1.1 in NetCDF format. These are downloadable from ESA with an account, after agreeing to their terms of use. https://maps.elie.ucl.ac.be/CCI/viewer/download.phpCitationESA. Land Cover CCI Product User Guide Version 2. Tech. Rep. (2017). Available at: maps.elie.ucl.ac.be/CCI/viewer/download/ESACCI-LC-Ph2-PUGv2_2.0.pdfMore technical documentation on the source datasets is available here:https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=doc*Index of all classes in this layer:10 Cropland, rainfed11 Herbaceous cover12 Tree or shrub cover20 Cropland, irrigated or post-flooding30 Mosaic cropland (>50%) / natural vegetation (tree, shrub, herbaceous cover) (<50%)40 Mosaic natural vegetation (tree, shrub, herbaceous cover) (>50%) / cropland (<50%)50 Tree cover, broadleaved, evergreen, closed to open (>15%)60 Tree cover, broadleaved, deciduous, closed to open (>15%)61 Tree cover, broadleaved, deciduous, closed (>40%)62 Tree cover, broadleaved, deciduous, open (15-40%)70 Tree cover, needleleaved, evergreen, closed to open (>15%)71 Tree cover, needleleaved, evergreen, closed (>40%)72 Tree cover, needleleaved, evergreen, open (15-40%)80 Tree cover, needleleaved, deciduous, closed to open (>15%)81 Tree cover, needleleaved, deciduous, closed (>40%)82 Tree cover, needleleaved, deciduous, open (15-40%)90 Tree cover, mixed leaf type (broadleaved and needleleaved)100 Mosaic tree and shrub (>50%) / herbaceous cover (<50%)110 Mosaic herbaceous cover (>50%) / tree and shrub (<50%)120 Shrubland121 Shrubland evergreen122 Shrubland deciduous130 Grassland140 Lichens and mosses150 Sparse vegetation (tree, shrub, herbaceous cover) (<15%)151 Sparse tree (<15%)152 Sparse shrub (<15%)153 Sparse herbaceous cover (<15%)160 Tree cover, flooded, fresh or brakish water170 Tree cover, flooded, saline water180 Shrub or herbaceous cover, flooded, fresh/saline/brakish water190 Urban areas200 Bare areas201 Consolidated bare areas202 Unconsolidated bare areas210 Water bodies

This layer shows median household income by race and by age of householder. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. Median income and income source is based on income in past 12 months of survey. This layer is symbolized to show median household income. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B19013B, B19013C, B19013D, B19013E, B19013F, B19013G, B19013H, B19013I, B19049, B19053Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

The U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) conducted research to identify areas of seafloor elevation stability and instability based on elevation changes between the years of 2016 and 2019 along the Florida Reef Tract (FRT) from Miami to Key West within a 939.4 square-kilometer area. USGS SPCMSC staff used seafloor elevation-change data from Fehr and others (2021) derived from an elevation-change analysis between two elevation datasets acquired in 2016/2017 and 2019 using the methods of Yates and others (2017). Most of the elevation data from the 2016/2017 time period were collected during 2016, so as an abbreviated naming convention, we refer to this time period as 2016. Due to file size limitations, the elevation-change data was divided into five blocks. A seafloor stability threshold was determined for the 2016-2019 FRT elevation-change datasets based on the vertical uncertainty of the 2016 and 2019 digital elevation models (DEMs). Five stability categories (which include, Stable: 0.0 meters (m) to ±0.24 m or 0.0 m to ±0.49 m; Moderately stable: ±0.25 m to ±0.49 m; Moderately unstable: ±0.50 m to ±0.74 m; Mostly unstable: ±0.75 m to ±0.99 m; and Unstable: ±1.00 m to Max/Min elevation change) were created and used to define levels of stability and instability for each elevation-change value (total of 235,153,117 data points at 2-m horizontal resolution) based on the amount of erosion and accretion during the 2016 to 2019 time period. Seafloor-stability point and triangulated irregular network (TIN) surface models were created for each block at five different elevation-change data resolutions (1st order through 5th order) with each resolution becoming increasingly more detailed. The stability models were used to determine the level of seafloor stability at potential areas of interest for coral restoration and 14 habitat types found along the FRT. Stability surface (TIN) models were used for areas defined by specific XY geographic points, while stability point models were used for areas defined by bounding box coordinate locations. This data release includes ArcGIS Pro map packages containing the binned and color-coded stability point and surface (TIN) models, potential coral restoration locations, and habitat files for each block; maps of each stability model; and data tables containing stability and elevation-change data for the potential coral restoration locations and habitat types. Data were collected under Florida Keys National Marine Sanctuary permit FKNMS-2016-068. Coral restoration locations were provided by Mote Marine Laboratory under Special Activity License SAL-18-1724-SCRP.

This dataset contains oil and gas leases cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores.Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data.Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This data represents the graphic portrayal of land parcels and their spatial relationships throughout York County, South Carolina. Land parcel boundaries are also the basis for and define coincident boundaries for other layers, such as zoning, subdivisions, public safety response (ORI -Police, Fire, EMS) and Jurisdiction.Boundaries are established from a variety of sources including cadastral plats, subdivision plats, deeds, land contracts, right-of-way plats, and others. Each feature represents a parcel of land that is inventoried by a unique identifier, referred to as a “Tax Map Id” number. This dataset also includes multi-unit structures which have separate tax accounts for each unit, such as condominium units, represented as stacked polygon features. The parent parcel number [ParentTaxID] for the land parcel is distinguished from the child parcel [TaxMapID] for the condo unit. This data does not include mobile home data. Attributes include data stored within the Esri Fabric data model combined with those from the CAMA data. Examples of relevant attributes include:the [TaxMapID], [ParcelID] and [AprAccNum] can be used to uniquely identify each parcel. the [MailAddr1], [MailAddr2], [MailApt], [MailCity], [MailState], [MailZip] can be used as the full tax billing address for the owner.The [Owner1], [Owner2], [Owner3] describe the owner.the [YearBuilt] offers the oldest year a building was built on the property, reference this web map for info on potential lead pipes on premises;the area of the parcel in acres [GISSizeAC] as calculated from the parcel geometry and also the [deededAcres] from recorded documents, and ;the date that the parcel boundary was last edited [DATE_MODIFIED].How were parcels compiled? This layer was initially developed as an ink-on-mylar property maps maintained by the County from the early 1970's through around 2001.In the 1990s, the county procured services to convert parcels from source documents, however the product delivered in 2000 used a methodology which lost fidelity of source documents. Since then, county staff adhered to this same methodology in their daily work. Between 2001 and 2015 staff used an Esri topology to maintain parcel data in ArcMap. In 2015 the county migrated to Parcel Fabric (ArcMap) and then in 2021 to Pro (2.6/10.8.1 Enterprise) Parcel Fabric. In May of 2021 the county began outsourcing maintenance of parcel edits. This has worked well and was initiated in part to ensure a higher standard of editing practice was adhered to, but also to fulfil a shortage of skilled staff in the job market. County parcel mapping staff remain responsible for simple transactions (merge, split), compilation of materials to create vendor edit request task, and QC or review of vendor work. In Q4 2021, County Staff performed a needs assessment to review alignment issues between parcels and other layers and the internal business requirements for data alignment to parcels. They determined boundary layers must remain coincident with parcels, which are used in decision making by citizens and across many areas of government. Also, it was determined that our parcels had many errors from 20 years of edits in a non-Fabric data model and the previous editing practices. The county will be remapping parcels using ARP grant funding in the 2023-2024 timeframe. Upon delivery in 2024, data maintenance practices will ensure ongoing alignment with parcels.Year BuiltTo obtain the year built for structures on a property, use the 'Buildings' table available through our open data portal.Once you have downloaded the 'Buildings' table and this parcels layer, consider processing the building records in some way to join or perform a relate as there could be many buildings on one parcel, using the following fields:Parcel.AprAccNum = BuildingTable.PropertyID(Note: 98,227 parcels have 1 building, 647 parcels have 2 buildings, 272 have 3 or more)Data SchemaReview the Parcel schema document (PDF) to gain a better understand of the data fields. Access the file geodatabase source data in SC State Plane coordinate system

The Santa Cruz County Impervious Surfaces map is a 5-class fine-scale polygon vector representation of all artificial impervious surfaces in Santa Cruz County. There are 242,471 features in the dataset. Non-impervious areas are not mapped and are not covered by polygons. The impervious map represents the state of the landscape in summer, 2020. This data product was produced by the impervious mapping team at the University of Vermont Spatial Analysis Lab. Table 1 lists download locations for the dataset.

Santa Cruz County impervious surfaces data product availability






  Description


  Link




  File GDB


  https://vegmap.press/Santa_Cruz_Impervious_FileGDB




  ArcGIS Pro Layer Package


  https://vegmap.press/Santa_Cruz_Impervious_Layer_Package




  Vector Tile Layer


  https://vegmap.press/Santa_Cruz_Impervious_Vector_Tile_Layer

Detailed Dataset Description: The impervious map was created using “expert systems” rulesets developed in Trimble Ecognition. These rulesets combine automated image segmentation with-object based image classification techniques. In contrast with machine learning approaches, expert systems rulesets are developed heuristically based on the knowledge of experienced image analysts. Key data sets used in the expert systems rulesets for impervious mapping included: high resolution (6 inch or greater) 4-band orthophotography (2020), the lidar point cloud (2020), and lidar derived rasters such as the canopy height model. After it was produced using Trimble Ecognition, the preliminary impervious map product was manually edited by a team of UVM’s photo interpreters. Manual editing corrected errors where the automated methods produced incorrect results. The impervious map has 5 classes, which are described below:

Building – Structures including homes, commercial buildings, outbuildings, and other human-made structures such as water tanks and silage silos. Structures fully occluded by vegetation will not be mapped.




Paved Road – Roads that are paved and wide enough for a vehicle.




Dirt/Gravel Road – Dirt or gravel roads wide enough for a vehicle. Non-ephemeral fire roads, ranch roads and long driveways. Polygons representing narrow unpaved (single track) trails are not included in this data product.




Other Dirt/Gravel Surface – Dirt or gravel surfaces that are highly compacted and used by humans and equipment, such as parking lots, road pull-offs, some dirt or gravel paths, and highly compacted areas around commercial activities. This class DOES NOT include natural turf playing fields, very lightly used dirt roads, livestock areas, naturally occurring bare soil or rock, or bare areas around ponds.




Other Paved Surface – Includes parking lots, sidewalks, paved walking paths, swimming pools, tennis courts.

Miscellaneous quality control and processing notes:

Zoom level used during manual quality control was no finer than 1 to 500.


Vector data was created with no overlapping polygons.

Data Limitations: This is not a planimetric data product and was created using semi-automated techniques. It provides a reasonable and useful depiction of impervious surfaces for planner and managers but does not have the accuracy or precision to support engineering. Please note that this dataset does not contain information about ownership potential access restrictions. Appropriate uses of the data product include:

As an input to storm water models




For planners to assess % imperviousness in a parcel/watershed




To help identify areas of human infrastructure for fuels and fire management




As an input to fuel models that are used in fire behavior and fire spread models




For cartography and mapping




Generally for use at scales 1:1,000 and smaller




Inappropriate uses of this product include:




Measuring exact square footage of structures or impervious features for building projects




Using the impervious as geographically precise information in transportation and public works




Determining ownership or maintenance responsibility of a particular feature, such as a paved or dirt road




Identifying publicly accessible areas for recreation or other uses

Confirming the suitability of a surface for any use including driving, hiking, bicycling, etc.

The protected areas include National Parks, Areas of Outstanding Natural Beauty and National Scenic Areas. The original datasets used to create this are listed and linked below: National Parks (England)Areas of Outstanding Natural Beauty (England)Areas of Outstanding Natural Beauty (Wales)Areas of Outstanding Natural Beauty (Northern Ireland)National Scenic AreasOtter Data filtered to the relevant years and then to only include open recordsLand Cover Map 2019 (25m rasterised land parcels, GB)Citation: Morton, R. D.; Marston, C.G.; O’Neil, A. W.; Rowland, C. S. (2020). Land Cover Map 2019 (25m rasterised land parcels, GB). NERC Environmental Information Data Centre. https://doi.org/10.5285/f15289da-6424-4a5e-bd92-48c4d9c830ccLand Cover Map 2019 (25m rasterised land parcels, N. Ireland)Citation: Morton, R. D.; Marston, C.G.; O’Neil, A. W.; Rowland, C. S. (2020). Land Cover Map 2019 (25m rasterised land parcels, N. Ireland). NERC Environmental Information Data Centre. https://doi.org/10.5285/2f711e25-8043-4a12-ab66-a52d4e649532OS Open RiversData was processed in ArcGIS Pro before being shared to ArcGIS Online before being used in Report Builder for ArcGIS.

Statewide Download (FGDB) (SHP)Users can also download smaller geographic areas of this feature service in ArcGIS Pro using the Copy Features geoprocessing tool. The address service contains statewide address points and related landmark name alias table and street name alias table.The New Jersey Office of Information Technology, Office of GIS (NJOGIS), in partnership with several local GIS and public safety agencies, has built a comprehensive statewide NG9-1-1 database meeting and exceeding the requirements of the National Emergency Number Association (NENA) 2018 NG9-1-1 GIS Data Standard (NENA-STA-006.1-2018). The existing New Jersey Statewide Address Point data last published in 2016 has been transformed in the NENA data model to create this new address point data.The initial address points were processed from statewide parcel records joined with the statewide Tax Assessor's (MOD-IV) database in 2015. Address points supplied by Monmouth County, Sussex County, Morris County and Montgomery Township in Somerset County were incorporated into the statewide address points using customized Extract, Transform and Load (ETL) procedures.The previous version of the address points was loaded into New Jersey's version of the NENA NG9-1-1 data model using Extract, Transform and Load (ETL) procedures created with Esri's Data Interoperability Extension. Subsequent manual and bulk processing corrections and additions have been made, and are ongoing.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

This layer shows which parts of the United States and Puerto Rico fall within ten minutes' walk of one or more grocery stores. It is estimated that 20% of U.S. population live within a 10 minute walk of a grocery store, and 92% of the population live within a 10 minute drive of a grocery store. The layer is suitable for looking at access at a neighborhood scale.When you add this layer to your web map, along with the drivable access layer and the SafeGraph grocery store layer, it becomes easier to spot grocery stores that sit within a highly populated area, and grocery stores that sit in a shopping center far away from populated areas. Add the Census block points layer to show a popup with the count of stores within 10 minutes' walk and drive. This view of a city begins to hint at the question: how many people have each type of access to grocery stores? And, what if they are unable to walk a mile regularly, or don't own a car?How to Use This Layer in a Web MapUse this layer in a web map to introduce the concepts of access to grocery stores in your city or town. This is the kind of map where people will want to look up their home or work address to validate what the map is saying. See this example web map which you can use in your projects, storymaps, apps and dashboards.The layer was built with that use in mind. Many maps of access use straight-line, as-the-crow-flies distance, which ignores real-world barriers to walkability like rivers, lakes, interstates and other characteristics of the built environment. Block analysis using a network data set and Origin-Destination analysis factors these barriers in, resulting in a more realistic depiction of access.Lastly, this layer can serve as backdrop to other community resources, like food banks, farmers markets (example), and transit (example). Add a transit layer to immediately gauge its impact on the population's grocery access. You can also use this map to see how it relates to communities of concern. Add a layer of any block group or tract demographics, such as Percent Senior Population (examples), or Percent of Households with Access to 0 Vehicles (examples).The layer is a useful visual resource for helping community leaders, business and government leaders see their town from the perspective of its residents, and begin asking questions about how their community could be improved.Data sourcesPopulation data is from the 2010 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer.Grocery store locations are from SafeGraph, reflecting what was in the data as of October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters.The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Alternative versions of these layers are available. These pairs use different colors but are otherwise identical in content.Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis.The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels.The SafeGraph grocery store locations were created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 records. In this map, this layer is included as a vector tile layer.MethodologyEvery census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway.A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in.The results for each analysis were captured in the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle).The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step.Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool uses a 200 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect.Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point.Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes