US Postal Service ZIP Code boundaries. This layer was created by Los Angeles County eGIS to align with parcel boundaries.ZIP is an acronym for Zone Improvement Plan.Legal vs. Postal Cities: Many users confuse the name the Post Office delivers mail to (e.g. Van Nuys, Hollywood) as a legal city (in this case Los Angeles), when they are a postal city. The County contains 88 legal cities, and over 400 postal names that are tied to the ZIP Codes. To support usability and geocoding, we have attached the first 3 postal cities to each address, based upon its ZIP Code.The US Postal Service is the authoritative source for ZIP Code data. See their website for more information.

The features in this layer represent the five-digit ZIP Code areas that are used by the U.S. Postal Service to deliver mail more effectively. This layer provides ZIP Code, postal district name, population, and area for the ZIP Code areas in California.

Feature layer generated from running the Join Features solution

© Los Angeles County

Polygon geometry with attributes displaying United States Postal Service zone improvement plan (ZIP) codes in East Baton Rouge Parish, Louisiana.Metadata

Blocks are typically bounded by streets, roads or creeks. In cities, a census block may correspond to a city block, but in rural areas where there are fewer roads, blocks may be limited by other features. The Census Bureau established blocks covering the entire nation for the first time in 1990.There are less number of Census Blocks within Los Angeles County in 2020 Census TIGER/Line Shapefiles, compared in 2010.Updated:1. June 2023: This update includes 2022 November Santa Clarita City annexation and the addition of "Kinneloa Mesa" community (was a part of unincorporated East Pasadena). Added new data fields FIP_CURRENT to CITYCOMM_CURRENT to reflect new/updated city and communities. Updated city/community names and FIP codes of census blocks that are in 2022 November Santa Clarita City annexation and new Kinneloa Mesa community (look for FIP_Current, City_Current, Comm_Current field values)2. February 2023: Updated few Census Block CSA values based on Demographic Consultant inquiry/suggestions3. April 2022: Updated Census Block data attribute values based on Supervisorial District 2021, Service Planning Area 2022, Health District 2022 and ZIP Code Tabulation Area 2020Created: March 2021How This Data is Created? This census geographic file was downloaded from Census Bureau website: https://www2.census.gov/geo/tiger/TIGER2020PL/STATE/06_CALIFORNIA/06037/ on February 2021 and customized for LA County. New data fields are added in the census blocks 2020 data and populated with city/community names, LA County FIPS, 2021 Supervisorial Districts, 2020 Census Zip Code Tabulation Area (ZCTA) and some administrative boundary information such as 2022 Health Districts and 2022 Service Planning Areas (SPS) are also added. "Housing20" field value and "Pop20" field value is populated with PL 94-171 Redistricting Data Summary File: Decennial Census P.L. 94-171 Redistricting Data Summary Files. Similarly, "Feat_Type" field is added and populated with water, ocean and land values. Five new data fields (FIP_CURRENT to CITYCOMM_CURRENT) are added in June 2023 updates to accommodate 2022 Santa Clarita city annexation. City/community names and FIP codes of census blocks affected by 2022 November Santa Clarita City annexation are assigned based on the location of block centroids. In June 2023 update, total of 36 blocks assigned to the City of Santa Clarita that were in Unincorporated Valencia and Castaic. Note: This data includes 3 NM ocean (FEAT_TYPE field). However, user can use a definition query to remove those. Data Fields: 1. STATE (STATEFP20): State FIP, "06" for California, 2. COUNTY (COUNTYFP20): County FIP "037" for Los Angeles County, 3. CT20: (TRACTCE20): 6-digit census tract number, 4. BG20: 7-digit block group number, 5. CB20 (BLOCKCE20): 4-digit census block number, 6. CTCB20: Combination of CT20 and CB20, 7. FEAT_TYPE: Land use types such as water bodies, ocean (3 NM ocean) or land, 8. FIP20: Los Angeles County FIP code, 9. BGFIP20: Combination of BG20 and FIP20, 10. CITY: Incorporated city name, 11. COMM: Unincorporated area community name and LA City neighborhood, also known as "CSA", 12. CITYCOMM: City/Community name label, 13. ZCTA20: Parcel specific zip codes, 14. HD12: 2012 Health District number, 15. HD_NAME: Health District name, 16. SPA22: 2022 Service Planning Area number, 17. SPA_NAME: Service Planning Area name, 18. SUP21: 2021 Supervisorial District number, 19. SUP_LABEL: Supervisorial District label, 20. POP20: 2020 Population (PL 94-171 Redistricting Data Summary File - Total Population), 21. HOUSING20: 2020 housing (PL 94-171 Redistricting Data Summary File - Total Housing),22. FIP_CURRENT: Los Angeles County 2023 FIP code, as of June 2023,23. BG20FIP_CURRENT: Combination of BG20 and 2023 FIP, as of June 2023,24. CITY_CURRENT: 2023 Incorporated city name, as of June 2023,25. COMM_CURRENT: 2023 Unincorporated area community name and LA City neighborhood, also known as "CSA", as of June 2023,26. CITYCOMM_CURRENT: 2023 City/Community name label, as of June 2023.

Enrichissement du fichier fourni par la Poste avec les noms de régions, départements et commune en lettre minuscule ainsi que leurs codes INSEE respectifs. https://www.data.gouv.fr/fr/datasets/base-officielle-des-codes-postaux/ Fichier de correspondance entre les codes communes (INSEE) et les codes postaux au format csv. Ce fichier comprend : code_commune_INSEE nom_commune_postal code_postal libelle_acheminement ligne_5 latitude longitude code_commune article nom_commune nom_commune_complet code_departement nom_departement code_region nom_region Exemple: Code_commune_INSEE,Nom_commune,Code_postal,Libelle_acheminement,Ligne_5,longitude,latitude,code_commune,article,nom_commune,nom_commune_complet,code_departement,nom_departement,code_region,nom_region 1001 L ABERGEMENT CLEMENCIAT 1400 L ABERGEMENT CLEMENCIAT 46.1534255214 4.92611354223 1 L' Abergement-Clémenciat L'Abergement-Clémenciat 1 Ain 84 Auvergne-Rhône-Alpes 1002 L ABERGEMENT DE VAREY 1640 L ABERGEMENT DE VAREY 46.0091878776 5.42801696363 2 L' Abergement-de-Varey L'Abergement-de-Varey 1 Ain 84 Auvergne-Rhône-Alpes 1004 AMBERIEU EN BUGEY 1500 AMBERIEU EN BUGEY 45.9608475114 5.3729257777 4 Ambérieu-en-Bugey Ambérieu-en-Bugey 1 Ain 84 Auvergne-Rhône-Alpes Il correspond aux codes postaux de France (métropole et DOM), ceux des TOM, ainsi que MONACO. Note aux réutilisateurs: les contours géographiques des communes, à partir de leurs codes INSEE, sont aussi disponibles sur https://www.data.gouv.fr/fr/. Vous découvrirez des formats de fichiers supplémentaires, des outils de visualisation et des API sur https://datanova.legroupe.laposte.fr. 💓💓💓 Suport Vous pouvez soutenir mon travail https://github.com/sponsors/mohamed-badaoui Merci 🙏

A dataset showing the population of 54601 between 2010 and 2020.

This group of layers are a geographic representation of the service boundaries for each of the programs administered by the LA County Department of Public Social Services (DPSS). Each DPSS district office is responsible for tracking and auditing the cases that fall within their boundaries. The following are the DPSS programs that have a service boundary:- CalFresh- CalWORKS- Medi-Cal- IHSS- GROW- General Relief- GAIN- CAPIPlease note that these layers are subject to change as DPSS sees fit and without prior notice. For more information on these programs, please visit https://dpss.lacounty.gov/.

This data set contains all of the indigenous languages captured from CIELO surveys by Zip Code. Survey results are visualized on the LA County Limited English Communities map at https://apps.gis.lacounty.gov/static/ARDI/limited-english/.Created by: Lupe Renteria SalomeDate Created: 8/29/2024Last modified: 12/19/2024Source: USC Equity Research Institute analysis of outreach data collected by Comunidades Indígenas en Liderazgo (CIELO), Los Angeles County, 2021-2023.Data Included:Individuals who self-reported "yes" to the question of being from an indigenous community and/or reported that they speak an Indigenous language.You will find a "Blank" and "0" column that counts respondents who did not report an indigenous language. Subtract these counts from the "total" column to calculate total respondents who reported speaking any indigenous language.Data set includes all reported values for zip_code, some that may not be complete zip codes or not in LA County.

Power Outages by County

This is the ONS Postcode Directory (ONSPD) for the United Kingdom as at February 2023 in Comma Separated Variable (CSV) and ASCII text (TXT) formats. This file contains the multi CSVs so that postcode areas can be opened in MS Excel. To download the zip file click the Download button. The ONSPD relates both current and terminated postcodes in the United Kingdom to a range of current statutory administrative, electoral, health and other area geographies. It also links postcodes to pre-2002 health areas, 1991 Census enumeration districts for England and Wales, 2001 Census Output Areas (OA) and Super Output Areas (SOA) for England and Wales, 2001 Census OAs and SOAs for Northern Ireland and 2001 Census OAs and Data Zones (DZ) for Scotland. It now contains 2021 Census OAs and SOAs for England and Wales. It helps support the production of area based statistics from postcoded data. The ONSPD is produced by ONS Geography, who provide geographic support to the Office for National Statistics (ONS) and geographic services used by other organisations. The ONSPD is issued quarterly. (File size - 234 MB)NOTE: The 2022 ONSPDs included an incorrect update of the ITL field with two LA changes in Northamptonshire. This error has been corrected from the February 2023 ONSPD.NOTE: There was an issue with the originally published file where some change orders yet to be included in OS Boundary-LineÔ (including The Cumbria (Structural Changes) Order 2022, The North Yorkshire (Structural Changes) Order 2022 and The Somerset (Structural Changes) Order 2022) were mistakenly implemented for terminated postcodes. Version 2 corrects this, so that ward codes E05014171–E05014393 are not yet included. Please note that this product contains Royal Mail, Gridlink, LPS (Northern Ireland), Ordnance Survey and ONS Intellectual Property Rights.

The California Department of Forestry and Fire Protection's Fire and Resource Assessment Program (FRAP) annually maintains and distributes an historical wildland fire perimeter dataset from across public and private lands in California. The GIS data is developed with the cooperation of the United States Forest Service Region 5, the Bureau of Land Management, California State Parks, National Park Service and the United States Fish and Wildlife Service and is released in the spring with added data from the previous calendar year. Although the dataset represents the most complete digital record of fire perimeters in California, it is still incomplete, and users should be cautious when drawing conclusions based on the data.

This data should be used carefully for statistical analysis and reporting due to missing perimeters (see Use Limitation in metadata). Some fires are missing because historical records were lost or damaged, were too small for the minimum cutoffs, had inadequate documentation or have not yet been incorporated into the database. Other errors with the fire perimeter database include duplicate fires and over-generalization. Additionally, over-generalization, particularly with large old fires, may show unburned "islands" within the final perimeter as burned. Users of the fire perimeter database must exercise caution in application of the data. Careful use of the fire perimeter database will prevent users from drawing inaccurate or erroneous conclusions from the data. This data is updated annually in the spring with fire perimeters from the previous fire season. This dataset may differ in California compared to that available from the National Interagency Fire Center (NIFC) due to different requirements between the two datasets. The data covers fires back to 1878. As of May 2024, it represents fire23_1.

Please help improve this dataset by filling out this survey with feedback:

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep23_1 was released in May 2024. Two hundred eighty four fires from the 2023 fire season were added to the database (21 from BLM, 102 from CAL FIRE, 72 from Contract Counties, 19 from LRA, 9 from NPS, 57 from USFS and 4 from USFW). The 2020 Cottonwood fire, 2021 Lone Rock and Union fires, as well as the 2022 Lost Lake fire were added. USFW submitted a higher accuracy perimeter to replace the 2022 River perimeter. Additionally, 48 perimeters were digitized from an historical map included in a publication from Weeks, d. et al. The Utilization of El Dorado County Land. May 1934, Bulletin 572. University of California, Berkeley. Two thousand eighteen perimeters had attributes updated, the bulk of which had IRWIN IDs added. A duplicate 2020 Erbes perimeter was removed. The following fires were identified as meeting our collection criteria, but are not included in this version and will hopefully be added in the next update: Big Hill #2 (2023-CAHIA-001020).

YEAR_ field changed to a short integer type. San Diego CAL FIRE UNIT_ID changed to SDU (the former code MVU is maintained in the UNIT_ID domains). COMPLEX_INCNUM renamed to COMPLEX_ID and is in process of transitioning from local incident number to the complex IRWIN ID. Perimeters managed in a complex in 2023 are added with the complex IRWIN ID. Those previously added will transition to complex IRWIN IDs in a future update.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2019-2023), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-present. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep23_1) Metadata

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

Un jeu de données mis à jour avec les données 2015 est disponible. Correspondance entre les codes postaux et codes INSEE des communes Françaises. Ce jeu de données a été constitué à partir des données de la base GEOFLA® 2013 mise à disposition par l'IGN (codes INSEE) ainsi qu'à partir de données Wikipédia (codes postaux).

La base officielle des codes postaux est un jeu de données qui fournit la correspondance entre les codes postaux et les codes INSEE des communes.Ce jeu de données comprend :Le nom de la communeLe code INSEE de la communeLa ligne 5 de l'adresse postale : précision du lieu-dit associé ou du nom de la commune déléguée associéeLe code postal de la communeLe libellé d’acheminement

Government Code 51175-89 directs the California Department of Forestry and Fire Protection (CAL FIRE) to identify areas of very high fire hazard severity zones within Local Responsibility Areas (LRA). Mapping of the areas, referred to as Very High Fire Hazard Severity Zones (VHFHSZ), is based on data and models of, potential fuels over a 30-50 year time horizon and their associated expected fire behavior, and expected burn probabilities to quantify the likelihood and nature of vegetation fire exposure (including firebrands) to buildings. Details on the project and specific modeling methodology can be found at http://frap.cdf.ca.gov/projects/hazard/methods.html. Local Responsibility Area VHFHSZ maps were initially developed in the mid-1990s and are now being updated based on improved science, mapping techniques, and data. This specific geographic information system dataset depicts final CAL FIRE recommendations for Very High FHSZs within the local jurisdiction. The process of finalizing these boundaries involved an extensive local review process, the details of which are available at http://frap.cdf.ca.gov/projects/hazard/btnet/ (click on "Continue as guest without logging in"). Local government has 120 days to designate, by ordinance, very high fire hazard severity zones within its jurisdiction after receiving the recommendation. Local government can add additional VHFHSZs. There is no requirement for local government to report their final action to CAL FIRE when the recommended zones are adopted. Consequently, users are directed to the appropriate local entity (county, city, fire department, or Fire Protection District) to determine the status of the local fire hazard severity zone ordinance. To display the areas of VHFHSZ recommended by CAL FIRE, simply display on the attribute HAZ_CLASS, as that has been filtered to represent only areas in the Very High Class, and only for areas that are in Local Responsibility Area (LRA) status.

© CAL FIRE recoginzes the important contribution of various local government entities that contributed data, maps, and comments that were critical components of the FHSZ mapping process.

This layer is a component of PlanningData.

A best-fit lookup between postcodes, frozen 2011 Census Output Areas (OA), Lower Layer Super Output Areas (LSOA), Middle Layer Super Output Areas (MSOA) and current local authority districts (LAD) as at May 2022 in the UK. Postcodes are best-fitted by plotting the location of the postcode's mean address into the areas of the output geographies. (File size 24 MB).Field Names - PCD7, PCD8, PCDS, DOINTR, DOTERM, USERTYPE, OA11CD, LSOA11CD, MSOA11CD, LADCD, LSOA11NM, MSOA11NM, LADNM, LADNMWField Types - All TextField Lengths - 7, 8, 8, 8, 8, 1, 9, 9, 9, 9, 55, 65, 45, 45

The 311 Citizen Request for Service Parent Type hosted feature layer displays the last 365 days of citizen service requests in East Baton Rouge Parish, Louisiana. The data in this layer is categorized by service request parent type including:BlightCode ViolationDrainage and FloodingEnvironmentalGarbageMowing and TreeNeighborhood and SubdivisionRecyclingRoad MaintenanceSewer and WastewaterStreet and TrafficThe data includes attribute fields for applying filters such as date range, council district, neighborhood, or ZIP code.

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

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