See full Data Guide here. Drainage Basin Set:

Connecticut Drainage Basins is 1:24,000-scale, polygon and line feature data that define natural drainage areas in Connecticut. These are small basin areas that average approximately 1 square mile in size and make up, in order of increasing size, the larger local, subregional, regional, and major drainage basin areas. Connecticut Drainage Basins includes drainage areas for all Connecticut rivers, streams, brooks, lakes, reservoirs and ponds published on 1:24,000-scale 7.5 minute topographic quadrangle maps prepared by the USGS between 1969 and 1984. Data is compiled at 1:24,000 scale (1 inch = 2,000 feet). This information is not updated. Polygon and line features represent drainage basin areas and boundaries, respectively. Each basin area (polygon) feature is outlined by one or more major, regional, subregional, local, impoundment, or river reach boundary (line) feature. These data include 7,076 basin area (polygon) features and 20,945 basin boundary (line) features. Basin area (polygon) attributes include major, regional, subregional, local, (full) basin number, and feature size in acres and square miles. The full basin number (BASIN_NO) uniquely identifies individual basins and is up to 13 characters in length. There are 7,031 unique basin numbers. Examples include 6000-00-1+*, 4300-00-1+L1, and 6002-00-2-R1. The first digit (column 1) designates the major basin, the first two digits (columns 1-2) designate the regional basin, the first 4 digits (columns 1-4) designate the subregional basin, and the first seven digits (columns 1-7) designate the local basin. Note, there are slightly more basin polygon features (7,076) than unique basin numbers (7,031) primarily because a few water supply watershed boundaries split a basin into two polygon features at the location of a small dam or point of diversion along a stream. Basin boundary (line) attributes include a drainage divide type attribute (DIVIDE) used to cartographically represent the hierarchical drainage basin system. This divide type attribute is used to assign different line symbology to major, regional, subregional, local, stream reach, and lake impoundment drainage basin divides. For example, major basin drainage divides are more pronounced and shown with a wider line symbol than regional basin drainage divides. Connecticut Drainage Basins is the data source for other digital spatial data including the Connecticut Major Drainage Basins, Connecticut Regional Drainage Basins, Connecticut Subregional Drainage Basins, and Connectcut Local Drainage Basins. Purpose: The polygon features define the contributing drainage area for individual reservoirs, lakes, ponds and river and stream reaches in Connecticut. These are hydrologic land units where precipitation is collected. Rain falling in a basin may take two courses. It may both run over the land and quickly enter surface watercourses, or it may soak into the ground moving through the earth until it surfaces at a wetland or stream. In an undisturbed natural drainage basin, the surface and ground water arrive as precipitation and leave either by evaporation or as surface runoff at the basin's outlet. A basin is a self-contained hydrologic system, with a clearly defined water budget and cycle. The amount of water that flows into the basins equals the amount that leaves. A drainage divide is the topographic barrier along a ridge or line of hilltops separating adjacent drainage basins. For example, rain or snow melt draining down one side of a hill generally will flow into a different basin and stream than water draining down the other side of the hill. These hillsides are separated by a drainage divided that follows nearby hilltops and ridge lines. Use these basin data to identify where rainfall flows over land and downstream to a particular watercourse. Use these data to categorize and tabulate information according to drainage basin by identifying the basin number for individual reservoir, lake, pond, stream reach, or location of interest. Due to the hierarchical nature of the basin numbering system, a database that records the 13-digit basin number for individual geographic locations of interest will support tabulations by major, regional, subregional or local basin as well as document the unique 13-digit basin number. To identify either all upstream basins draining to a particular location or all downstream basins flowing from a particular location, refer to the Gazetteer of Drainage Basin Areas of Connecticut, Nosal, 1977, CT DEP Water Resources Bulletin 45, for the hydrologic sequence, headwater to outfall, of drainage basins available at http://cteco.uconn.edu/docs/wrb/wrb45_gazetteer_of_drainage_areas_of_connecticut.pdf Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.). Not intended for analysis with other digital data compiled at scales greater than or more detailed than 1:24,000 scale. Use these data with 1:24,000-scale hydrography data also available from the State of Connecticut, Department of Environmental Protection.

onnecticut Drainage Basins is 1:24,000-scale, polygon and line feature data that define natural drainage areas in Connecticut. These are small basin areas that average approximately 1 square mile in size and make up, in order of increasing size, the larger local, subregional, regional, and major drainage basin areas. Connecticut Drainage Basins includes drainage areas for all Connecticut rivers, streams, brooks, lakes, reservoirs and ponds published on 1:24,000-scale 7.5 minute topographic quadrangle maps prepared by the USGS between 1969 and 1984. Data is compiled at 1:24,000 scale (1 inch = 2,000 feet). This information is not updated. Polygon and line features represent drainage basin areas and boundaries, respectively. Each basin area (polygon) feature is outlined by one or more major, regional, subregional, local, impoundment, or river reach boundary (line) feature. These data include 7,076 basin area (polygon) features and 20,945 basin boundary (line) features. Basin area (polygon) attributes include major, regional, subregional, local, (full) basin number, and feature size in acres and square miles. The full basin number (BASIN_NO) uniquely identifies individual basins and is up to 13 characters in length. There are 7,031 unique basin numbers. Examples include 6000-00-1+*, 4300-00-1+L1, and 6002-00-2-R1. The first digit (column 1) designates the major basin, the first two digits (columns 1-2) designate the regional basin, the first 4 digits (columns 1-4) designate the subregional basin, and the first seven digits (columns 1-7) designate the local basin. Note, there are slightly more basin polygon features (7,076) than unique basin numbers (7,031) primarily because a few water supply watershed boundaries split a basin into two polygon features at the location of a small dam or point of diversion along a stream. Basin boundary (line) attributes include a drainage divide type attribute (DIVIDE) used to cartographically represent the hierarchical drainage basin system. This divide type attribute is used to assign different line symbology to major, regional, subregional, local, stream reach, and lake impoundment drainage basin divides. For example, major basin drainage divides are more pronounced and shown with a wider line symbol than regional basin drainage divides. Connecticut Drainage Basins is the data source for other digital spatial data including the Connecticut Major Drainage Basins, Connecticut Regional Drainage Basins, Connecticut Subregional Drainage Basins, and Connectcut Local Drainage Basins.

The Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 19 of the Atlas, Cretaceous Mannville Group of the Western Canada Sedimentary Basin, Figure 6, Cadomin/Cut Bank Isopach and Lithofacies. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.

PLSSSecondDivision: This data set represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.

The GIS boundary for the Proposed Thompson Divide Withdrawal that will reserve the identified Federal lands and mineral interest from operation of the public land laws, mining laws, and mineral leasing, mineral materials, and geothermal leasing laws for up to 20 years to protect wildlife, recreation, ecological and scenic values, as described in Federal Register Notice 2022-22448 Vol. 87 No. 199 page 62878. Edits to the boundary have been incorporated from the US Forest Service and from the Bureau of Land Management in order to follow features that allow for legal land descriptions to be generated and eliminate the need for a new cadastral survey. All US Forest Service edits were made with direction USFS land managers from the White River National Forest and the Grand Mesa, Uncompahgre, and Gunnison National Forest. The Greater Thompson Divide withdraws 221,898.23 acres, including approximately 197,744.66 acres of National Forest System lands, approximately 15,464.99 acres of BLM-managed public lands, and approximately 8,688.58 acres of reserved Federal mineral interest, from all forms of entry, appropriation, and disposal under the public land laws; location and entry under the mining laws; and operation of the mineral leasing, mineral materials, and geothermal leasing laws, subject to valid existing rights, for a period of 20 years. The areas described, including both Federal and non-Federal lands, aggregate approximately 257,439.93 acres. Please refer to the Public Land Order (https://www.federalregister.gov:443/documents/2024/04/08/2024-07384/public-land-order-no-7939-thompson-divide-withdrawal-colorado) PLO No. 7939 for more information on the legal land description of the boundary.

BLM NV PLSSSpecialSurvey: This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.

Summary: This dataset contains an inventory of City of Los Angeles Sidewalks and related features (Access Ramps, Curbs, Driveways, and Parkways).Background: This inventory was performed throughout 2017 using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines. The dataset has not been updated since its creation.Description: The following provides more detail about the feature classes in this dataset. All features were digitized (“traced”) as observed in the orthophotography (digital aerial photos) and assigned the Parcel Identification Number (PIN) of their corresponding property:Sidewalk (polygon) – represents paved pedestrian walkways. Typical widths are between 3‐6 feet in residential areas and larger and more variable in commercial and high‐density traffic areas.Alley-Sidewalk (polygon) – represents the prevailing walkway or path of travel at the entrance/exit of an alley. Digitized as Sidewalk features but categorized as Alley Sidewalk and assigned a generic PIN value, ALLEY SIDEWALK.Corner Polygon (polygon) - feature created where sidewalks from two streets meet but do not intersect (i.e. at corner lots). There’s no standard shape/type and configurations vary widely. These are part of the Sidewalk feature class.In commercial and high‐density residential areas where there is only continuous sidewalk (no parkway strip), the sidewalk also functions as a Driveway.Driveway (polygon) – represents area that provides vehicular access to a property. Features are not split by extended parcel lot lines except when two adjacent properties are served by the same driveway approach (e.g. a common driveway), in which case they are and assigned a corresponding PIN.Parkway (polygon) – represents the strip of land behind the curb and in front of the sidewalk. Generally, they are landscaped with ground cover but they may also be filled in with decorative stone, pavers, decomposed granite, or concrete. They are created by offsetting lines, the Back of Curb (BOC) line and the Face of Walk (FOW). The distance between the BOC and FOW is measured off the aerial image and rounded to the nearest 0.5 foot, typically 6 – 10 feet.Curb (polygon) – represents the concrete edging built along the street to form part of the gutter. Features are always 6” wide strips and are digitized using the front of curb and back of curb digitized lines. They are the leading improvement polygon and are created for all corner, parkway, driveway and, sidewalk (if no parkway strip is present) features.Curb Ramp, aka Access Ramp (point) – represents the geographic center (centroid) of Corner Polygon features in the Sidewalk feature class. They have either a “Yes” or “No” attribute that indicates the presence or absence of a wheelchair access ramp, respectively.Fields: All features include the following fields...FeatureID – a unique feature identifier that is populated using the feature class’ OBJECTID fieldAssetID – a unique feature identifier populated by Los Angeles City staff for internal usePIND – a unique Parcel Identification Number (PIN) for all parcels within the City of L.A. All Sidewalk related features will be split, non-overlapping, and have one associated Parcel Identification Number (PIN). CreateDate – indicates date feature was createdModifiedDate – indicates date feature was revised/editedCalc_Width (excluding Access Ramps) – a generalized width of the feature calculated using spatial and mathematical algorithms on the feature. In almost all cases where features have variable widths, the minimum width is used. Widths are rounded to the nearest whole number. In cases where there is no value for the width, the applied algorithms were unable to calculate a reliable value.Calc_Length (excluding Access Ramps) – a generalized length of the feature calculated using spatial and mathematical algorithms on the feature. Lengths are rounded to the nearest whole number. In cases where there is no value for the length, the applied algorithms were unable to calculate a reliable value.Methodology: This dataset was digitized using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines.The general work flow is as follows:Create line work based on digital orthophotography, working from the face‐of‐curb (FOC) inward to the property right-of-way (ROW)Build sidewalk, parkway, driveway, and curb polygons from the digitized line workPopulate all polygons with the adjacent property PIN and classify all featuresCreate Curb Ramp pointsWarnings: This dataset has been provided to allow easy access and a visual display of Sidewalk and related features (Parkways, Driveway, Curb Ramps and Curbs). Every reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Other things to keep in mind about this dataset are listed below:Obscured Features – The existence of dense tree canopy or dark shadows in the aerial imagery tend to obscure or make it difficult to discern the extent of certain features, such as Driveways. In these cases, they may have been inferred from the path in the corresponding parcel. If a feature and approach was completely obscured, it was not digitized. In certain instances the coloring of the sidewalk and adjacent pavement rendered it impossible to identify the curb line or that a sidewalk existed. Therefore a sidewalk may or may not be shown where one actually may or may not exist.Context: The following links provide information on the policy context surrounding the creation of this dataset. It includes links to City of L.A. websites:Willits v. City of Los Angeles Class Action Lawsuit Settlementhttps://www.lamayor.org/willits-v-city-la-sidewalk-settlement-announcedSafe Sidewalks LA – program implemented to repair broken sidewalks in the City of L.A., partly in response to the above class action lawsuit settlementhttps://sidewalks.lacity.org/Data Source: Bureau of EngineeringNotes: Please be aware that this dataset is not actively being maintainedLast Updated: 5/20/20215/20/2021 - Added Calc_Width and Calc_Length fieldsRefresh Rate: One-time deliverable. Dataset not actively being maintained.

Integrated terrain models covering 16,357 square kilometers of the Massachusetts coastal zone and offshore waters were built to provide a continuous elevation and bathymetry terrain model for ocean planning purposes. The area is divided into the following four geographical areas to reduce file size and facilitate publishing: Massachusetts Bay from the Massachusetts-New Hampshire border south to Provincetown and Scituate and east to Stellwagen Bank; Cape Cod Bay from Provincetown to Scituate and south to Hyannis; Buzzards Bay from the Cape Cod Canal southwest to the State border including the Elizabeth Islands and extending north to Fall River and Mount Hope Bay; and Nantucket and Vineyard Sounds, from Hyannis south to the border of the Massachusetts Coastal zone approximately 8 kilometers south of Nantucket. A Triangulated Irregular Network was created from public-domain bathymetric and LiDAR data using the ArcGIS terrain-model framework and then interpolated into a 32-bit GeoTiff of 10 meter resolution. The grids for each of the four geographical areas are referenced to the Universal Transverse Mercator, Zone 19, North American Datum of 1983 coordinate system, and the North American Vertical Datum of 1988. A polygon shapefile recording the source datasets accompanies each of the four grids.

The Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 19 of the Atlas, Cretaceous Mannville Group of the Western Canada Sedimentary Basin, Figure 6, Cadomin/Cut Bank Isopach and Lithofacies. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.

Natural Earth is a public domain map dataset available at 1:10m, 1:50m, and 1:110 million scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.

Natural Earth was built through a collaboration of many volunteers and is supported by NACIS (North American Cartographic Information Society).

Natural Earth Vector comes in ESRI shapefile format, the de facto standard for vector geodata. Character encoding is Windows-1252.

Natural Earth Vector includes features corresponding to the following:

Cultural Vector Data Thremes:

• Countries: matched boundary lines and polygons with names attributes for countries and sovereign states. Includes dependencies (French Polynesia), map units (U.S. Pacific Island Territories) and sub-national map subunits (Corsica versus mainland Metropolitan France).
• Disputed areas and breakaway regions - From Kashmir to the Elemi Triangle, Northern Cyprus to Western Sahara.
• First order admin (provinces, departments, states, etc.): internal boundaries and polygons for all but a few tiny island nations. Includes names attributes and some statistical groupings of the same for smaller countries.
• Populated places: point symbols with name attributes. Includes capitals, major cities and towns, plus significant smaller towns in sparsely inhabited regions. We favor regional significance over population census in determining rankings.
• Urban polygons: derived from 2002-2003 MODIS satellite data.
• Parks and protected areas: US National Park Service units.
• Pacific nation groupings: boxes for keeping these far-flung islands tidy.
• Water boundary indicators: partial selection of key 200-mile nautical limits, plus some disputed, treaty, and median lines.

Physical Vector Data Themes:

• Coastline: ocean coastline, including major islands. Coastline is matched to land and water polygons.
• Land: Land polygons including major islands
• Ocean: Ocean polygon split into contiguous pieces.
• Minor Islands: additional small ocean islands ranked to two levels of relative importance.
• Reefs: major coral reefs from WDB2.
• Physical region features: polygon and point labels of major physical features.
• Rivers and Lake Centerlines: ranked by relative importance. Includes name and line width attributes. Don’t want minor lakes? Turn on their centerlines to avoid unseemly data gaps.
• Lakes: ranked by relative importance, coordinating with river ranking. Includes name attributes.
• Glaciated areas: polygons derived from DCW, except for Antarctica derived from MOA. Includes name attributes for major polar glaciers.
• Antarctic ice shelves: derived from 2003-2004 MOA. Reflects recent ice shelf collapses.
• Bathymetry: nested polygons at 0, -200, -1,000, -2,000, -3,000, -4,000, -5,000, -6,000, -7,000, -8,000, -9,000,and -10,000 meters. Created from SRTM Plus.
• Geographic lines: Polar circles, tropical circles, equator, and International Date Line.
• Graticules: 1-, 5-, 10-, 15-, 20-, and 30-degree increments. Includes WGS84 bounding box.

Tabular data of population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2010 census tracts split by 2019 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/) released 2010 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Field:CT10: 2010 Census tractFIP19: 2019 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2019) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT10FIP19CSA: 2010 census tract with 2019 city FIPs for incorporated cities, unincorporated areas and LA neighborhoods. SPA12: 2012 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD12: 2012 Health District (HD) number: HD_NAME: Health District name.POP19_AGE_0_4: 2019 population 0 to 4 years oldPOP19_AGE_5_9: 2019 population 5 to 9 years old POP19_AGE_10_14: 2019 population 10 to 14 years old POP19_AGE_15_17: 2019 population 15 to 17 years old POP19_AGE_18_19: 2019 population 18 to 19 years old POP19_AGE_20_44: 2019 population 20 to 24 years old POP19_AGE_25_29: 2019 population 25 to 29 years old POP19_AGE_30_34: 2019 population 30 to 34 years old POP19_AGE_35_44: 2019 population 35 to 44 years old POP19_AGE_45_54: 2019 population 45 to 54 years old POP19_AGE_55_64: 2019 population 55 to 64 years old POP19_AGE_65_74: 2019 population 65 to 74 years old POP19_AGE_75_84: 2019 population 75 to 84 years old POP19_AGE_85_100: 2019 population 85 years and older POP19_WHITE: 2019 Non-Hispanic White POP19_BLACK: 2019 Non-Hispanic African AmericanPOP19_AIAN: 2019 Non-Hispanic American Indian or Alaska NativePOP19_ASIAN: 2019 Non-Hispanic Asian POP19_HNPI: 2019 Non-Hispanic Hawaiian Native or Pacific IslanderPOP19_HISPANIC: 2019 HispanicPOP19_MALE: 2019 Male POP19_FEMALE: 2019 Female POV19_WHITE: 2019 Non-Hispanic White below 100% Federal Poverty Level POV19_BLACK: 2019 Non-Hispanic African American below 100% Federal Poverty Level POV19_AIAN: 2019 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV19_ASIAN: 2019 Non-Hispanic Asian below 100% Federal Poverty Level POV19_HNPI: 2019 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV19_HISPANIC: 2019 Hispanic below 100% Federal Poverty Level POV19_TOTAL: 2019 Total population below 100% Federal Poverty Level POP19_TOTAL: 2019 Total PopulationAREA_SQMIL: Area in square milePOP19_DENSITY: Population per square mile.POV19_PERCENT: Poverty percentage.How this data created?The tabular data of population by age groups, by ethnic groups and by gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2010 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Note:1. Population and poverty data estimated as of July 1, 2019. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundary are not the same because boundary is reviewed and updated annually.

This is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

PLSSIntersected: This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.

Tabular data of population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2010 census tracts split by 2016 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/) released 2010 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Field:CT10: 2010 Census tractFIP16: 2016 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2016) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT10FIP16CSA: 2010 census tract with 2016 city FIPs for incorporated cities, unincorporated areas and LA neighborhoods. SPA12: 2012 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD12: 2012 Health District (HD) number: HD_NAME: Health District name.POP16_AGE_0_4: 2016 population 0 to 4 years oldPOP16_AGE_5_9: 2016 population 5 to 9 years old POP16_AGE_10_14: 2016 population 10 to 14 years old POP16_AGE_15_17: 2016 population 15 to 17 years old POP16_AGE_18_19: 2016 population 18 to 19 years old POP16_AGE_20_44: 2016 population 20 to 24 years old POP16_AGE_25_29: 2016 population 25 to 29 years old POP16_AGE_30_34: 2016 population 30 to 34 years old POP16_AGE_35_44: 2016 population 35 to 44 years old POP16_AGE_45_54: 2016 population 45 to 54 years old POP16_AGE_55_64: 2016 population 55 to 64 years old POP16_AGE_65_74: 2016 population 65 to 74 years old POP16_AGE_75_84: 2016 population 75 to 84 years old POP16_AGE_85_100: 2016 population 85 years and older POP16_WHITE: 2016 Non-Hispanic White POP16_BLACK: 2016 Non-Hispanic African AmericanPOP16_AIAN: 2016 Non-Hispanic American Indian or Alaska NativePOP16_ASIAN: 2016 Non-Hispanic Asian POP16_HNPI: 2016 Non-Hispanic Hawaiian Native or Pacific IslanderPOP16_HISPANIC: 2016 HispanicPOP16_MALE: 2016 Male POP16_FEMALE: 2016 Female POV16_WHITE: 2016 Non-Hispanic White below 100% Federal Poverty Level POV16_BLACK: 2016 Non-Hispanic African American below 100% Federal Poverty Level POV16_AIAN: 2016 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV16_ASIAN: 2016 Non-Hispanic Asian below 100% Federal Poverty Level POV16_HNPI: 2016 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV16_HISPANIC: 2016 Hispanic below 100% Federal Poverty Level POV16_TOTAL: 2016 Total population below 100% Federal Poverty Level POP16_TOTAL: 2016 Total PopulationAREA_SQMIL: Area in square milePOP16_DENSITY: Population per square mile.POV16_PERCENT: Poverty rate/percentage.How this data created?The tabular data of population by age groups, by ethnic groups and by gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2010 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Note:1. Population and poverty data estimated as of July 1, 2016. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundary are not the same because boundary is reviewed and updated annually.

The Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 19 of the Atlas, Cretaceous Mannville Group of the Western Canada Sedimentary Basin, Figure 6, Cadomin/Cut Bank Isopach and Lithofacies. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.

The Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 19 of the Atlas, Cretaceous Mannville Group of the Western Canada Sedimentary Basin, Figure 6, Cadomin/Cut Bank Isopach and Lithofacies. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.

[Metadata] Underground Injection Control Line - POLYGONS (UIC Polys). NOTE: If you need to determine whether your parcel/project is above or below the UIC line, please contact the DOH Safe Drinking Water Branch (SDWB) at (808) 586-4258. This layer should be used ONLY as a low resolution/rough cut approximation of where the UIC lines are located. May, 2023 - Data is still current, per DOH SDWB. Upon request by the State DOH SDWB, the GIS Program made several modifications to this layer. 1. Changed the UIC_Code attributes from a numeric code field to a text field in order to add clarity to the meaning of the attribute values (whether the area was above or below the UIC line). 2. Created a uic_line layer from the uic_poly layer to reduce confusion when using the layer to depict and refer to the UIC "LINE" and to enable more straightforward symbolization of the layer. The uic_poly layer is being kept in place to allow for easier analysis. For additional information, please refer to metadata at https://files.hawaii.gov/dbedt/op/gis/data/uic_poly.pdf or contact the Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, Hi. 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.

Connectivity_Belote_HD: From Belote et al. 2022, we used the middle tolerance scenario with a 150 m moving window and reclassified raster based on the mean value (.727). Everything above the mean was considered "suitable" connectivity. The layer was clipped to the analysis area and converted into a polygon.

Potential stewardship for Residential parcels in Baltimore City summarized by block group. Residential parcels was defined as only those parcels with a land use code of residential (LU_CODE = "R") based on the 2003 Maryland Property View A&T database. PRIZM 5, 15, and 62 classes are also present. PRIZM is the Potential Rating Index by Zip code Markets produced by the Claritas Corporation - > http://www.clusterbigip1.claritas.com/claritas/Default.jsp>.

   Total Potential stewardship is that land within a parcels not occupied by buildings, that is land that could potentially support vegetation, regardless of whether or not any vegetation is present. Realized Potential Stewardship is land that is currently occupied by vegetation. Not Realized Potential Stewardship is the land not occupied by buildings or existing vegetation, and is thus the land that is potentially available for "greening" initiatives. Normalization for realized and not realized potential stewardship is carried out by dividing by the total potential stewardship. 


   The potential stewardship was calculated using parcel data, building footprints, and GDT census block groups. Building footprints were erased from the parcel area, resulting in a layer indicating the potential stewardship for each parcel. The potential stewardship layer was then unioned MD DNR's 2001 SUFA vegetation layer. All polygons corresponding to water features were deleted since water features cannot undergo "greening."  All polygons that did fall in the potential stewardship area were deleted. This resulted in a layer in which the polygons represented the potential stewardship land along with the potential stewardship land occupied by either grass or trees. This layer was then intersected with the census block group layer resulting in a layer that had the potential stewardship land, potential stewardship vegetation, and block group IDs. All attributes were then summarized at the block group level.


   A cursory analysis of the parcel data indicated that parcel data was outdated for the following block groups: 245102503031, 245102503032, and 245102503033. Certain block groups with very high Normalized Total Potential Stewardship values may be indicative of the fact that building footprint data was missing, although the extent of this problem is unknown.


   Note: transportation networks are not part of the parcel data, and thus were appropriately not part of this analysis.

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 March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

City boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities 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
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_COUNTY: 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.
• CDTFA_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. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• 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

Polygon file representing the precinct split boundaries in Indianapolis and Marion County, Indiana. Data projection: NAD 1983 StatePlane Indiana East FIPS 1301 (US Feet)