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 data represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular survey data. The rectangular survey data are a reference system for land tenure based upon meridian, township/range, section, section subdivision and government lots. The non-rectangular survey data represent surveys that were largely performed to protect and/or convey title on specific parcels of land such as mineral surveys and tracts. The data are largely complete in reference to the rectangular survey data at the level of first division. However, the data varies in terms of granularity of its spatial representation as well as its content below the first division. Therefore, depending upon the data source and steward, accurate subdivision of the rectangular data may not be available below the first division and the non-rectangular minerals surveys may not be present. At times, the complexity of surveys rendered the collection of data cost prohibitive such as in areas characterized by numerous, overlapping mineral surveys. In these situations, the data were often not abstracted or were only partially abstracted and incorporated into the data set. These PLSS data were compiled from a broad spectrum or sources including federal, county, and private survey records such as field notes and plats as well as map sources such as USGS 7 ½ minute quadrangles. The metadata in each data set describes the production methods for the data content. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. A complete PLSS data set includes the following: PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners, Metadata at a Glance (which identified last revised date and data steward) and Conflicted Areas (known areas of gaps or overlaps or inconsistencies). The Entity-Attribute section of this metadata describes these components in greater detail. The second division of the PLSS is quarter, quarter-quarter, sixteenth or government lot division of the PLSS. The second and third divisions are combined into this feature class as an intentional de-normalization of the PLSS hierarchical data. The polygons in this feature class represent the smallest division to the sixteenth that has been defined for the first division. For example In some cases sections have only been divided to the quarter. Divisions below the sixteenth are in the Special Survey or Parcel Feature Class. A Survey System Description is a named or numbered area of land that can be identified by a type and a designator. The survey system is generally a simultaneous conveyance that defines an area of land within which there is a consistent method of land description. These areas are typically non-federally managed lands. The special surveys polygons define the non-plss system areas for federally managed lands. The first, second and third division attributes are provied if needed for an application. These attributes are not needed if the intent is to track plats and subdivision or other survey systems only.

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.

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.

description: This data represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular survey data. The rectangular survey data are a reference system for land tenure based upon meridian, township/range, section, section subdivision and government lots. The non-rectangular survey data represent surveys that were largely performed to protect and/or convey title on specific parcels of land such as mineral surveys and tracts. The data are largely complete in reference to the rectangular survey data at the level of first division. However, the data varies in terms of granularity of its spatial representation as well as its content below the first division. Therefore, depending upon the data source and steward, accurate subdivision of the rectangular data may not be available below the first division and the non-rectangular minerals surveys may not be present. At times, the complexity of surveys rendered the collection of data cost prohibitive such as in areas characterized by numerous, overlapping mineral surveys. In these situations, the data were often not abstracted or were only partially abstracted and incorporated into the data set. These PLSS data were compiled from a broad spectrum or sources including federal, county, and private survey records such as field notes and plats as well as map sources such as USGS 7 minute quadrangles. The metadata in each data set describes the production methods for the data content. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. A complete PLSS data set includes the following: PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners, Metadata at a Glance (which identified last revised date and data steward) and Conflicted Areas (known areas of gaps or overlaps or inconsistencies). The Entity-Attribute section of this metadata describes these components in greater detail. The second division of the PLSS is quarter, quarter-quarter, sixteenth or government lot division of the PLSS. The second and third divisions are combined into this feature class as an intentional de-normalization of the PLSS hierarchical data. The polygons in this feature class represent the smallest division to the sixteenth that has been defined for the first division. For example In some cases sections have only been divided to the quarter. Divisions below the sixteenth are in the Special Survey or Parcel Feature Class. A Survey System Description is a named or numbered area of land that can be identified by a type and a designator. The survey system is generally a simultaneous conveyance that defines an area of land within which there is a consistent method of land description. These areas are typically non-federally managed lands. The special surveys polygons define the non-plss system areas for federally managed lands. The first, second and third division attributes are provied if needed for an application. These attributes are not needed if the intent is to track plats and subdivision or other survey systems only.; abstract: This data represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular survey data. The rectangular survey data are a reference system for land tenure based upon meridian, township/range, section, section subdivision and government lots. The non-rectangular survey data represent surveys that were largely performed to protect and/or convey title on specific parcels of land such as mineral surveys and tracts. The data are largely complete in reference to the rectangular survey data at the level of first division. However, the data varies in terms of granularity of its spatial representation as well as its content below the first division. Therefore, depending upon the data source and steward, accurate subdivision of the rectangular data may not be available below the first division and the non-rectangular minerals surveys may not be present. At times, the complexity of surveys rendered the collection of data cost prohibitive such as in areas characterized by numerous, overlapping mineral surveys. In these situations, the data were often not abstracted or were only partially abstracted and incorporated into the data set. These PLSS data were compiled from a broad spectrum or sources including federal, county, and private survey records such as field notes and plats as well as map sources such as USGS 7 minute quadrangles. The metadata in each data set describes the production methods for the data content. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. A complete PLSS data set includes the following: PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners, Metadata at a Glance (which identified last revised date and data steward) and Conflicted Areas (known areas of gaps or overlaps or inconsistencies). The Entity-Attribute section of this metadata describes these components in greater detail. The second division of the PLSS is quarter, quarter-quarter, sixteenth or government lot division of the PLSS. The second and third divisions are combined into this feature class as an intentional de-normalization of the PLSS hierarchical data. The polygons in this feature class represent the smallest division to the sixteenth that has been defined for the first division. For example In some cases sections have only been divided to the quarter. Divisions below the sixteenth are in the Special Survey or Parcel Feature Class. A Survey System Description is a named or numbered area of land that can be identified by a type and a designator. The survey system is generally a simultaneous conveyance that defines an area of land within which there is a consistent method of land description. These areas are typically non-federally managed lands. The special surveys polygons define the non-plss system areas for federally managed lands. The first, second and third division attributes are provied if needed for an application. These attributes are not needed if the intent is to track plats and subdivision or other survey systems only.

This dataset represents a water shortage social vulnerability analysis performed by DWR using Census 2021 block groups as the unit of analysis. This feature class includes water shortage social vulnerability indicators and scores from an analysis done by CA Department of Water Resources, joined to the 2021 Census Block Groups. Most of the indicators were pulled from the ACS (American Communities Survey). These indicators were joined to the block groups to represent a spatial analysis of the social vulnerability of communities to water shortages. The goal of this data is to provide a spatial representation of social and economic factors that can affect water shortage vulnerability in the state of California. Model indicators included in the attribute table are percent of the population 65 and older, percent of households with no vehicles, percent of population 25 and older without a high school diploma. Please note that all of these model indicators are estimated values pulled from the ACS (American Communities Survey). All model indicators are added together using sum-rank methods outlined in the Drought and Water Shortage Risk Scoring: California's Domestic Wells and State Smalls Systems document and CDC standards for sum-rank methods. This data is for the 2022 analysis using 2017-2021 ACS estimates and 2021 Census block groups. From the draft Drought and Water Shortage Vulnerability Scoring document: “Water Code Division 6 Part 2.55 Section 8 Chapter 10 (Assembly Bill 1668) effectively requires California Department of Water Resources (DWR), in consultation with other agencies and an advisory group, to identify small water suppliers and “rural communities” that are at risk of drought and water shortage. Following legislation passed in 2021 and signed by Governor Gavin Newsom, the Water Code Division 6, Section 10609.50 through 10609.80 (Senate Bill 552 of 2021) effectively requires the California Department of Water Resources to update the scoring and tool periodically in partnership with the State Water Board and other state agencies. This document describes the indicators, datasets, and methods used to construct this deliverable. " A spatial analysis was performed on the 2021 Census Block Groups, modified PLSS sections, and small water system service areas using a variety of input datasets related to drought vulnerability and water shortage risk. These indicator values were subsequently rescaled and summed for a final physical vulnerability score for the sections and small water system service areas. The 2021 Census Block Groups were joined with ACS data to represent the social vulnerability of communities, which is relevant to drought risk tolerance and resources. These three feature datasets contain the units of analysis (modified PLSS sections, block groups, small water systems service areas) with the model indicators for vulnerability in the attribute table. Model indicators are calculated for each unit of analysis according to the Vulnerability Scoring documents provided by Julia Ekstrom (Division of Regional Assistance). All three feature classes are DWR analysis zones that are based off existing GIS datasets. The spatial data for the sections feature class is extracted from the Well Completion Reports PLSS sections to be aligned with the work and analysis that SGMA is doing. These are not true PLSS sections, but a version of the projected section lines in areas where there are gaps in PLSS. The spatial data for the Census block group feature class is downloaded from the Census. ACS (American Communities Survey) data is joined by block group, and statistics calculated by DWR have been added to the attribute table. The spatial data for the small water systems feature class was extracted from the State Water Resources Control Board (SWRCB) SABL dataset, using a definition query to filter for active water systems with 3000 connections or less. None of these datasets are intended to be the authoritative datasets for representing PLSS sections, Census block groups, or water service areas. The spatial data of these feature classes is used as units of analysis for the spatial analysis performed by DWR. These datasets are intended to be authoritative datasets of the scoring tools required from DWR according to Senate Bill 552. Please refer to the Drought and Water Shortage Vulnerability Scoring: California's Domestic Wells and State Smalls Systems documentation for more information on indicators and scoring. These estimated indicator scores may sometimes be calculated in several different ways, or may have been calculated from data that has since be updated. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.4, dated September 14, 2022. DWR makes no warranties or guarantees — either expressed or implied— as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov.

This feature class consists of the trail routes on the Tongass National Forest. A route feature stores the spatial locations (geography) of the trail. These feature classes have an (M) value or measure on their vertices. A route system depicts all trails within or in close proximity to an administrative unit. A trail is a linear feature constructed for the purpose of allowing the free movement of people, stock, or Off Highway Vehicles (OHV). Route measurements and route directions must correspond to those stored in the INFRA Oracle table RTE_BASICS. Associated National Application: INFRA Travel Routes INFRA Web Page: http://basenet.fs.fed.us/support/help/trails/. New field called Data_Source was added but because these are routed trails based on trail number, and many trails have a mix of data sources, this field is not populated. To see the data source see the feature class Trail_Ln which allows a trail to be split so different data sources along the trail can be identified.Note: Extracted from GI on August 27, 2012

Update date: from GISP repository on 2/6/25. This is a static dataset.Data Type: polyline dataAn open channel is digitized from paper or scanned imagery.Subtypes:Improved: An open drainage course confined with lined or unlined embankments.Unimproved: A natural drainage course graded to channelize storm water.Swale: A graded depression with relatively low slope to channelize storm water. Ditch: A trench provided to channelize storm water. Attributes: Most of the feature classes in this storm drain geometric network share the same GIS table schema. Only the most critical attributes per operations of the Los Angeles County Flood Control District are listed below:AttributeDescriptionASBDATEThe date the design plans were approved "as-built" or accepted as "final records".CROSS_SECTION_SHAPEThe cross-sectional shape of the pipe or channel. Examples include round, square, trapezoidal, arch, etc.DIAMETER_HEIGHTThe diameter of a round pipe or the height of an underground box or open channel.DWGNODrain Plan Drawing Number per LACFCD NomenclatureEQNUMAsset No. assigned by the Department of Public Works (in Maximo Database).MAINTAINED_BYIdentifies, to the best of LAFCD's knowledge, the agency responsible for maintaining the structure.MOD_DATEDate the GIS features were last modified.NAMEName of the individual drainage infrastructure.OWNERAgency that owns the drainage infrastructure in question.Q_DESIGNThe peak storm water runoff used for the design of the drainage infrastructure.SOFT_BOTTOMFor open channels, indicates whether the channel invert is in its natural state (not lined).SUBTYPEMost feature classes in this drainage geometric nature contain multiple subtypes. 1 = Improved, 2 = Unimproved, 3 = Ditch, 4 = SwaleUPDATED_BYThe person who last updated the GIS feature.WIDTHWidth of a channel in feet.This Storm Drain Dataset is a work in progress, and all users of this data are STRONGLY ENCOURAGED to obtain the most current copy, available for download at the LA County eGIS Hub site.Terms of UseThis data is derived from the County Cadastral Landbase and features are typically added to this dataset per recorded 'as-built' drawings. Accurate facility locations on the ground must be determined by qualified field personnel. If any errors are found, or if there are general questions, please contact the individuals listed in the Credits.This product is for information purposes and should not be used for legal, engineering, or survey purposes. County assumes no liability for any errors or omissions.

This dataset represents a water shortage vulnerability analysis performed by DWR using modified PLSS sections pulled from the Well Completion Report PLSS Section Summaries. The attribute table includes water shortage vulnerability indicators and scores from an analysis done by CA Department of Water Resources, joined to modified PLSS sections. Several relevant summary statistics from the Well Completion Reports are included in this table as well. This data is from the 2024 analysis.

Water Code Division 6 Part 2.55 Section 8 Chapter 10 (Assembly Bill 1668) effectively requires California Department of Water Resources (DWR), in consultation with other agencies and an advisory group, to identify small water suppliers and “rural communities” that are at risk of drought and water shortage. Following legislation passed in 2021 and signed by Governor Gavin Newsom, the Water Code Division 6, Section 10609.50 through 10609.80 (Senate Bill 552 of 2021) effectively requires the California Department of Water Resources to update the scoring and tool periodically in partnership with the State Water Board and other state agencies. This document describes the indicators, datasets, and methods used to construct this deliverable.  This is a statewide effort to systematically and holistically consider water shortage vulnerability statewide of rural communities, focusing on domestic wells and state small water systems serving between 4 and 14 connections. The indicators and scoring methodology will be revised as better data become available and stake-holders evaluate the performance of the indicators, datasets used, and aggregation and ranking method used to aggregate and rank vulnerability scores. Additionally, the scoring system should be adaptive, meaning that our understanding of what contributes to risk and vulnerability of drought and water shortage may evolve. This understanding may especially be informed by experiences gained while navigating responses to future droughts.”

A spatial analysis was performed on the 2020 Census Block Groups, modified PLSS sections, and small water system service areas using a variety of input datasets related to drought vulnerability and water shortage risk and vulnerability. These indicator values were subsequently rescaled and summed for a final vulnerability score for the sections and small water system service areas. The 2020 Census Block Groups were joined with ACS data to represent the social vulnerability of communities, which is relevant to drought risk tolerance and resources. These three feature datasets contain the units of analysis (modified PLSS sections, block groups, small water systems service areas) with the model indicators for vulnerability in the attribute table. Model indicators are calculated for each unit of analysis according to the Vulnerability Scoring documents provided by Julia Ekstrom (Division of Regional Assistance).

All three feature classes are DWR analysis zones that are based off existing GIS datasets. The spatial data for the sections feature class is extracted from the Well Completion Reports PLSS sections to be aligned with the work and analysis that SGMA is doing. These are not true PLSS sections, but a version of the projected section lines in areas where there are gaps in PLSS. The spatial data for the Census block group feature class is downloaded from the Census. ACS (American Communities Survey) data is joined by block group, and statistics calculated by DWR have been added to the attribute table. The spatial data for the small water systems feature class was extracted from the State Water Resources Control Board (SWRCB) SABL dataset, using a definition query to filter for active water systems with 3000 connections or less. None of these datasets are intended to be the authoritative datasets for representing PLSS sections, Census block groups, or water service areas. The spatial data of these feature classes is used as units of analysis for the spatial analysis performed by DWR.

These datasets are intended to be authoritative datasets of the scoring tools required from DWR according to Senate Bill 552. Please refer to the Drought and Water Shortage Vulnerability Scoring: California's Domestic Wells and State Smalls Systems documentation for more information on indicators and scoring. These estimated indicator scores may sometimes be calculated in several different ways, or may have been calculated from data that has since be updated. Counts of domestic wells may be calculated in different ways. In order to align with DWR SGMO's (State Groundwater Management Office) California Groundwater Live dashboards, domestic wells were calculated using the same query. This includes all domestic wells in the Well Completion Reports dataset that are completed after 12/31/1976, and have a 'RecordType' of 'WellCompletion/New/Production or Monitoring/NA'.

Please refer to the Well Completion Reports metadata for more information. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.4, dated September 14, 2022. DWR makes no warranties or guarantees — either expressed or implied— as to the completeness, accuracy, or correctness of the data.

DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to GIS@water.ca.gov.

This wye pipes feature class represents current wastewater information connecting the sewer service to either side of the street in the City of Los Angeles. 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 Wye is entered into attributes. Principal attributes include:WYE_SUBTYPE: wye subtype is the principal field that describes various types of points as either Chimney, Chimney Riser, Offset Chimney Riser, Siphon, Special Case, Spur, Tap, Tee, Unclassified, Vertical Tee, Vertical Tee Riser, Wye, Wye Drawn as a Tap.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary).Wastewater Wye pipes lines layer was created in geographical information systems (GIS) software to display the location of wastewater wye pipes. The wyes lines layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are entered manually based on wastewater sewer maps and BOE standard plans, and information about the lines is entered into attributes. The wye pipes lines features are sewer pipe connections for buildings. The features in the Wastewater connector wye points layer is a related structure connected with the wye pipe line. The WYE_ID field value is the unique ID. The WYE_ID field relates to the Sewer Permit tables. The annotation wye features are displayed on maps alongside features from the Wastewater Sewer Wye pipes lines layer. The wastewater wye pipes lines 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. Wye pipe information should only be added to the Wastewater wye pipes 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 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, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:SPECIAL_STRUCT: This attribute is the basin number.TOP_: When a chimney is present, this is the depth at the top of the chimney.BOTTOM: When a chimney is present, this is the depth at the bottom of the chimney.PL_HUNDS: This value is the hundreds portion of the stationing at the property line.SHAPE: Feature geometry.USER_ID: The name of the user carrying out the edits of the wye pipes data.TYPE: This is the old wye status and is no longer referenced.REMARKS: This attribute contains additional comments regarding the wye line segment, such as a line through in all caps when lined out on wye maps.WYE_NO: This value is the number of the line segment for the wye structure located along the pipe segment. This is a 2 digit value. The number starts at 1 for the first wye connected to a pipe. The numbers increase sequentially with each wye being unique.WYE_ID: The value is a combination of PIPE_ID and WYE_NO fields, forming a unique number. This 19 digit value is a key attribute of the wye lines data layer. This field relates to the Permit tables.C_TENS: This value is the tens portion of the stationing at the curb line.C_HUNDS: This value is the hundreds portion of the stationing at the curb line.WYE_SUBTYPE: This value is the type of sewer connection. Values: • 2 - Tap. • 8 - Siphon. • 13 - Wye Drawn as a Tap. • 9 - Special Case. • 6 - Chimney riser. • 4 - Chimney. • 5 - Vertical Tee Riser. • 7 - Vertical tee. • 10 - Spur. • 11 - Unclassified. • 12 - Offset Chimney Riser. • 1 - Wye. • 3 - Tee.SIDE: The side of the pipe looking up stream to which structure attaches. Values: • U - Unknown. • L - Left. • R - Right. • C - Centered.ASSETID: User-defined unique feature number that is automatically generated.PL_DEPTH: This value is the depth of the service connection at the property line.DEPTH: This value is the depth of the Wye from the surface in feet.STAT_HUND: This value is the hundreds portion of the stationing.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.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe and to the field named PIPE_ID in the Pipe line feature class data layers.OBJECTID: Internal feature number.ENABLED: Internal feature number.REHAB: This attribute indicates if the wye pipe has been rehabilitated.C_DEPTH: This value is the depth of the service connection at the curb line.STAT_TENS: This value is the tens portion of the stationing.BASIN: This attribute is the basin number.LAST_UPDATE: Date of last update of the point feature.STATUS: This value is the active or inactive status of the wye pipes. Values: • Capped - Capped. • INACTIVE - Inactive.PL_TENS: This value is the tens portion of the stationing at the property line.CRTN_DT: Creation date of the point feature.SERVICEID: User-defined unique feature number that is automatically generated.SHAPE_Length: Length of feature in internal units.

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.

This lateral pipes feature class represents current wastewater information connecting a residence or business to the mainline sewer in the City of Los Angeles. 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.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater Lateral Pipes lines layer was created in geographical information systems (GIS) software to display the location of wastewater lateral pipes. The laterals lines layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are entered manually based on wastewater sewer maps and BOE standard plans, and information about the lines is entered into attributes. The lateral lines are constructed from LA City's main sewer connection to the Landbase parcels as shown on the Wye maps. The wastewater lateral pipes lines 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. Lateral pipe information should only be added to the Wastewater lateral pipes 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 BOE. 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, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:REHABRECORDEDLENGTHLATERALTYPE: This value is the type of lateral line. Values: • Dash - This value is for laterals that were created from a Sewer permit taken out for construction of the lateral. • Solid - This value is for laterals that were constructed when original pipe lines were constructed.MATERIALENABLED: Internal feature number.SHAPE: Feature geometry.LAST_UPDATE: Date of last update of the line feature.USER_ID: The name of the user carrying out the edits of the pipe data.SPECIAL_STRUCTDIAMETEROBJECTID: Internal feature number.CRTN_DT: Creation date of the line feature.ASSETID: User-defined unique feature number that is automatically generated.ATTACHMENTSHAPE_Length: Length of feature in internal units.

This fee feature class represents current wastewater information in the City of Los Angeles. This fee indicates that a property owner has paid the fee for a Special House Connection Sewer or Bonded Sewer House Connection Sewer permit, and the property has not been assessed for a public sewer. Fee information is inputted into the Wastewater Database by the District Office Staff. 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.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary).Wastewater Fee points layer was created in geographical information systems (GIS) software to display points representing bonded or special fee parcels. The fee 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 fee points data layer indicate that property owner have paid the fee for a Special House Connection Sewer or Bonded Sewer House Connection Sewer permit, and the property has not been assessed for a public sewer. The wastewater fee 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. Fee information should only be added to the Wastewater Fee 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:BOE_PROCESS_DATEFEE_NO: This value is the number of the document filed to establish the fees owed.AMOUNT: This value is the dollar amount of the fee owed.STATUS: This value shows the fees that were transferred to other SFC sites in the City of Los Angeles. The value indicates whether that record was a Transfer donor or a transfer recipient. Values: • TD - Transfer donor. • TR - Transfer recipient.VERIFIED: This value of is Y or null.LAT: The value is the latitude coordinate of the point.SHAPE: Feature geometry.LAST_MODF_DT: Last modification date of the point feature.LON: The value is the longitude coordinate of the point.SEWER_MAPREF_NO: This value is the reference number.PIN: The value is a combination of MAPSHEET and ID fields in Landbase Parcels data, 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. This attribute is automatically generated by the Wastewater Application during background processes, running the identity process.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • V - Valley Engineering District. • H - Harbor Engineering District. • W - West LA Engineering District. • C - Central Engineering District.OBJECTID: Internal feature number.CRTN_DTJOB_ADDRESS: This value is the the address for the parcel.USER_ID: The name of the user carrying out the edits of the fee points.TYPE: This value is the text as indicated on the map containing Wastewater Wye data. Values: • H - Unknown. • UNK - Unknown. • SSC - Sewer service charge. • LP - Letters of Participation. • SFC - Sewer facilities charge. • SF - Special fees. • OF - Outlet facilities charge. • C - Unknown. • F - Fee. • D - Unknown. • BL - Bonded lateral. • AF - No fees. • A - Unknown. • B - Bonded fee due. • S - Unknown.REMARKS: This attribute contains additional comments regarding fee points.

This connector wye feature class represents current wastewater information in the City of Los Angeles. The connector wye is the location of a chimney. 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.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater Connector Wye points layer was created in geographical information systems (GIS) software to display the location of wastewater connection points at the wye pipe lines. The connector wye layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The connector wye points are entered when the wye pipe lines are edited based on wastewater sewer maps and BOE standard plans, and information about the points is entered into attributes. The connector wye is a structure connected to the wye pipe line. Reference the WYE_SUBTYPE field for the type of structure. The WYE_ID field value is the unique ID. The WYE_ID field relates to the Sewer Permit tables. The wastewater connector wye points are inherited from sewer spatial data originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. Wye pipe information should only be added to the Wastewater wye pipes 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, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:REHAB: This attribute indicates if the pipe has been rehabilitated.BOTTOM: When a chimney is present, this is the depth at the bottom of the chimney.TOP_: When a chimney is present, this is the depth at the top of the chimney.PL_DEPTH: This value is the depth of the service connection at the property line.TYPE: This is the old wye status and is no longer referenced.SHAPE: Feature geometry.LAST_UPDATE: Date of last update of the point feature.USER_ID: The name of the user carrying out the edits of the wye data.SPECIAL_STRUCT: This describes the special structure. The design of the special structure doesn't follow the BOE Standard Plans.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe and to the field named PIPE_ID in the Pipe line feature class data layers.WYE_NO: This value is the number of the line segment for the wye structure located along the pipe segment. This is a 2 digit value. The number starts at 1 for the first wye connected to a pipe. The numbers increase sequentially with each wye being unique.C_HUNDS: This value is the hundreds portion of the stationing at the curb line.DEPTH: This value is the depth of the Wye from the surface in feet.STAT_TENS: This value is the tens portion of the stationing.WYE_SUBTYPE: This value is the type of sewer connection. Values: • 1 - Vertical tee. • 7 - . • 3 - Offset Chimney. • 4 - . • 2 - Chimney.ENABLED: Internal feature number.PL_TENS: This value is the tens portion of the stationing at the property line.SIDE: The side of the pipe looking up stream to which structure attaches. Values: • R - Right. • L - Left. • C - Centered. • U - Unknown.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.STATUS: This value is the active or inactive status of the connector wye. Values: • INACT - Inactive. • ABAN - Abandoned. • ACT - Active. • PROP_ACT - Proposed Active. • ABAN - Proposed Inactive.BASIN: This attribute is the basin number.OBJECTID: Internal feature number.C_TENS: This value is the tens portion of the stationing at the curb line.STAT_HUND: This value is the hundreds portion of the stationing.SERVICEID: User-defined unique feature number that is automatically generated.CRTN_DT: Creation date of the point feature.WYE_ID: The value is a combination of PIPE_ID and WYE_NO fields, forming a unique number. This 19 digit value is a key attribute of the wye lines data layer. This field relates to the Permit tables.PL_HUNDS: This value is the hundreds portion of the stationing at the property line.REMARKS: This attribute contains additional comments regarding the wye line segment, such as a line through in all caps when lined out on wye maps.ASSETID: User-defined unique feature number that is automatically generated.C_DEPTH: This value is the depth of the service connection at the curb line.

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals.Dataset SummaryPhenomenon Mapped: Ready-to-use project packages with over 170 attributes derived from the SSURGO dataset, split up by HUC8s. Geographic Extent: The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Source: Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024Link to source metadata*Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data.The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them.Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units.Area SymbolSpatial VersionMap Unit SymbolMap Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field.Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields.Survey Area VersionTabular VersionMap Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field.Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted AverageComponent Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected.Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent KeyComponent Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r).Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Map Unit Name (muname) fields. This field was created using the dominant soil order of each map unit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a model that included the Pivot Table Tool, the Summarize Tool and a custom script. The first 11 fields provide the sum of Component Percentage Representative Value for each soil order for each map unit. The Soil Order Dominant Condition field was calculated by selecting the highest value in the preceding 11 soil order fields. In the case of tied values the component with the lowest average slope value (slope_r) was selected. If both soil order and slope were tied

This data represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular survey data. The rectangular survey data are a reference system for land tenure based upon meridian, township/range, section, section subdivision and government lots. The non-rectangular survey data represent surveys that were largely performed to protect and/or convey title on specific parcels of land such as mineral surveys and tracts. The data are largely complete in reference to the rectangular survey data at the level of first division. However, the data varies in terms of granularity of its spatial representation as well as its content below the first division. Therefore, depending upon the data source and steward, accurate subdivision of the rectangular data may not be available below the first division and the non-rectangular minerals surveys may not be present. At times, the complexity of surveys rendered the collection of data cost prohibitive such as in areas characterized by numerous, overlapping mineral surveys. In these situations, the data were often not abstracted or were only partially abstracted and incorporated into the data set. These PLSS data were compiled from a broad spectrum or sources including federal, county, and private survey records such as field notes and plats as well as map sources such as USGS 7 ½ minute quadrangles. The metadata in each data set describes the production methods for the data content. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. A complete PLSS data set includes the following: PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners, Metadata at a Glance (which identified last revised date and data steward) and Conflicted Areas (known areas of gaps or overlaps or inconsistencies). The Entity-Attribute section of this metadata describes these components in greater detail. The second division of the PLSS is quarter, quarter-quarter, sixteenth or government lot division of the PLSS. The second and third divisions are combined into this feature class as an intentional de-normalization of the PLSS hierarchical data. The polygons in this feature class represent the smallest division to the sixteenth that has been defined for the first division. For example In some cases sections have only been divided to the quarter. Divisions below the sixteenth are in the Special Survey or Parcel Feature Class. A Survey System Description is a named or numbered area of land that can be identified by a type and a designator. The survey system is generally a simultaneous conveyance that defines an area of land within which there is a consistent method of land description. These areas are typically non-federally managed lands. The special surveys polygons define the non-plss system areas for federally managed lands. The first, second and third division attributes are provied if needed for an application. These attributes are not needed if the intent is to track plats and subdivision or other survey systems only.

Data Type: Dynamic. Vintage: Current. Editing of street features within ASP is ad-hoc. Such generally occurs on a daily to weekly basis.Data is in State Plane Grid Coordinates, Colorado Central Zone, NAD83 (US feet).This street data is maintained in the Address Street Political (ASP) production database by the Business Innovation & Technology Division via the ASP Tools. Source data is the BaseLine feature class, an atomic-level linear dataset which includes street, unnamed road and political line features. Column BL_TYPE has a domain of 'S' (street), 'U' (unnamed road and 'N' (non-street political line) and is used by the ASP DERIVATIVE processing, through tabular selection, to pull the street and unnamed road subsets to distinct features classes whenever geometric or attribute editing occurs. These linear derivatives are then pushed to the spatial data warehouse (SDEWHP) by the ASP To Warehouse (ASP2WH) processing. Here, BLTYPE is obviously 'S' for all features.Original street feature digitization in the early 1990s occurred using 1:4,800 scale ortho-rectified imagery and remnants of that digitation effort remain, where road geometry will appear quite jagged and rough when zoomed to larger scales. Between 2003 and 2011, using the Address Geocode Environment (AGE) toolset, street digitization generally occurred at higher resolutions, where1:1,000 was the desired scale. Since 2012, when ASP and the ASP Tools went live, efforts have been made to consistently digitize new street features, and fix old, at a 1:500 scale. Due to the offset in the 2022 ortho-imagery relevant the 2020 through 2012 image data, streets seen in 2020 or prior imagery will generally match to that data, where only streets new to the 2022 imagery will be aligned to such. Column BLUID (BaseLine Unique Identifier) is the unique BaseLine feature key maintained by the ASP Tools, which is independant and not-to-be confused with Esri's OBJECTID. Column BLUID is used in all ASP bridge tables where many-to-many street-related correspondences are managed.Columns BL_LBPUID (Left BPUID) and BL_RBPUID (Right BPUID) refer to the associated coincident BasePoly polgonal feature associated with the respective side of the street. Cul-de-sacs and dead-end roads, where one endpoint of the road has no connectivity to another BaseLine feature, will obviously carry the same value for BL_LBPUID and BL_RBPUID. Note BasePoly features carry political or jurisdictional attributes, and the relation of an adddress to the side of a street to which it matches and the political polygon associated with that side of the street feature is how all political attributes are tied to address point features- with the exception of special districts (tax authorities). The latter are the only political component attached to addresses via point-in-poly spatial overlay.Columns STREET_LLO (left low), STREET_LHI (left high), STREET_RLO (right low) and STREET_RHI (right high) refer to the left- and right-side address range attributes attached to a street feature. Addressible street features carry non-zero values in these columns. Note feature directionality always corresponds with address-range attribution: low values are associated with the feature's from-node and high values with the to-node.Columns STREET_LADDRESSABLE and STREET_RADDRESSABLE are flags indicating whether the side of the street is addressable, where the domain is 'Y' (yes) or null (no).Columns STREET_LZIP and STREET_RZIP refer to the left- and right zip codes associated with the street feature. Columns STREET_DIRECTION_PREFIX (street direction prefix), STREET_NAME (street name), STREET_TYPE (street type) and STREET_DIRECTION_SUFFIX (street direction suffix) form the individual components of the full street name (column STREET_NAME_FULL). Note column STREET_NAME may not be null whereas the other individual components may. Columns STREET_DIRECTION_PREFIX, STREET_TYPE and STREET_DIRECTION_SUFFIX all utilize appropriate domain tables for data entry. Table "StreetNameFull" carries the domain of all distinct (unique) street name full combinations, while table "StreetName" carries the domain of all distinct column STREET_NAME values. Both of these tables are available in SDEWHP.Column STREET_ALIAS (street alias) is a "flag" which is 'Y' where the street feature is an aliased street and null otherwise. By aliased, we mean multiple street names are attached to the feature where the primary name (generally what is signed) is shown in column STREET_NAME_FULL. The many-to-many correspondence of street features to street names is managed through the "StreetAndName" bridge table, which contains all street feature (BLUID) and street name full unique identifier (SNFUID) combinations. Table StreetAndName column STRNAMPRIORITY is used to manage which street name is primary, where a '1' indicates the signed street name and '2' the secondary name. Note the "StreetToStreetName" and "StreetNameToStreet" relationship classes (RCs) exist in SDEWHP so that when the "Street" feature class is added to an MXD, identify operations will return the multiple street names when such exist. To find all aliased streets through a tabular join, use the syntax per the following SQL:SELECT bluid, c.street_name_full, strnampriority FROM street a, streetandname b, streetnamefull c WHERE a.bluid = b.bluid AND b.snfuid = c.snfuid AND street_alias = 'Y' ORDER BY c.street_name_full, bluid, strnampriorityColumn STREET_GRID_NAME contains a code for how the street was named and addressed. For most street features, the code will be either 'DMAG' (Denver Metropolitan Addressing Grid) or 'JCAG' (Jefferson County Addressing Grid), where the latter is the County's extention to DMAG. The City of Golden (GOLDEN) is an exceptiopn, where most city streets were named and addressed based on Golden's grid. However, there are three areas within the City of Golden's municipal extents where no grid (GOLDNG) was employed. Another prominent exception is the Ken caryl Ranch Plains (KCRP) subdivision, which was granted an exemption from County addressing standards. Column STREET_GRID_KEY contains the numeric JAGUID key from the feature class JefffersonCountyAddressingGrid where such are associated with features from the Denver (DMAG) standards.Coulmns STREET_BUILT (street built) and STREET_PAVED (street paved) are "flags" which are 'Y' where true and null otherwise.Column STREET_CLASS (street classification) is a three-digit code with this domain: '010' (freeway), '020' (parkway), '030' (principal arterial), '040' (minor arterial), '050' (principal collector), '060' (collector), '070' (local residential street). ASP street classifications are periodically reviewed relative the County's Major Thoroughfare Plan (per Highways & Transportation).Column STREET_SPEED_CAD contains a two-to-three digit value associated with street classification (STREET_CLASS) and maintained solely for Sheriff Computer Aided Dispatch (CAD) purposes. Column STREET_SPEED_LIMIT contain a two digit value representing the posted speed limit. The default value for a feature derived from the STREET_SPEED_LIMIT associated with the street classification (STREET_CLASS) but may be adjusted up-or-down in 5 mile-per-hour increments to reflect actual posted speed limits. Note column STREET_SPEED_LIMIT was initially assogned based on defaults for street classificaitons; no effort has been made to correct. Over time, these values will be adjusted using both Cartegraph road maintenance information and actual observation. Column STREET_TRAVEL_DIRECTION is a two-character code for how travel occurs on a street segment. Note travel directionality, on one-way segments, often differs from feature directionality (orientation of a feature in terms of from- and to-nodes) where feature directionality is always based on addressing and the associated addressing grid. Column STREET_TRAVEL_DIRECTION contains this domain: 'BI' (bi-directional, two-way travel), 'FT' (one way travel, from feature from-node to to-node), 'TF' (one way travel, from to-node to from node), and 'NT' (no travel allowed).Columns STREET_ZLEVEL_FROM and STREET_ZLEVEL_TO are one-digit codes used to manage feature connectivity in the database relative real-world road connectivity. As an example, in the database the street features for I-70 and WARD RD show connectivity whereas in the real world Ward Road is at ground level and I-70 is an overpass- one may not directly turn left- or right from one to the other. The domain of values are '0' (underpass), '1' (ground level) and '2' and '3' for overpass conditions, where '1' is the norm for the from- and to-nodes (endpoints) of most street features. These columns consequently help manage where turns may or may not occur and are of great value in general routing operations and in dispatch. Columns LCOUNTYCODE, LCOUNTYNAME and RCOUNTYCODE, RCOUNTYNAME refer to the respective left- and right three digit Colorado county code and its associated county name. These columns do not exist in the source 'BaseLine' feature class in ASP but are appended and populated by the nightly ASP DERIVATIVE processing whenever editing has occurred. The county code is populated on the basis of left- or right- BPUID for the street segment. Given some street features on the county boundary, or extending out-of-county, have no associated BasePoly feature then LBPUID or RBPUID must be null. Consequently, in these cases, the LCOUNTYCODE or RCOUNTYCODE is null, and the associated LCOUNTYNAME or RCOUNTYNAME is designated as 'OUT OF COUNTY' rather than carrying the actual county name.

The TxDOT Roadway Inventory 2017 feature class is a statewide dataset that has attribute information routed to TxDOT Roadway linework. By using linear referencing tools, attribute information from the TxDOT Roadway Inventory table are located on the linework. Roadway attributes such as functional system, traffic counts, surface types among many others can be found on a roadway simply by selecting it or performing a query. The TxDOT Roadway Inventory layer can also be found on TxDOT’s Open Data Portal. This product is created annually by the Transportation Planning and Programming Division at TxDOT in the Data Analysis, Mapping and Reporting Branch for internal and public use.TxDOT Roadway Inventory Specifications 2017Update Frequency: 1 YearsSource: Geospatial Roadway Inventory Database (GRID)Security Level: PublicOwned by TxDOT: TrueRelated LinksData Dictionary PDF [Generated 2025/04/24]

This pipe feature class represents current wastewater information of the mainline sewer in the City of Los Angeles. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the storm drain system using a geometric network model, to ensure that its storm drains reflect current ground conditions. The conduits and inlets represent the storm drain infrastructure in the City of Los Angeles. Storm drain information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the wastewater Pipe is entered into attributes. Principal attributes include:PIPE_SUBTYPE: pipe subtype is the principal field that describes various types of lines as either Airline, Force Main, Gravity, Siphon, or Special Lateral.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater pipe lines layer was created in geographical information systems (GIS) software to display the location of sewer pipes. The pipe lines layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are entered manually based on wastewater sewer maps and BOE standard plans, and information about the lines is entered into attributes. The pipe lines are the main sewers constructed within the public right-of-way in the City of Los Angeles. The ends of line segments, of the pipe lines data, are coincident with the wastewater connectivity nodes, cleanout nodes, non-structures, and physical structures points data. Refer to those layers for more information. The wastewater pipe lines 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. For the historical information of the wastewater pipe lines layer, refer to the metadata nested under the sections Data Quality Information, Lineage, Process Step section. Pipe information should only be added to the Wastewater Pipes 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, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:STREET: This is the street name and street suffix on which the pipe is located.PIPE_LABEL: This attribute identifies the arc segment between two nodes, which represents the pipe segment. There could be any number of pipes between the same two maintenance holes and at least one. If there is more than one pipe between the same two maintenance holes, then a value other than 'A' is assigned to each pipe, such as the value 'B', 'C', and so on consecutively. Also, when a new pipe is constructed, some old pipes are not removed from the ground and the new pipe is added around the existing pipe. In this case, if the original pipe was assigned an 'A', the new pipe is assigned a 'B'.C_UP_INV: This is the calculated pipe upstream invert elevation value.PIPE_MAT: The value signifies the various materials that define LA City's sewer system. Values: • TCP - Terra Cotta pipe. • CMP - Corrugated metal pipe. • RCP - Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • PCT - Polymer concrete pipe. • CON - Concrete or cement. • DIP - Ductile iron pipe. • ABS - Acrylonitrile butadiene styrene. • STL - Steel. • UNK - Unknown. • ACP - Asbestos cement pipe. • RCL - Reinforced concrete pipe lined. • OTH - Other or unknown. • VCP - Vitrified clay pipe. • TRS - Truss pipe. • CIP - Cast iron pipe. • PVC - Polyvinyl chloride. • BRK - Brick. • RCPL - Lined Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • B/C - Concrete brick pipe. • FRP - Centrifugally cast fiberglass reinforced plastic mortar pipe.DN_INV: This is the downstream invert elevation value.PIPE_WIDTH: This value is the pipe dimension for shapes other than round.C_SLOPE: This is the calculated slope.ENABLED: Internal feature number.DN_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the downstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map using a standardized numbering scheme. The S-Map is divided into 16 grids, each numbered sequentially from west to east and north to south. The first three digits represent the S-Map number, the following two digits represent the grid number, and the last three digits represent the structure number within the grid. This field also relates to the (name of table or layer) node attribute table.PIPE_SIZE: This value is the inside pipe diameter in inches.MON_INST: This is the month of the pipe installation.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe feature class and to the field in the Wye line feature class data layers.REMARKS: This attribute contains additional comments regarding the pipe line segment.DN_STA_PLS: This is the tens value of the downstream stationing.EASEMENT: This value denotes whether or not the pipe is within an easement.DN_STA_100: This is the hundreds value of the downstream stationing.PIPE_SHAPE: The value signifies the shape of the pipe cross section. Values: • SE - Semi-Elliptical. • O1 - Semi-Elliptical. • UNK - Unknown. • BM - Burns and McDonald. • S2 - Semi-Elliptical. • EL - Elliptical. • O2 - Semi-Elliptical. • CIR - Circular. • Box - Box (Rectangular).PIPE_STATUS: This attribute contains the pipe status. Values: • U - Unknown. • P - Proposed. • T - Abandoned. • F - As Built. • S - Siphon. • L - Lateral. • A - As Bid. • N - Non-City. • R - Airline.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • O - Out LA. • V - Valley Engineering District. • W - West LA Engineering District. • H - Harbor Engineering District. • C - Central Engineering District.C_PIPE_LEN: This is the calculated pipe length.OWNER: This value is the agency or municipality that constructed the pipe. Values: • PVT - Private. • CTY - City of LA. • FED - Federal Facilities. • COSA - LA County Sanitation. • OUTLA - Adjoining cities.CRTN_DT: Creation date of the line feature.TRTMNT_LOC: This value is the treatment plant used to treat the pipe wastewater.PCT_ENTRY2: This is the flag determining if the second slope value, in SLOPE2 field, was entered in percent as opposed to a decimal. Values: • Y - The value is expressed as a percent. • N - The value is not expressed as a percent.UP_STA_100: This is the hundreds value of the upstream stationing.DN_MH: The value is the ID of the structure. This point is the structure that may be a maintenance hole, pump station, junction, etc. The field name DN_MH signifies the structure is the point at the downstream end of the pipe line segment. The field DN_MH is a key attribute to relate the pipe lines feature class to the STRUCTURE_ID field in the physical structures feature class.SAN_PIPE_IDUSER_ID: The name of the user carrying out the edits of the pipe data.WYE_MAT: This is the pipe material as shown on the wye card.WYE_DIAM: This is the pipe diameter as shown on the wye card.SLOPE2: This is the second slope value used for pipe segments with a vertical curve.EST_YR_LEV: This value is the year installed level.EST_MATL: This is the flag determining if the pipe material was estimated.LINER_DATE: This value is the year that the pipe was re-lined.LAST_UPDATE: Date of last update of the line feature.SHAPE: Feature geometry.EST_YEAR: This is the flag indicating if the year if installation was estimated.EST_UPINV: This is the flag determining if the pipe upstream elevation value was estimated.WYE_UPDATE: This value indicates whether the wye card was updated.PCT_ENTRY: This is the flag determining if the slope was entered in percent as opposed to a decimal. Values: • N - The value is not expressed as a percent. • Y - The value is expressed as a percent.PROF: This is the profile drawing number.PLAN1: This is the improvement plan drawing number.PLAN2: This is the supplementary improvement plan drawing number.EST_DNINV: This is the flag determining if the pipe downstream elevation value was estimated.UP_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the upstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map

The Digital Geologic Units of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina consists of geologic units mapped as area (polygon) features. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). The data were captured, grouped and attributed as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1. (available at: https://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The data layer is available as a feature class in a 9.1 personal geodatabase (grsm_geology.mdb). Attributed geologic contact lines that define the geologic unit polygons are present within the Geologic Contacts (GRSMGLGA) data layer. The Geologic Units (GRSMGLG) GIS data layer is also available as a coverage export (.E00) file (GRSMGLG.E00), and as a shapefile (.SHP) file (GRSMGLG.SHP). Each GIS data format has an ArcGIS 9.1 layer (.LYR) file (GRSMGLG_GDB.LYR (geodatabase feature class), GRSMGLG_COV.LYR (coverage), GRSMGLG_SHP.LYR (shapefile) with map symbology that is included with the GIS data. See the Distribution Information section for additional information on data acquisition. The GIS data projection is NAD83, UTM Zone 17N. That data is within the area of interest of Great Smoky Mountains National Park. This dataset is just one component of the Digital Geologic Map of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina. The data layers (feature classes) that comprise the Digital Geologic Map of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina include: GRSMAML (Alteration and Metamorphic Lines), GRSMATD (Geologic Attitude and Observation Points), GRSMFLD (Folds), GRSMFLT (Faults), GRSMGLG (Geologic Units), GRSMGLGA (Geologic Contacts), GRSMGPT (Point Geologic Features), GRSMGSL (Geologic Sample Localities), GRSMMIN (Mine Point Features), GRSMSEC (Cross Section Lines), GRSMSUR (Surficial Geologic Units), GRSMSURA (Surficial Contacts) and GRSMSYM (Fault Symbology). There are three additional ancillary map components, the Geologic Unit Information (GRSMGLG1) Table, the Source Map Information (GRSMMAP) Table and the Map Help File (GRSM_GEOLOGY.HLP). Refer to the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1 (available at: https://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm) for detailed data layer (feature class) and table specifications including attribute field parameters, definitions and domains, and implemented topology rules and relationship classes.The corresponding Integration of Resource Management Applications (IRMA) NPS Data Store reference is Great Smoky Mountains National Park Geology.