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.

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

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 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.

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

This feature class consists of approximately 505,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS).Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides dissolved route segmentation (i.e. routes are not segmented when they intersect other routes), thus rendering one table record per route. In cases where routes are noncontiguous (e.g. a valid physical gap exists), multi-part geometry is created. The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other. Routes built in the prime and non-prime directions are included. Each road centerline record has a master route record assigned. This feature class is best suited for labeling roadways when overlap reference is needed.Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Purpose: This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located.

This dataset is a collection of regional boundary shapefiles, not elsewhere provided, used as spatial overlays to derive spatial summary statistics of various hazard, climate and other ecological raster data. The collection informed the assessment of freshwater and terrestrial natural environments as part of the National Climate Risk Assessment (NCRA). The shapefiles are derived from the intersection of publicly available 3rd party input data such as NCRA region boundaries, NCRA Hazard grids, Geofabric Level 2 Basins and Geofabric Network Streamlines.

The shapefiles (not elsewhere provided) in this collection include: NCRA Regions x Aggregate Ecosystem Groups 5km NCRA Hazard cells intersecting Geofabric Perennial Streams x Geofabric Level Basin 5km NCRA Hazard cells intersecting Geofabric Non- Perennial Streams x Geofabric Level Basin

All layers are ESRI shapefiles in the GCS WGS 1984 (EPSG 4326) Lineage: The input data used to derive the Regional Boundary shapefiles are:

1. NCRA Regions
2. A polygonised representation of NCRA Hazard raster data supplied by the Australian Climate Service (ACS)
3. Level 2 drainage basins from the Australian Hydrological Geospatial Fabric (AHGF) v3
4. Network Streams from the Australian Hydrological Geospatial Fabric (AHGF) v3
5. Aggregate Ecosystem Groups (AEGs) derived from National Vegetation Information System (NVIS) data

All processing was carried out using the Overlay Tools available in ArcGIS Desktop 10.8 with inputs reprojected to WGS84 before intersecting.

DERIVED Region Boundaries

1. NCRA Regions x Aggregate Ecosystem Groups: NCRA Regions were combined with the polygonised AEGs using ArcGIS Intersect tool output shapefile - NCRA_x_AEG_regions_WGS84.shp

2. 5km NCRA Hazard cells intersecting Geofabric Perennial Streams x Geofabric Level Basin: Hazard cell polygons were selected based on their spatial intersection with Geofabric Network Streams where the Perennial attribute is "Perennial". The selected cells were then combined with the Geofabric Level 2 Basins using ArcGIS Intersect tool. output shapefile - Perennial_x_GeofabricLevel2Basins_WGS84_singleparts2.shp

3. 5km NCRA Hazard cells intersecting Geofabric Non-Perennial Streams x Geofabric Level Basin: Hazard cell polygons were selected based on their spatial intersection with Geofabric Network Streams where the Perennial attribute is "Non Perennial". The selected cells were then combined with the Geofabric Level 2 Basins using ArcGIS Intersect tool. output shapefile - NonPerennial_x_GeofabricLevel2Basins_WGS84_singleparts2.shp

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.

Contours are lines of equal elevation. This is a contour feature layer for the state of Connecticut derived from the index contour in the 1' contour data set. All closed polygons less than 35' length have been deleted to improve loading performance. This data set is derived from the 2023 Lidar with15 to 20 points per meter squared.Source:1 foot contours were generated for each production block from the final bare earth DEMs using ArcGIS software. Contours are labeled as intermediate or index with index contours set to every 10th interval. 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)Contours were cut by Town then merged into COGsGeographic ExtentCoverage: State of Connecticut ClassificationsSensitivity: PublicUsage: Public UseQuality: High QualityKnown Quality Issues: None known, but subject to standard limitations of third-party commercial data CurrencyCreated: 2023Update Frequency: Per FlightLast Updated: August 2023

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.

For a city, street blocks are a very common way in which to organize and relate work (e.g. 'I need to fix a pothole on the 1600 Block of Pennsylvania Ave'). Although driveways or alleys may intersect streets, this representation requires that the segment remain unbroken. Road types include streets. Previously Called Street Segments. Note that there are no from/to address fields. We will not be maintaining them in our data. There also will be no generating a 'streetname' list.For more information please visit DDOT's wiki page.

Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510.

According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.

Contours are lines of equal elevation. This is a contour feature layer for the state of Connecticut derived from the index contour in the 1' contour data set. All closed polygons less than 35' length have been deleted to improve loading performance. This data set is derived from the 2023 Lidar with15 to 20 points per meter squared.Source:1 foot contours were generated for each production block from the final bare earth DEMs using ArcGIS software. Contours are labeled as intermediate or index with index contours set to every 10th interval. 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)Contours were cut by Town then merged into COGsGeographic ExtentCoverage: State of Connecticut ClassificationsSensitivity: PublicUsage: Public UseQuality: High QualityKnown Quality Issues: None known, but subject to standard limitations of third-party commercial data CurrencyCreated: 2023Update Frequency: Per FlightLast Updated: August 2023

As part of the basemap data layers, the street centerline map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, network analysis, geocoding, and presentation output).This dataset is designed to represent and locate the street centerlines in Lexington-Fayette County. The street centerlines are broken down into line segments that run from intersection to intersect and include street maintance, ownership, address ranges, and name information. The centerlines are updates through a variety of methods. Most commonly new streets are added from georeferenced plats, but corrections are alwo made by GPS collection and referencing to aerial photos.The data is in ESRI feature class format, but can be exported to any number of supported formats, including shapefile and dxf. The native projection for the data is Kentucky State Plane North (NAD83), but may have been reprojected for use in other applications. Please check metadata to determine current projection.

berkeley 100

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

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)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.

Source:

berkeley 50

berkeley 10