Overview

This dataset contains all DOMI Street Closure Permit data in the Computronix (CX) system from the date of its adoption (in May 2020) until the present. The data in each record can be used to determine when street closures are occurring, who is requesting these closures, why the closure is being requested, and for mapping the closures themselves. It is updated hourly (as of March 2024).

Preprocessing/Formatting

It is important to distinguish between a permit, a permit's street closure(s), and the roadway segments that are referenced to that closure(s).

• The CX system identifies a street in segments of roadway. (As an example, the CX system could divide Maple Street into multiple segments.)

• A single street closure may span multiple segments of a street.

• The street closure permit refers to all the component line segments.

• A permit may have multiple streets which are closed. Street closure permits often reference many segments of roadway.

The roadway_id field is a unique GIS line segment representing the aforementioned segments of road. The roadway_id values are assigned internally by the CX system and are unlikely to be known by the permit applicant. A section of roadway may have multiple permits issued over its lifespan. Therefore, a given roadway_id value may appear in multiple permits.

The field closure_id represents a unique ID for each closure, and permit_id uniquely identifies each permit. This is in contrast to the aforementioned roadway_id field which, again, is a unique ID only for the roadway segments.

City teams that use this data requested that each segment of each street closure permit be represented as a unique row in the dataset. Thus, a street closure permit that refers to three segments of roadway would be represented as three rows in the table. Aside from the roadway_id field, most other data from that permit pertains equally to those three rows. Thus, the values in most fields of the three records are identical.

Each row has the fields segment_num and total_segments which detail the relationship of each record, and its corresponding permit, according to street segment. The above example produced three records for a single permit. In this case, total_segments would equal 3 for each record. Each of those records would have a unique value between 1 and 3.

The geometry field consists of string values of lat/long coordinates, which can be used to map the street segments.

All string text (most fields) were converted to UPPERCASE data. Most of the data are manually entered and often contain non-uniform formatting. While several solutions for cleaning the data exist, text were transformed to UPPERCASE to provide some degree of regularization. Beyond that, it is recommended that the user carefully think through cleaning any unstructured data, as there are many nuances to consider. Future improvements to this ETL pipeline may approach this problem with a more sophisticated technique.

Known Uses

These data are used by DOMI to track the status of street closures (and associated permits).

Further Documentation and Resources

An archived dataset containing historical street closure records (from before May of 2020) for the City of Pittsburgh may be found here: https://data.wprdc.org/dataset/right-of-way-permits

This layer displays change in pixels of the Sentinel-2 10m Land Use/Land Cover product developed by Esri, Impact Observatory, and Microsoft. Available years to compare with 2021 are 2018, 2019 and 2020.By default, the layer shows all comparisons together, in effect showing what changed 2018-2021. But the layer may be changed to show one of three specific pairs of years, 2018-2021, 2019-2021, or 2020-2021.Showing just one pair of years in ArcGIS Online Map ViewerTo show just one pair of years in ArcGIS Online Map viewer, create a filter.1. Click the filter button.2. Next, click add expression.3. In the expression dialogue, specify a pair of years with the ProductName attribute. Use the following example in your expression dialogue to show only places that changed between 2020 and 2021:ProductNameis2020-2021By default, places that do not change appear as a transparent symbol in ArcGIS Pro. But in ArcGIS Online Map Viewer, a transparent symbol may need to be set for these places after a filter is chosen. To do this:4. Click the styles button.5. Under unique values click style options.6. Click the symbol next to No Change at the bottom of the legend.7. Click the slider next to "enable fill" to turn the symbol off.Showing just one pair of years in ArcGIS ProTo show just one pair of years in ArcGIS Pro, choose one of the layer's processing templates to single out a particular pair of years. The processing template applies a definition query that works in ArcGIS Pro.1. To choose a processing template, right click the layer in the table of contents for ArcGIS Pro and choose properties.2. In the dialogue that comes up, choose the tab that says processing templates.3. On the right where it says processing template, choose the pair of years you would like to display.The processing template will stay applied for any analysis you may want to perform as well.How the change layer was created, combining LULC classes from two yearsImpact Observatory, Esri, and Microsoft used artificial intelligence to classify the world in 10 Land Use/Land Cover (LULC) classes for the years 2017-2021. Mosaics serve the following sets of change rasters in a single global layer:Change between 2018 and 2021Change between 2019 and 2021Change between 2020 and 2021To make this change layer, Esri used an arithmetic operation combining the cells from a source year and 2021 to make a change index value. ((from year * 16) + to year) In the example of the change between 2020 and 2021, the from year (2020) was multiplied by 16, then added to the to year (2021). Then the combined number is served as an index in an 8 bit unsigned mosaic with an attribute table which describes what changed or did not change in that timeframe.Variable mapped: Change in land cover between 2018, 2019, or 2020 and 2021Data Projection: Universal Transverse Mercator (UTM)Mosaic Projection: WGS84Extent: GlobalSource imagery: Sentinel-2Cell Size: 10m (0.00008983152098239751 degrees)Type: ThematicSource: Esri Inc.Publication date: January 2022What can you do with this layer?Global LULC maps provide information on conservation planning, food security, and hydrologic modeling, among other things. This dataset can be used to visualize land cover anywhere on Earth. This layer can also be used in analyses that require land cover input. For example, the Zonal Statistics tools allow a user to understand the composition of a specified area by reporting the total estimates for each of the classes.Land Cover processingThis map was produced by a deep learning model trained using over 5 billion hand-labeled Sentinel-2 pixels, sampled from over 20,000 sites distributed across all major biomes of the world. The underlying deep learning model uses 6 bands of Sentinel-2 surface reflectance data: visible blue, green, red, near infrared, and two shortwave infrared bands. To create the final map, the model is run on multiple dates of imagery throughout the year, and the outputs are composited into a final representative map.Processing platformSentinel-2 L2A/B data was accessed via Microsoft’s Planetary Computer and scaled using Microsoft Azure Batch.Class definitions1. WaterAreas where water was predominantly present throughout the year; may not cover areas with sporadic or ephemeral water; contains little to no sparse vegetation, no rock outcrop nor built up features like docks; examples: rivers, ponds, lakes, oceans, flooded salt plains.2. TreesAny significant clustering of tall (~15-m or higher) dense vegetation, typically with a closed or dense canopy; examples: wooded vegetation, clusters of dense tall vegetation within savannas, plantations, swamp or mangroves (dense/tall vegetation with ephemeral water or canopy too thick to detect water underneath).4. Flooded vegetationAreas of any type of vegetation with obvious intermixing of water throughout a majority of the year; seasonally flooded area that is a mix of grass/shrub/trees/bare ground; examples: flooded mangroves, emergent vegetation, rice paddies and other heavily irrigated and inundated agriculture.5. CropsHuman planted/plotted cereals, grasses, and crops not at tree height; examples: corn, wheat, soy, fallow plots of structured land.7. Built AreaHuman made structures; major road and rail networks; large homogenous impervious surfaces including parking structures, office buildings and residential housing; examples: houses, dense villages / towns / cities, paved roads, asphalt.8. Bare groundAreas of rock or soil with very sparse to no vegetation for the entire year; large areas of sand and deserts with no to little vegetation; examples: exposed rock or soil, desert and sand dunes, dry salt flats/pans, dried lake beds, mines.9. Snow/IceLarge homogenous areas of permanent snow or ice, typically only in mountain areas or highest latitudes; examples: glaciers, permanent snowpack, snow fields. 10. CloudsNo land cover information due to persistent cloud cover.11. RangelandOpen areas covered in homogenous grasses with little to no taller vegetation; wild cereals and grasses with no obvious human plotting (i.e., not a plotted field); examples: natural meadows and fields with sparse to no tree cover, open savanna with few to no trees, parks/golf courses/lawns, pastures. Mix of small clusters of plants or single plants dispersed on a landscape that shows exposed soil or rock; scrub-filled clearings within dense forests that are clearly not taller than trees; examples: moderate to sparse cover of bushes, shrubs and tufts of grass, savannas with very sparse grasses, trees or other plants.CitationKarra, Kontgis, et al. “Global land use/land cover with Sentinel-2 and deep learning.” IGARSS 2021-2021 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2021.AcknowledgementsTraining data for this project makes use of the National Geographic Society Dynamic World training dataset, produced for the Dynamic World Project by National Geographic Society in partnership with Google and the World Resources Institute.For questions please email environment@esri.com

Map Layers for display from four key Auditor GIS datasets. All map layers are turned off by default. Visibility range in italicsCAUV:Current Agricultural Use Designations (UniqueValues) <1:24,000REAL ESTATE:Commercial Market Areas (UniqueValues) <1:500,000; labels at <1:100,000Residential Market Areas (UniqueValues) <1:225,000: labels at <1:50,000Mobile Home Areas (SingleSymbol) <1:225,000: labels at <1:24,000SCHOOLS:School Districts (UniqueValues) <1:225,000: labels to >1:10,000Elementary Attendance Zones (SingleSymbol) <1:225,000; labels at <1:150,000Junior High School Attendance Zones (SingleSymbol) <1:225,000; labels at <1:150,000High School Attendance Zones (SingleSymbol) <1:225,000; labels at <1:150,000TAX ACCOUNTING:CRAs (Community Reinvestment Areas) (UniqueValues) <1:225,000: labels at <1:50,000Enterprise Zones(UniqueValues) <1:225,000: labels at <1:50,000Taxing Districts (SingleSymbol) <1:225,000: labels to >1:5,000

This parcels polygons feature class represents current city parcels within the City of Los Angeles. It shares topology with the Landbase parcel lines feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcels is entered into attributes. Principal attributes include:PIN and PIND: represents the unique auto-generated parcel identifier and key to related features and tables. This field is related to the LA_LEGAL, LA_APN and LA_HSE_NBR tables. PIN contains spaces and PIND replaces those spaces with a dash (-).LA_LEGAL - Table attributes containing legal description. Principal attributes include the following:TRACT: The subdivision tract number as recorded by the County of Los AngelesMAP_REF: Identifies the subdivision map book reference as recorded by the County of Los Angeles.LOT: The subdivision lot number as recorded by the County of Los Angeles.ENG_DIST: The four engineering Districts (W=Westla, C=Central, V= Valley and H=Harbor).CNCL_DIST: Council Districts 1-15 of the City of Los Angeles. OUTLA means parcel is outside the City.LA_APN- Table attributes containing County of Los Angeles Assessors information. Principal attributes include the following:BPP: The Book, Page and Parcel from the Los Angeles County Assessors office. SITUS*: Address for the property.LA_HSE_NBR - Table attributes containing housenumber information. Principal attributes include the following:HSE_ID: Unique id of each housenumber record.HSE_NBR: housenumber numerical valueSTR_*: Official housenumber addressFor a complete list of attribute values, please refer to Landbase_parcel_polygons_data_dictionary.Landbase parcels polygons data layer was created in geographical information systems (GIS) software to display the location of the right of way. The parcels polygons layer delineates the right of way from Landbase parcels lots. The parcels polygons layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a polygon feature class and attribute data for the features. The area inside a polygon feature is a parcel lot. The area outside of the parcel polygon feature is the right of way. Several polygon features are adjacent, sharing one line between two polygons. For each parcel, there is a unique identifier in the PIND and PIN fields. The only difference is PIND has a dash and PIN does not. The types of edits include new subdivisions and lot cuts. Associated legal information about the landbase parcels lots is entered into attributes. The landbase parcels layer is vital to other City of LA Departments, by supporting property and land record operations and identifying legal information for City of Los Angeles. The landbase parcels polygons are inherited from a database originally created by the City's Survey and Mapping Division. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.ASSETID: User-defined feature autonumber.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral grid index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers. An A-map is the smallest grid in the index map and is used when there is a large amount of spatial information in the map display. There are more parcel lines and annotation than can fit in the B-map, and thus, an A-map is used. There are 4 A-maps in a B-map. In areas where parcel lines and annotation can fit comfortably in an index map, a B-map is used. The B-maps are at a scale of 100 feet, and A-maps are at a scale of 50 feet.OBJECTID: Internal feature number.BPPMAP_REFTRACTBLOCKMODLOTARBCNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/navigatela, click Council Districts layer name, under Boundaries layer group.SHAPE: Feature geometry.BOOKPAGEPARCELPIND: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. The D in the field name PIND, means "dash", and there is a dash between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.PIN: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.

Ecological Land Units (ELUs) are areas of distinct bioclimate, landform, lithology, and land cover that form the basic components of terrestrial ecosystem structure. The ELU layer was produced by combining the values in four 250-m cell-sized rasters using the ArcGIS Combine tool (Spatial Analyst). In 2015 these four components resulted in 3,639 different combinations or ELUs, which is 284 fewer than 2014 which used older land cover and a different landform methodology. Note: This layer is designed for use as a geoprocessing input layer and to support pop-ups in ArcGIS Online. Because of the large number of unique values in the image service, the legend cannot be used in a meaningful way. Use the World Ecological Land Units Map 2015 tiled map layer for mapping and visualization. These four component datasets represent the most accurate, current, globally comprehensive, and finest spatial and thematic resolution data available for each of the four inputs. Values for each of the four input layers are listed in the table below. BioclimateLandformsLithologyLand CoverArcticPlainsUndefinedBare AreaCold DryHillsUnconsolidated SedimentSparse VegetationCold Semi-DryMountainsCarbonate Sedimentary RockGrassland, Shrub, or ScrubCold Moist Mixed Sedimentary RockMostly CroplandCold Wet Non-Carbonate Sedimentary RockMostly Needleleaf/Evergreen ForestCool Dry EvaporiteMostly Deciduous ForestCool Semi-Dry PyroclasticsSwampy or Often FloodedCool Moist Metamorphic RockArtificial or Urban AreaCool Wet Acidic VolcanicsSurface WaterHot Dry Acidic PlutonicsUndefinedHot Semi-Dry Non-Acidic Volcanics Hot Moist Non-Acidic Plutonics Hot Wet Warm Dry Warm Semi-Dry Warm Moist Warm Wet This layer is suitable for analysis and can be used in ArcGIS Online to support pop-ups. It can be used in ArcGIS Desktop. Because of the large number of unique values in the image service it cannot be symbolized and displays as an all black layer. To use in pop-ups set the transparency to 100% and configure the pop-up. The pop-up from this layer can be combined with the World Ecological Land Units Map. Layers providing access to the four input layers used to create this map see the following links: World BioclimatesWorld Landforms Improved Hammond MethodWorld LithologyWorld Land Cover ESA 2010 The ecophysiographic facets layer is available here and a layer summarizing the local diversity of the ecophysiographic facets is available here. A service is available to the data tables associated with this and other global layers. These data table services can be used by developers to create custom applications. For more information see the World Ecophysiographic Tables. The layer was created by the USGS and Esri in 2015. For more information see the publication:Sayre and others. 2014. A New Map of Global Ecological Land Units — An Ecophysiographic Stratification Approach. Washington, DC: Association of American Geographers. 46 pages. Dataset SummaryAnalysis: Restricted single source analysis. Maximum size of analysis is 16,000 x 16,000 pixels. What can you do with this layer?This layer is suitable for analysis and can be used in ArcGIS Online to support pop-ups. It can be used in ArcGIS Desktop. Because of the large number of unique values in the image service it can not be symbolized and displays as an all white layer. To use in pop-ups set the transparency to 100% and configure the pop-up. Restricted single source analysis means this layer has size constraints for analysis and it is not recommended for use with other layers in multisource analysis. This layer has query, identify, and export image services available. This layer is restricted to a maximum area of 16,000 x 16,000 pixels - an area 4,000 kilometers on a side or an area approximately the size of Europe. This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks. The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started see the Living Atlas Discussion Group. The Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.

Note: 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 beginning 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.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCounty 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 LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon) Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_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 BureauCENSUS_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 SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.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 countyCENSUS_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 support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts,

Unique values and counts of metadata subject fields.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

Related 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
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 (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

This alley feature class represents current street centerline lines in the City of Los Angeles. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Alley Centerline layer was created in geographical information systems (GIS) software to display alley centerlines. The purpose of the layer is to show the location of the alleys on map products and web mapping applications. The Bureau of Street Services tracks the location of existing alleys that they maintain. Alleys are not dedicated streets, and the use of the road is determined by the Planning Department. Street features in the Street Centerline layer are dedicated. In the Alley Centerline layer, there is no naming convention stored in the corresponding records to identify the names of the alleys. Department of Transportation, LADOT, is working on a naming standard. Note there are Alleys features in the Street Centerline layer are Named Alleys. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley line feature in the Street Centerline layer, the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name for the alley stored in the STNAME and STSFX fields. Currently the Alley line features in Alley layer do not split the street centerline layer features where they intersect, so there is no intersection point created or maintained in the Intersection layer.List of Fields:ZIP_R: Zip code right.ID: A unique numeric identifier of the line feature. This unique identifier is no longer used and ASSETID is used now instead.AL_DESIG: This value is currently not being used.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.SHAPE: Feature geometry.USER_ID: The name of the user carrying out the edits.CRTN_DT: Creation date of the polygon feature.LST_MODF_DT: Last modification date of the feature.ZIP_L: Zip code left.STNUM: Street identification number. This field is currently not being used.OBJECTID: Internal feature number.LINE_ID: This value is currently not being edited. This used to be an automatically assigned unique ID of the alley centerline line segments.ASSETID: User-defined feature autonumber.AL_ID: This value is the ID of the alley as assigned by Bureau of Street Services, Department of Public Works. This is unique for each alley, but not unique for each alley line segment. This field has not been updated.SHAPE.LEN

PDF Map of FCC Form 477 provider reported maximum download speeds by census block for January - June 2020. This map seeks to highlight areas that are undeserved by terrestrial broadband (fiber/cable/dsl on the ground), with "underserved" defined as down/up speeds less than 25/3 Mbps.These data represent a static snapshot of provider reported coverage between January 2020 and June 2020. Maps also depict the locations of federally recognized tribes, Alaskan communities, ANCSA and borough boundaries.Broadband coverage is represented using provider reported speeds under the FCC Form 477 the amalgamated broadband speed measurement category based on Form 477 "All Terrestrial Broadband" as a proxy for coverage. This field is unique to the NBAM platform. These maps do not include satellite internet coverage (and may not include microwave coverage through the TERRA network for all connected areas).This map was produced by DCRA using data provided by NTIA through the NBAM platform as part of a joint data sharing agreement undertaken in the year 2021. Maps were produced using the feature layer "NBAM Data by Census Geography v4": https://maps.ntia.gov/arcgis/home/item.html?id=8068e420210542ba8d2b02c1c971fb20Coverage is symbolized using the following legend:No data avalible or no terrestrial coverage: Grey or transparent< 10 Mbps Maximum Reported Download: Red10-25 Mbps Maximum Reported Download: Orange25-50 Mbps Maximum Reported Download: Yellow50-100 Mbps Maximum Reported Download: Light Blue100-1000 Mbps Maximum Reported Download: Dark Blue_Description from layer "NBAM Data by Census Geography v4":This layer is a composite of seven sublayers with adjacent scale ranges: States, Counties, Census Tracts, Census Block Groups, Census Blocks, 100m Hexbins and 500m Hexbins. Each type of geometry contains demographic and internet usage data taken from the following sources: US Census Bureau 2010 Census data (2010) USDA Non-Rural Areas (2013) FCC Form 477 Fixed Broadband Deployment Data (Jan - Jun 2020) Ookla Consumer-Initiated Fixed Wi-Fi Speed Test Results (Jan - Jun 2020) FCC Population, Housing Unit, and Household Estimates (2019). Note that these are derived from Census and other data. BroadbandNow Average Minimum Terrestrial Broadband Plan Prices (2020) M-Lab (Jan - Jun 2020)Some data values are unique to the NBAM platform: US Census and USDA Rurality values. For units larger than blocks, block count (urban/rural) was used to determine this. Some tracts and block groups have an equal number of urban and rural blocks—so a new coded value was introduced: S (split). All blocks are either U or R, while tracts and block groups can be U, R, or S. Amalgamated broadband speed measurement categories based on Form 477. These include: 99: All Terrestrial Broadband Plus Satellite 98: All Terrestrial Broadband 97: Cable Modem 96: DSL 95: All Other (Electric Power Line, Other Copper Wireline, Other) Computed differences between FCC Form 477 and Ookla values for each area. These are reflected by six fields containing the difference of maximum, median, and minimum upload and download speed values.The FCC Speed Values method is applied to all speeds from all data sources within the custom-configured Omnibus service pop-up. This includes: Geography: State, County, Tract, Block Group, Block, Hex Bins geographies Data source: all data within the Omnibus, i.e. FCC, Ookla, M-Lab Representation: comparison tables and single speed values

This physical structures points feature class represents current wastewater information in the City of Los Angeles. The maintenance hole structure is used to provide access to the sewer from the surface. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the sanitary sewer system using a geometric network model, to ensure that its sewers reflect current ground conditions. The sanitary sewer system, pump plants, wyes, maintenance holes, and other structures represent the sewer infrastructure in the City of Los Angeles. Wye and sewer information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the wastewater Physical_structure is entered into attributes. Principal attributes include:JUNCTION_SUBTYPE: junction subtype is the principal field that describes various types of points as either Diversion Structure, Drop or Drop Trap, Flush, Junction Chamber, Junction Structure, Maintenance, Offset, Other Structure, Siphon, Special Shallow, Special Structure, Terminal, Transition, Trap, Valve Vault, Weir. For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater Physical Structures points layer was created in geographical information systems (GIS) software to display the location of wastewater structures. The structures points layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a points feature class and attribute data for the features. The points are entered manually based on wastewater sewer maps and BOE standard plans, and information about the points is entered into attributes. The physical structures points data layer differs from non-structures points data layer, such that physical structures points are maintenance holes. Reference the JUNCTION_SUBTYPE and MH_TYPE field for the type of structure. The STRUCTURE_ID field value is the unique ID. The wastewater structures points are inherited from a sewer spatial database originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. Structures information should only be added to the Wastewater Structures layer if documentation exists, such as a wastewater map approved by the City Engineer. Sewers plans and specifications proposed under private development are reviewed and approved by Bureau of Engineering. The Department of Public Works, Bureau of Engineering's, Brown Book (current as of 2010) outlines standard specifications for public works construction. For more information on sewer materials and structures, look at the Bureau of Engineering Manual, Part F, Sewer Design section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf. For more information on maintenance holes, a copy can be viewed at http://boemaps.eng.ci.la.ca.us/reports/pdf/s140-0_std_pl.pdf.List of Fields:SERVICEID: User-defined unique feature number that is automatically generated.OBJECTID: Internal feature number.FACILITY_NO: This field is currently not being edited.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • W - West LA Engineering District. • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District.CNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/index.cfm, click Council Districts layer name, under Boundaries layer group.CRTN_DT: Creation date of the point feature.MDIST: This value is the maintenance district identifier. Bureau of Sanitation needs to provide BOE with updated definitions. This field is currently not being edited.LAT: The value is the latitude coordinate of the point.USER_ID: The name of the user carrying out the edits of the structure data.LON: The value is the longitude coordinate of the point.NAME: This field is currently not being edited.VDATUM: This is the year of the standard plan, which contains the information the user enters into pipe data.MHMATERIAL: The value is the material that the structure is made from. This information is not specified on the standard plan. Values: • UNK - Unknown. • RCP - Reinforced Concrete Pipe. • CSP - Corrugated Steel Pipe. • CIPC - Cast in place concrete. • C - Concrete. • BRK - Brick. • PRC - Precast Reinforced Concrete. • B - Brick. • CON - Concrete. • VCP - Vitrified Clay Pipe. • O - Other. • P - Plastic.BLKNO: The value is the block number of the street on which the physical structure is located.STREET2: The value is the cross street name on which the physical structure hole is located, if applicable.COVERDIAM: The value diameter of the physical structure cover expressed in feet.BARRELDIAM: The value diameter of the inside of the physical structure expressed in feet.STATUS: This value is the active or inactive status of the structure. Values: • ABAN - Proposed Inactive. • PROP_ACT - Proposed Active. • INACT - Inactive. • ACT - Active. • ABAN - Abandoned.SEQ: The value is the sequence number of the maintenance hole.SHAPE: Feature geometry.STREET1: The value is the street name on which the physical structure is located.MH_BASE: The value is the non-structure base, used by Bureau of Sanitation to describe the direction of flow at the intersection of a pipe and a non-structure. Values: • F - F. • B - B. • G - G. • H - H. • Q - Q.MH_TYPE: The value signifies the maintenance hole type or other structure type. Values: • DMH - Drop Maintenance Hole. • CFS - Confluence Structure. • DMT - Drop trap Maintenance Hole. • ABN - Abandoned. • BPS - Bypass Structure. • DI - Diversion Structure. • SH - Shallow Maintenance Hole. • OMH - Offset Maintenance Hole. • RV - Relief Valve. • SIP - Siphon. • VV - Valve vault. • LH - Lamp Hole. • FL - Flush Station. • GV - Gate Valve. • TRP - Trap maintenance hole. This type of structure is used to prevent sewer gases from flowing upstream in the sewer line. • HD - Transition. • TRS - Transition structure. • FT - Flush Tank. • WMH - Weir maintenance hole. This type of structure is used to gauge sewer flows. Automatic recording devices may be installed for flow measurement. • INA - Inactive. • MH - Maintenance Hole. • OTH - Other structure. • FS - Flush Station. • WW - Wet well. • JT - Junction Chamber Trap. • JC - Junction Chamber. • PMH - Pressure Maintenance Hole. • PS - Pump Station. • FMH - Flush Maintenance Hole. • TMH - Terminal maintenance hole. • GS - Gauging Structure. • JS - Junction Structure.LID_ELEV: The value is the lid elevation of the structure, in decimal feet.BASIN: The value is basin number.OWNER: This value is the agency or municipality that constructed the physical structure. Values: • CTY - City of LA. • FED - Federal Facilities. • OUTLA - Adjoining cities. • COSA - LA County Sanitation. • PVT - Private.COMMENTS: This attribute contains comments of structures and structure status.MH_DEPTH: The value is the depth of the physical structure expressed in decimal feet.JUNCTION_SUBTYPE: The value is the type of physical structure. Values: • 1 - Maintenance. • 4 - Offset. • 15 - Valve Vault. • 6 - Diversion Structure. • 8 - Flush. • 9 - Junction Chamber. • 5 - Trap. • 7 - Special Shallow. • 3 - Terminal. • 10 - Siphon. • 13 - Junction Structure. • 16 - Transition. • 2 - Drop or Drop Trap. • 11 - Weir. • 12 - Special Structure. • 14 - Other Structure.LAST_UPDATE: Date of last update of the point feature.YEAR_INST: This is the year of the structure installation.ROUTE: The value is the sewer maintenance route number.ADDRESS: This field is currently not being edited.ENABLED: Internal feature number.STRUCTURE_ID: The value is the ID of the structure. It could be either the value from the UP_STRUCT or DN_STRUCT fields. This point is the structure that may be a maintenance hole, junction, siphon, etc. The field STRUCTURE_ID is a key attribute to relate the physical structures feature class to the UP_MH field or the DN_MH field in pipe lines feature class.ASSETID: User-defined unique feature number that is automatically generated.

PDF Map of FCC Form 477 provider reported maximum download speeds by census block for January - June 2020. This map seeks to highlight areas that are undeserved by terrestrial broadband (fiber/cable/dsl on the ground), with "underserved" defined as down/up speeds less than 25/3 Mbps.These data represent a static snapshot of provider reported coverage between January 2020 and June 2020. Maps also depict the locations of federally recognized tribes, Alaskan communities, ANCSA and borough boundaries.Broadband coverage is represented using provider reported speeds under the FCC Form 477 the amalgamated broadband speed measurement category based on Form 477 "All Terrestrial Broadband" as a proxy for coverage. This field is unique to the NBAM platform. These maps do not include satellite internet coverage (and may not include microwave coverage through the TERRA network for all connected areas).This map was produced by DCRA using data provided by NTIA through the NBAM platform as part of a joint data sharing agreement undertaken in the year 2021. Maps were produced using the feature layer "NBAM Data by Census Geography v4": https://maps.ntia.gov/arcgis/home/item.html?id=8068e420210542ba8d2b02c1c971fb20Coverage is symbolized using the following legend:No data avalible or no terrestrial coverage: Grey or transparent< 10 Mbps Maximum Reported Download: Red10-25 Mbps Maximum Reported Download: Orange25-50 Mbps Maximum Reported Download: Yellow50-100 Mbps Maximum Reported Download: Light Blue100-1000 Mbps Maximum Reported Download: Dark Blue_Description from layer "NBAM Data by Census Geography v4":This layer is a composite of seven sublayers with adjacent scale ranges: States, Counties, Census Tracts, Census Block Groups, Census Blocks, 100m Hexbins and 500m Hexbins. Each type of geometry contains demographic and internet usage data taken from the following sources: US Census Bureau 2010 Census data (2010) USDA Non-Rural Areas (2013) FCC Form 477 Fixed Broadband Deployment Data (Jan - Jun 2020) Ookla Consumer-Initiated Fixed Wi-Fi Speed Test Results (Jan - Jun 2020) FCC Population, Housing Unit, and Household Estimates (2019). Note that these are derived from Census and other data. BroadbandNow Average Minimum Terrestrial Broadband Plan Prices (2020) M-Lab (Jan - Jun 2020)Some data values are unique to the NBAM platform: US Census and USDA Rurality values. For units larger than blocks, block count (urban/rural) was used to determine this. Some tracts and block groups have an equal number of urban and rural blocks—so a new coded value was introduced: S (split). All blocks are either U or R, while tracts and block groups can be U, R, or S. Amalgamated broadband speed measurement categories based on Form 477. These include: 99: All Terrestrial Broadband Plus Satellite 98: All Terrestrial Broadband 97: Cable Modem 96: DSL 95: All Other (Electric Power Line, Other Copper Wireline, Other) Computed differences between FCC Form 477 and Ookla values for each area. These are reflected by six fields containing the difference of maximum, median, and minimum upload and download speed values.The FCC Speed Values method is applied to all speeds from all data sources within the custom-configured Omnibus service pop-up. This includes: Geography: State, County, Tract, Block Group, Block, Hex Bins geographies Data source: all data within the Omnibus, i.e. FCC, Ookla, M-Lab Representation: comparison tables and single speed values

PDF Map of FCC Form 477 provider reported maximum download speeds by census block for January - June 2020. This map seeks to highlight areas that are undeserved by terrestrial broadband (fiber/cable/dsl on the ground), with "underserved" defined as down/up speeds less than 25/3 Mbps.These data represent a static snapshot of provider reported coverage between January 2020 and June 2020. Maps also depict the locations of federally recognized tribes, Alaskan communities, ANCSA and borough boundaries.Broadband coverage is represented using provider reported speeds under the FCC Form 477 the amalgamated broadband speed measurement category based on Form 477 "All Terrestrial Broadband" as a proxy for coverage. This field is unique to the NBAM platform. These maps do not include satellite internet coverage (and may not include microwave coverage through the TERRA network for all connected areas).This map was produced by DCRA using data provided by NTIA through the NBAM platform as part of a joint data sharing agreement undertaken in the year 2021. Maps were produced using the feature layer "NBAM Data by Census Geography v4": https://maps.ntia.gov/arcgis/home/item.html?id=8068e420210542ba8d2b02c1c971fb20Coverage is symbolized using the following legend:No data avalible or no terrestrial coverage: Grey or transparent< 10 Mbps Maximum Reported Download: Red10-25 Mbps Maximum Reported Download: Orange25-50 Mbps Maximum Reported Download: Yellow50-100 Mbps Maximum Reported Download: Light Blue100-1000 Mbps Maximum Reported Download: Dark Blue_Description from layer "NBAM Data by Census Geography v4":This layer is a composite of seven sublayers with adjacent scale ranges: States, Counties, Census Tracts, Census Block Groups, Census Blocks, 100m Hexbins and 500m Hexbins. Each type of geometry contains demographic and internet usage data taken from the following sources: US Census Bureau 2010 Census data (2010) USDA Non-Rural Areas (2013) FCC Form 477 Fixed Broadband Deployment Data (Jan - Jun 2020) Ookla Consumer-Initiated Fixed Wi-Fi Speed Test Results (Jan - Jun 2020) FCC Population, Housing Unit, and Household Estimates (2019). Note that these are derived from Census and other data. BroadbandNow Average Minimum Terrestrial Broadband Plan Prices (2020) M-Lab (Jan - Jun 2020)Some data values are unique to the NBAM platform: US Census and USDA Rurality values. For units larger than blocks, block count (urban/rural) was used to determine this. Some tracts and block groups have an equal number of urban and rural blocks—so a new coded value was introduced: S (split). All blocks are either U or R, while tracts and block groups can be U, R, or S. Amalgamated broadband speed measurement categories based on Form 477. These include: 99: All Terrestrial Broadband Plus Satellite 98: All Terrestrial Broadband 97: Cable Modem 96: DSL 95: All Other (Electric Power Line, Other Copper Wireline, Other) Computed differences between FCC Form 477 and Ookla values for each area. These are reflected by six fields containing the difference of maximum, median, and minimum upload and download speed values.The FCC Speed Values method is applied to all speeds from all data sources within the custom-configured Omnibus service pop-up. This includes: Geography: State, County, Tract, Block Group, Block, Hex Bins geographies Data source: all data within the Omnibus, i.e. FCC, Ookla, M-Lab Representation: comparison tables and single speed values

Documented March 19, 2023

!!NEW!!!

GeoDAR reservoirs were registered to the drainage network! Please see the auxiliary data "GeoDAR-TopoCat" at https://zenodo.org/records/7750736. "GeoDAR-TopoCat" contains the drainage topology (reaches and upstream/downstream relationships) and catchment boundary for each reservoir in GeoDAR, based on the algorithm used for Lake-TopoCat (doi:10.5194/essd-15-3483-2023).

Documented April 1, 2022

Citation

Wang, J., Walter, B. A., Yao, F., Song, C., Ding, M., Maroof, A. S., Zhu, J., Fan, C., McAlister, J. M., Sikder, M. S., Sheng, Y., Allen, G. H., Crétaux, J.-F., and Wada, Y.: GeoDAR: georeferenced global dams and reservoirs database for bridging attributes and geolocations. Earth System Science Data, 14, 1869–1899, 2022, https://doi.org/10.5194/essd-14-1869-2022.

Please cite the reference above (which was fully peer-reviewed), NOT the preprint version. Thank you.

Contact

Dr. Jida Wang, jidawang@ksu.edu, gdbruins@ucla.edu

Data description and components

Data folder “GeoDAR_v10_v11” (.zip) contains two consecutive, peer-reviewed versions (v1.0 and v1.1) of the Georeferenced global Dams And Reservoirs (GeoDAR) dataset:

• GeoDAR_v10_dams (in both shapefile format and the comma-separated values (csv) format): GeoDAR version 1.0, including 22,560 dam points georeferenced based on the World Register of Dams (WRD), the International Commission on Large Dams (ICOLD; https://www.icold-cigb.org; last access on March 13th, 2019).
• GeoDAR_v11_dams (in both shapefile and csv): GeoDAR version 1.1 dam points, including 24,783 dams which harmonized GeoDAR_v10_dams and the Global Reservoir and Dam Database (GRanD) v1.3 (Lehner et al., 2011).
• GeoDAR_v11_reservoirs (in shapefile): GeoDAR version 1.1 reservoirs, including 21,515 reservoir polygons retrieved by associating GeoDAR_v11_dams with GRanD v1.3 reservoirs, HydroLAKES v1.0 (Messager et al., 2016), and the UCLA Circa 2015 Lake Inventory (Sheng et al., 2016). The reservoir retrieval follows a one-to-one relationship between dams and reservoirs.

As by-products of GeoDAR harmonization, folder “GeoDAR_v10_v11” also contains:

• GRanD_v13_issues.csv: This file contains the original records of all 7,320 dam points in GRanD v1.3, with 94 of them marked by our identified issues and suggested corrections. These 94 records are placed at the beginning of this table. They include 89 records showing possible georeferencing and/or attribute errors, and another 5 records documented as subsumed or replaced. Our added fields start from column BG and include:
  • “Issue”: main issue(s) of this record
  • “Description”: more detailed explanation of the issue
  • “Lat_corrected”: suggested correction for latitude (if any) in decimal degree
  • “Lon_corrected”: suggested correction for longitude (if any) in decimal degree
  • “Correction_source”: correction source(s)
  • “Harmonized”: whether this GRanD dam was harmonized in GeoDAR v1.1 and the reason.
• Wada_et_al_2017_harmonized.csv: This csv file contains the original records of all 139 georeferenced large dams/reservoirs in Wada et al. (2017; doi:10.1007/s10712-016-9399-6), with our revised storage capacities and spatial coordinates for data harmonization. Our added fields start from column E and include:
  • Revised_capacity_km3: Our revised reservoir storage capacity in cubic kilometers used for harmonization
  • Revised_lat: Revised latitude in decimal degree
  • Revised_lon: Revised longitude in decimal degree
  • Verification_notes: Description of the issues, verification sources, and other information used for harmonization.

Attribute description

PDF Map of FCC Form 477 provider reported maximum download speeds by census block for January - June 2020. This map seeks to highlight areas that are undeserved by terrestrial broadband (fiber/cable/dsl on the ground), with "underserved" defined as down/up speeds less than 25/3 Mbps.These data represent a static snapshot of provider reported coverage between January 2020 and June 2020. Maps also depict the locations of federally recognized tribes, Alaskan communities, ANCSA and borough boundaries.Broadband coverage is represented using provider reported speeds under the FCC Form 477 the amalgamated broadband speed measurement category based on Form 477 "All Terrestrial Broadband" as a proxy for coverage. This field is unique to the NBAM platform. These maps do not include satellite internet coverage (and may not include microwave coverage through the TERRA network for all connected areas).This map was produced by DCRA using data provided by NTIA through the NBAM platform as part of a joint data sharing agreement undertaken in the year 2021. Maps were produced using the feature layer "NBAM Data by Census Geography v4": https://maps.ntia.gov/arcgis/home/item.html?id=8068e420210542ba8d2b02c1c971fb20Coverage is symbolized using the following legend:No data avalible or no terrestrial coverage: Grey or transparent< 10 Mbps Maximum Reported Download: Red10-25 Mbps Maximum Reported Download: Orange25-50 Mbps Maximum Reported Download: Yellow50-100 Mbps Maximum Reported Download: Light Blue100-1000 Mbps Maximum Reported Download: Dark Blue_Description from layer "NBAM Data by Census Geography v4":This layer is a composite of seven sublayers with adjacent scale ranges: States, Counties, Census Tracts, Census Block Groups, Census Blocks, 100m Hexbins and 500m Hexbins. Each type of geometry contains demographic and internet usage data taken from the following sources: US Census Bureau 2010 Census data (2010) USDA Non-Rural Areas (2013) FCC Form 477 Fixed Broadband Deployment Data (Jan - Jun 2020) Ookla Consumer-Initiated Fixed Wi-Fi Speed Test Results (Jan - Jun 2020) FCC Population, Housing Unit, and Household Estimates (2019). Note that these are derived from Census and other data. BroadbandNow Average Minimum Terrestrial Broadband Plan Prices (2020) M-Lab (Jan - Jun 2020)Some data values are unique to the NBAM platform: US Census and USDA Rurality values. For units larger than blocks, block count (urban/rural) was used to determine this. Some tracts and block groups have an equal number of urban and rural blocks—so a new coded value was introduced: S (split). All blocks are either U or R, while tracts and block groups can be U, R, or S. Amalgamated broadband speed measurement categories based on Form 477. These include: 99: All Terrestrial Broadband Plus Satellite 98: All Terrestrial Broadband 97: Cable Modem 96: DSL 95: All Other (Electric Power Line, Other Copper Wireline, Other) Computed differences between FCC Form 477 and Ookla values for each area. These are reflected by six fields containing the difference of maximum, median, and minimum upload and download speed values.The FCC Speed Values method is applied to all speeds from all data sources within the custom-configured Omnibus service pop-up. This includes: Geography: State, County, Tract, Block Group, Block, Hex Bins geographies Data source: all data within the Omnibus, i.e. FCC, Ookla, M-Lab Representation: comparison tables and single speed values

Note: 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 beginning 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

County 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 layer removes the coastal buffer 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
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
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, gis@state.ca.gov

Field and Abbreviation Definitions

• 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_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 support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Unique values and counts of metadata subject fields.

Twelve maps of continental Europe indicating the protected nature area status in 2019 according to Natura 2000 and the International Union for Conservation of Nature (IUCN). The IUCN status was extracted from crowdsourced data obtained from OpenStreetMap through geofabrik.de.

This dataset contains:

• 3 raster maps representing Natura 2000 protection status (A, B and C), named Natura2000_[status].tif
• 8 raster maps representing OSM-derived IUCN protection status (1a, 1b, 2, 3, 4, 5, 6, and 'other'), named OSM_IUCN_[status].tif
• 1 aggregated map (adm_protected.area_natura2000.osm_p_30m_0..0cm_2019..2021_eumap_epsg3035_v0.1) where each of the 11 protection statuses, as well as pixels where multiple statuses apply, are assigned a unique value. This map can also be accessed interactively at maps.opendatascience.eu.

All files are provided as Cloud Optimized GeoTIFFs and projected in the Coordinate Reference System ETRS89 / LAEA Europe (= EPSG code 3035). Styling files for the aggregated raster are provided in both SLD and QML format.