Feature layer generated from running the Overlay layers solution.

GIS layer composed of Lorain County Township, Tract and Original Lot numbers within each township. Not all townships have Tracts and/or Original Lots. *Each layer has a different scale visibility. You may have to zoom in to a certain extent for the layer to turn on.

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

The ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) Project Package includes all of the layers that are in the NTIA Permitting and Environmental Information Application as well as the APPEIT Tool which will allow users to input a project area and determine what layers from the application overlap with it. An overview of the project package and the APPEIT tool is provided below.

User instructions on how to use the tool are available here. A video explaining how to use the Project Package is also available here.

Project Package Overview

This map package includes all of the layers from the NTIA Permitting and Environmental Information Application. The layers included are all feature services from various Federal and State agencies. The map package was created with ArcGIS Pro 3.4.0. The map package was created to allow users easy access to all feature services including symbology. The map package will allow users to avoid downloading datasets individually and easily incorporate into their own GIS system. The map package includes three maps.

1. Permitting and Environmental Information Application Layers for GIS Analysis - This map includes all of the map tabs shown in the application, except State Data which is provided in another tab. This map includes feature services that can be used for analysis with other project layers such as a route or project area.

2. Permitting and Environmental Information Application Layers – For Reference Only - This map includes layers that cannot be used for analysis since they are either imagery or tile layers.

3. State Data - Reference Only - This map includes all relevant state data that is shown in the application.

The NTIA Permitting and Environmental Information Application was created to help with your permitting planning and environmental review preparation efforts by providing access to multiple maps from publicly available sources, including federal review, permitting, and resource agencies. The application should be used for informational purposes only and is intended solely to assist users with preliminary identification of areas that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. Multiple maps are provided in the application which are created from public sources. This application does not have an exhaustive list of everything you need for permitting or environmental review for a project but is an initial starting point to see what might be required.

APPEIT Tool OverviewThe Department of Commerce’s National Telecommunications and Information Administration (NTIA) is providing the ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) to help federal broadband grant recipients and subgrantees identify permits and environmental factors as they plan routes for their broadband deployments. Identifying permit requirements early, initiating pre-application coordination with permitting agencies, and avoiding environmental impacts help drive successful infrastructure projects. NTIA’s public release of the APPEIT tool supports government-wide efforts to improve permitting and explore how online and digital technologies can promote efficient environmental reviews.

This Esri ArcGIS Pro tool is included in the map package and was created to support permitting, planning, and environmental review preparation efforts by providing access to data layers from publicly available sources, including federal review, permitting, and resource agencies. An SOP on how to use the tool is available here. For the full list of APPEIT layers, see Appendix Table 1 in the SOP. The tool is comprised of an ArcGIS Pro Project containing a custom ArcGIS Toolbox tool, linked web map shared by the NTIA’s National Broadband Map (NBAM), a report template, and a Tasks item to guide users through using the tool. This ArcGIS Pro project and its contents (maps and data) are consolidated into this (.ppkx) project file.

To use APPEIT, users will input a project area boundary or project route line in a shapefile or feature class format. The tool will return as a CSV and PDF report that lists any federal layers from the ArcGIS Pro Permitting and Environmental Information Web Map that intersect the project. Users may only input a single project area or line at a time; multiple projects or project segments will need to be screened separately. For project route lines, users are required to specify a buffer distance. The buffer distance that is used for broadband projects should be determined by the area of anticipated impact and should generally not exceed 500 feet. For example, the State of Maryland recommends a 100-foot buffer for broadband permitting. The tool restricts buffers to two miles to ensure relevant results.

Disclaimer

This document is intended solely to assist federal broadband grant recipients and subgrantees in better understanding Infrastructure Investment and Jobs Act (IIJA) broadband grant programs and the requirements set forth in the Notice of Funding Opportunity (NOFO) for this program. This document does not and is not intended to supersede, modify, or otherwise alter applicable statutory or regulatory requirements, the terms and conditions of the award, or the specific application requirements set forth in the NOFO. In all cases, statutory and regulatory mandates, the terms and conditions of the award, the requirements set forth in the NOFO, and follow-on policies and guidance, shall prevail over any inconsistencies contained in this document.

NTIA’s ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) should be used for informational purposes only and is intended solely to assist users with preliminary identification of broadband deployments that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements.

The tool is not an exhaustive or complete resource and does not and is not intended to substitute for, supersede, modify, or otherwise alter any applicable statutory or regulatory requirements, or the specific application requirements set forth in any NTIA NOFO, Terms and Conditions, or Special Award Condition. In all cases, statutory and regulatory mandates, and the requirements set forth in NTIA grant documents, shall prevail over any inconsistencies contained in these templates.

The tool relies on publicly available data available on the websites of other federal, state, local, and Tribal agencies, and in some instances, private organizations and research institutions. Layers identified with a double asterisk include information relevant to determining if an “extraordinary circumstance” may warrant more detailed environmental review when a categorical exclusion may otherwise apply. While NTIA continues to make amendments to its websites to comply with Section 508, NTIA cannot ensure Section 508 compliance of federal and non-federal websites or resources users may access from links on NTIA websites.

All data is presented “as is,” “as available” for informational purposes. NTIA does not warrant the accuracy, adequacy, or completeness of this information and expressly disclaims liability for any errors or omissions.

Please e-mail NTIAanalytics@ntia.gov with any questions.

Feature layer generated from running the Overlay layers solution.

Support layer for the following MPG Story Map: https://fws.maps.arcgis.com/apps/Cascade/index.html?appid=a99553093e5a45b183c18e8cf0762176Feature layer generated from running the Overlay layers solution.Get to know the Threatened Mazama Pocket Gopher! This storymap provides an interactive introduction to this furry and fossorial native species to the South Sound Prairies. https://fws.maps.arcgis.com/apps/MapSeries/index.html?appid=83b64cb7c194404fa5f0f024a5eab328To learn more about the Washington Office of the United Stated Fish and Wildlife Service (USFWS), please go to here: https://www.fws.gov/wafwo/index.cfm

Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.

Dataset Summary About this data: Feature layer contains all the U.S. postal codes at the 5-digit level for Rochester, NY. Created in January 2021. Updated April 2025. Data Dictionary: ZIP_CODE: The five digit zip code number for an area. PO_NAME: The name of the city that the zip code intersects (Rochester). STATE: The name of the state that the zip code intersects (NY). POP2023: The population of the zip code in the year 2023. SQMI: The size of the zip code in square miles. Source: This data comes from the City of Rochester.

Source:1 foot contours were generated for each production block from the final bare earth DEMs using ArcGIS software. Using ArcGIS software, the contours were validated for correct topology, including must not intersect, must not self intersect, and must not have dangles. Contours are then manually reviewed with the 3D breaklines to ensure complete coverage, correct coding, data integrity and that contours behave correctly around water bodies, water crossings, and elevated features such as overpasses. The contours are then clipped to individual tiles as creating one dataset for the entire project renders the feature class un-usable. Enclosed contours completely within building footprints were removed from the final contour dataset. Coordinate System:The data was developed based on a horizontal datum/projection of NAD83 (2011), State Plane Connecticut, U.S. Survey Feet and vertical datum of NAVD88 (GEOID18) Development:This vector tile package contains contour lines originally derived in the State Plane coordinate system. Prior to generating the tile service, individual contour blocks were merged into a single, seamless data layer to ensure consistency and completeness across the project area. This unified dataset served as the basis for creating the vector tile package. During the creation of the vector tile index, Web Mercator was used as the tiling reference to enable proper indexing and tile generation within ArcGIS Online. Please note that while the vector tile index references Web Mercator for mapping and display purposes, the contour line geometries are aligned with the original State Plane coordinate system, maintaining consistency with the source data used in production. This vector tile package contains contour lines originally derived in the State Plane coordinate system. Prior to generating the tile service, individual contour blocks were merged into a single, seamless data layer to ensure consistency and completeness across the project area. This unified dataset served as the basis for creating the vector tile package. During the creation of the vector tile index, Web Mercator was used as the tiling reference to enable proper indexing and tile generation within ArcGIS Online. Please note that while the vector tile index references Web Mercator for mapping and display purposes, but the contour lines were originally in the State Plane coordinate system Use Constraints:There are no formal use restrictions. However, users should be aware the conditions may have changed since the data was originally collected, and some areas may no longer accurately reflect current surface features. This data should not be used for critical decision-making without a full understanding of their limitations.

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.

berkeley 10

Feature layer generated from running the Overlay layers solution.

Feature layer generated from running the Overlay layers solution.

berkeley 500

Feature Service generated from running the Overlay layers solution.

dorchester business 100

Components Unknown: A connector that staff cannot define because the structure is buried, paved over, flooded, etc. The location is often inferred. Unknown is for use in the field.Intersection: A connector point whose location is inferred as the convergence between one or more stormwater conveyance structures (e.g. a pipe) where there is believed to be no catch basin or other structure that serves as a connector.

dorchester 500

This intersection points feature class represents current intersections in the City of Los Angeles. Few intersection points, named pseudo nodes, are used to split the street centerline at a point that is not a true intersection at the ground level. 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.Intersection layer was created in geographical information systems (GIS) software to display intersection points. Intersection points are placed where street line features join or cross each other and where freeway off- and on-ramp line features join street line features. The intersection points layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The intersection points relates to the intersection attribute table, which contains data describing the limits of the street segment, by the CL_NODE_ID field. The layer shows the location of the intersection points on map products and web mapping applications, and the Department of Transportation, LADOT, uses the intersection points in their GIS system. The intersection attributes are used in the Intersection search function on BOE's web mapping application NavigateLA. The intersection spatial data and related attribute data are maintained in the Intersection layer using Street Centerline Editing application. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. List of Fields:Y: This field captures the georeferenced location along the vertical plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, Y = in the record of a point, while the X = .CL_NODE_ID: This field value is entered as new point features are added to the edit layer, during Street Centerline application editing process. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline spatial data layer, then the intersections point spatial data layer, and then the intersections point attribute data during the creation of new intersection points. Each intersection identification number is a unique value. The value relates to the street centerline layer attributes, to the INT_ID_FROM and INT_ID_TO fields. One or more street centerline features intersect the intersection point feature. For example, if a street centerline segment ends at a cul-de-sac, then the point feature intersects only one street centerline segment.X: This field captures the georeferenced location along the horizontal plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, X = in the record of a point, while the Y = .ASSETID: User-defined feature autonumber.USER_ID: The name of the user carrying out the edits.SHAPE: Feature geometry.LST_MODF_DT: Last modification date of the polygon feature.LAT: This field captures the Latitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.OBJECTID: Internal feature number.CRTN_DT: Creation date of the polygon feature.TYPE: This field captures a value for intersection point features that are psuedo nodes or outside of the City. A pseudo node, or point, does not signify a true intersection of two or more different street centerline features. The point is there to split the line feature into two segments. A pseudo node may be needed if for example, the Bureau of Street Services (BSS) has assigned different SECT_ID values for those segments. Values: • S - Feature is a pseudo node and not a true intersection. • null - Feature is an intersection point. • O - Intersection point is outside of the City of LA boundary.LON: This field captures the Longitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.