This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire. Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable. Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC).  Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute. Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations. Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed. Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed. Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires. Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives. Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities. IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers. Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands. Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created. GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event. Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned. Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters) RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters. This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.

Area Covered: World

What can I do with this layer?
The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.


It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.

Attribute Information

• Latitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?
• Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.
• Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?
• Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.
  
• Acquisition Date: Derived Date/Time field combining Date and Time attributes.
• Satellite: Whether the detection was picked up by the Terra or Aqua satellite.
• Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.
• Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.
• Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.
• FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).
• DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.
• Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.

This map is provided for informational purposes and is not monitored 24/7 for accuracy and

This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire. Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable. Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC).  Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute. Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations. Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed. Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed. Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires. Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives. Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities. IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers. Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands. Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created. GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event. Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned. Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters) RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters. This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This dataset has been deprecated. Please see 2017 Countywide LiDAR Point Cloud for more information.Industry standard .las LiDAR (Light Detection And Ranging) classified points. This LiDAR data was collected using Leica's ALS50 Phase I sensor. The raw data was verified in Merrick and Company's LiDAR software (MARS) for complete coverage of the project area, and boresighted to align the flightlines. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: unclassified points, ground points, breakline proximity points, "noise" points and water. The data was next taken into MARS to reclassify the erroneous points that may remain in the LiDAR point cloud after auto-filter.The horizontal datum used is the North American 1983 HARN. The vertical datum is the North American Vertical Datum of 1988. The projection is Illinois State Plane, Eastern Zone, using US Survey Feet as units.

The LAS data set was originally classified according to 4 classes (ground, water, bridge overpass, and noise), with the rest of the data being unclassified. That left some classes to be derived and classified, of which one—the building/ structure class—was considered necessary for this project. In theory, deriving a building/structure layer is relatively straightforward: the building reflectance response should be unclassified, single-reflectance response points, whereas the vegetation, also unclassified, should yield a multiple-reflectance response as the beam bounces back through the canopy. Following this idea, we created a Digital Surface Model (DSM) from the single-response, unclassified LAS point cloud. We then subtracted these DSMs from the Bare Earth DEMs to create a difference image, which ideally should represent only buildings. Unfortunately, many trees were included in this “buildings” layer, due possibly to the sparse canopy that is characteristic of trees found in southwestern forests and possibly to the presence of fairly recent burn scars that include a number of standing dead trees and snags. In an attempt to remove the clutter of false positives due to trees, we developed a Normalized Difference Vegetation Index (NDVI) from the NAIP imagery acquired over the area in the same year. The NDVI is an image-processing technique that uses the reflective information found in the red (Red) and near-infrared (NIR) wavelengths to enhance the “green” vegetative response over other, non-vegetated surface features (Eq. 1). NDVI = (NIR−Red)/(NIR+Red) [Eq. 1]. This provides a floating-point image of values from -1 to 1, with numbers above 0 representing increasing vegetative cover. We further modified the NDVI equation to create an 8-bit image (Eq. 2). NDVImod = (NDVI+1)*100 [Eq. 2]. This 8-bit image had all positive integer values, where values above 100 indicated increasing vegetative cover. We used the generated NDVI image, in particular values above 109, to mask out many of the false anomalies. In addition, all heights less than 6 feet were masked out, as this was considered a minimum height for most buildings. We added 1 to values in the resulting image so that all values, even the zeroes, would be counted. Then values were clumped to produce an image of individually coded raster polygons. We eliminated all clusters smaller than 32 square meters (345 square feet) from the clumped image, ran a 3x3 majority filter to remove relict edges, and ran a 3x3 morphological close filter to remove holes in the raster polygons. We completed the raster processing in ERDAS IMAGINE and then converted the data set to a polygon layer in ESRI ArcGIS, as is and without using the ‘simplify polygon’ option. This was cleaned up further using the simplify buildings module with a minimum spacing of 2 meters. Once this was completed, the polygon layer was edited using the NAIP imagery and DSM Shaded Relief imagery as a background by a heads-up digitizing at a 1:3,000 scale (the approximate base resolution of the LiDAR data). The building/structure layer contained more than 44,612 identified structures.

Important Note:The metadata description below mentions the Regional Housing Needs Assessment (or RHNA). Part of meeting RHNA Eligibility is satisfying a list of criteria set by the State of California that needs to be met in order to qualify. This dataset contains both RHNA Eligible and non-RHNA Eligible sites. Non-RHNA Eligible sites are those that didn't quite meet the eligibility criteria set by the state, but will be still eligible for Rezoning per Department of Regional Planning guidelines, and thus represents a full picture of ALL sites that are eligible for Rezoning. The official Housing Element Rezoning layer that was certified by the State of California is located here, but it should be noted that this layer only contains sites that are RHNA Eligible.IntroductionThis metadata is broken up into different sections that provide both a high-level summary of the Housing Element and more detailed information about the data itself with links to other resources. The following is an excerpt from the Executive Summary from the Housing Element 2021 – 2029 document:The County of Los Angeles is required to ensure the availability of residential sites, at adequate densities and appropriate development standards, in the unincorporated Los Angeles County to accommodate its share of the regional housing need--also known as the Regional Housing Needs Allocation (RHNA). Unincorporated Los Angeles County has been assigned a RHNA of 90,052 units for the 2021-2029 Housing Element planning period, which is subdivided by level of affordability as follows:Extremely Low / Very Low (<50% AMI) - 25,648Lower (50 - 80% AMI) - 13,691Moderate (80 - 120% AMI) - 14,180Above Moderate (>120% AMI) - 36,533Total - 90,052NOTES - Pursuant to State law, the projected need of extremely low income households can be estimated at 50% of the very low income RHNA. Therefore, the County’s projected extremely low income can be estimated at 12,824 units. However, for the purpose of identifying adequate sites for RHNA, no separate accounting of sites for extremely low income households is required. AMI = Area Median IncomeDescriptionThe Sites Inventory (Appendix A) is comprised of vacant and underutilized sites within unincorporated Los Angeles County that are zoned at appropriate densities and development standards to facilitate housing development. The Sites Inventory was developed specifically for the County of Los Angeles, and has built-in features that filter sites based on specific criteria, including access to transit, protection from environmental hazards, and other criteria unique to unincorporated Los Angeles County. Other strategies used within the Sites Inventory analysis to accommodate the County’s assigned RHNA of 90,052 units include projected growth of ADUs, specific plan capacity, selected entitled projects, and capacity or planned development on County-owned sites within cities. This accounts for approximately 38 percent of the RHNA. The remaining 62 percent of the RHNA is accommodated by sites to be rezoned to accommodate higher density housing development (Appendix B).Caveats:This data is a snapshot in time, generally from the year 2021. It contains information about parcels, zoning and land use policy that may be outdated. The Department of Regional Planning will be keeping an internal tally of sites that get developed or rezoned to meet our RHNA goals, and we may, in the future, develop some public facing web applications or dashboards to show the progress. There may even be periodic updates to this GIS dataset as well, throughout this 8-year planning cycle.Update History:12/18/24 - Following the completion of the annexation to the City of Whittier on 11/12/24, 27 parcels were removed along Whittier Blvd which contained 315 Very Low Income units and 590 Above Moderate units. Following a joint County-City resolution of the RHNA transfer to the city, 247 Very Low Income units and 503 Above Moderate units were taken on by Whittier. 10/23/24 - Modifications were made to this layer during the updates to the South Bay and Westside Area Plans following outreach in these communities. In the Westside Planning area, 29 parcels were removed and no change in zoning / land use policy was proposed; 9 Mixed Use sites were added. In the South Bay, 23 sites were removed as they no longer count towards the RHNA, but still partially changing to Mixed Use.5/31/22 – Los Angeles County Board of Supervisors adopted the Housing Element on 5/17/22, and it received final certification from the State of California Department of Housing and Community Development (HCD) on 5/27/22. Data layer published on 5/31/22.Links to other resources:Department of Regional Planning Housing Page - Contains Housing Element and it's AppendicesHousing Element Update - Rezoning Program Story Map (English, and Spanish)Southern California Association of Governments (SCAG) - Regional Housing Needs AssessmentCalifornia Department of Housing and Community Development Housing Element pageField Descriptions:OBJECTID - Internal GIS IDAIN - Assessor Identification Number*SitusAddress - Site Address (Street and Number) from Assessor Data*Use Code - Existing Land Use Code (corresponds to Use Type and Use Description) from Assessor Data*Use Type - Existing Land Use Type from Assessor Data*Use Description - Existing Land Use Description from Assessor Data*Vacant / Nonvacant – Parcels that are vacant or non-vacant per the Use Code from the Assessor Data*Units Total - Total Existing Units from Assessor Data*Max Year - Maximum Year Built from Assessor Data*Supervisorial District (2021) - LA County Board of Supervisor DistrictSubmarket Area - Inclusionary Housing Submarket AreaPlanning Area - Planning Areas from the LA County Department of Regional Planning General Plan 2035Community Name - Unincorporated Community NamePlan Name - Land Use Plan Name from the LA County Department of Regional Planning (General Plan and Area / Community Plans)LUP - 1 - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 1 (% area) - Land Use Policy from Dept. of Regional Planning - Primary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 2 - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 2 (% area) - Land Use Policy from Dept. of Regional Planning - Secondary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*LUP - 3 - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (in cases where there are more than one Land Use Policy category present)*LUP - 3 (% area) - Land Use Policy from Dept. of Regional Planning - Tertiary Land Use Policy (% of parcel covered in cases where there are more than one Land Use Policy category present)*Current LUP (Description) – This is a brief description of the land use category. In the case of multiple land uses, this would be the land use category that covers the majority of the parcel*Current LUP (Min Density - net or gross) - Minimum density for this category (as net or gross) per the Land Use Plan for this areaCurrent LUP (Max Density - net or gross) - Maximum density for this category (as net or gross) per the Land Use Plan for this areaProposed LUP – Final – The proposed land use category to increase density.Proposed LUP (Description) – Brief description of the proposed land use policy.Prop. LUP – Final (Min Density) – Minimum density for the proposed land use category.Prop. LUP – Final (Max Density) – Maximum density for the proposed land use category.Zoning - 1 - Zoning from Dept. of Regional Planning - Primary Zone (in cases where there are more than one zone category present)*Zoning - 1 (% area) - Zoning from Dept. of Regional Planning - Primary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 2 - Zoning from Dept. of Regional Planning - Secondary Zone (in cases where there are more than one zone category present)*Zoning - 2 (% area) - Zoning from Dept. of Regional Planning - Secondary Zone (% of parcel covered in cases where there are more than one zone category present)*Zoning - 3 - Zoning from Dept. of Regional Planning - Tertiary Zone (in cases where there are more than one zone category present)*Zoning - 3 (% area) - Zoning from Dept. of Regional Planning - Tertiary Zone (% of parcel covered in cases where there are more than one zone category present)*Current Zoning (Description) - This is a brief description of the zoning category. In the case of multiple zoning categories, this would be the zoning that covers the majority of the parcel*Proposed Zoning – Final – The proposed zoning category to increase density.Proposed Zoning (Description) – Brief description of the proposed zoning.Acres - Acreage of parcelMax Units Allowed - Total Proposed Land Use Policy UnitsRHNA Eligible? – Indicates whether the site is RHNA Eligible or not. Very Low Income Capacity - Total capacity for the Very Low Income level as defined in the Housing ElementLow Income Capacity - Total capacity for the Low Income level as defined in the Housing ElementModerate Income Capacity - Total capacity for the Moderate Income level as defined in the Housing ElementAbove Moderate Income Capacity - Total capacity for the Above Moderate Income level as defined in the Housing ElementRealistic Capacity - Total Realistic Capacity of parcel (totaling all income levels). Several factors went into this final calculation. See the Housing Element (Links to Other Resources above) in the following locations - "Sites Inventory - Lower Income RHNA" (p. 223), and "Rezoning - Very Low / Low Income RHNA" (p231).Income Categories - Income Categories assigned to the parcel (relates

Data provided here are from the DC's 311 service request center. They represent all service requests for residential snow removal. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at 311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC) oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Map which allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

The Merced Vernal Pools and Grassland Reserve is 6,500 acres of protected habitat adjacent to the University of California Merced containing rare and endangered species and a unique seasonal wetland habitat. These data were gathered to be used for hydrological modelling on the Reserve for potential restoration projects and to be made public for other researchers who may find very high resolution topographical information useful for their work. This dataset contains a Digital Elevation Model created from 8 field survey days of Aerial LiDAR Scanning (ALS) with a small Unmanned Aerial System (sUAS).

Methods Work Completed by Researchers at University of California, Merced under the direction of Dean/Director/Professor Joshua H. Viers | Vicelab and CITRIS Aviation

Spatial Reference: WGS 1984 UTM Zone 10N / WGS84 Geoid

Units: Meters

Equipment: DJI M600 Pro with Phoenix Aerial Systems AL3-32 LiDAR

Software: Phoenix LiDAR Systems SpatialSuite 4.0.3, LasTools, ArcGIS Pro 2.4, Litchi, ArduPilot Mission Planner

Field Crew/Processing: Michael Kalua (sUAS Pilot/Mission Planning/Sensor Operator/Data Processing), Andreas Anderson (sUAS Pilot/Mission Planning/Sensor Operator), Daniel Gomez (Sensor Operator), Hayden Namgostar (Sensor Operator)

Field Methods: An RTK reference station was set up before each field day over a previously-surveyed benchmark near the entrance of the Reserve, which would continuously send RTK corrections to the LiDAR system over an internet connection service. Before flight the LiDAR system was allowed at least 15 minutes to reach thermal equilibrium and for the onboard Intertial Measurement Unit (IMU) to get a fix on the sensor's position and attitude. At the beginning of each set of flights the Pilot in Command (PIC) would perform a manual takeoff and IMU calibration maneuvers (straight-and-level flight and figure-eights) as per Phoenix LiDAR System's recommended procedures. Once the manuevers were completed and the Sensor Operator determined IMU attitude and position uncertainties were below threshold (0.003- typical values ranged an order of magnitude lower) the PIC would begin the automated waypoint mission via Litchi. During flight, the Sensor Operator would ensure the scanner was operational, that the IMU uncertainties were below margin, and address any potential error messages. In the event of errors, the PIC would bring the sUAS back and the section would be re-surveyed after the issues were addressed.

Processing Methods: The raw flightlines were fused using Phoenix SpatialExplorer 4.0.3 to include only the straight-and-level flightlines over the region of interest. The output were individual flightline .las point clouds conforming to LAS 1.4 format. These flightlines were then passed through a noise filter using LasNoise to remove any "birds" or unwanted noise. Using LasTools these noise-removed flightlines were then tiled, classified into ground/non-ground points, and rasterized into 0.25-meter Digital Surface Models (DSM) containing all points and Bare-Earth Digital Elevation Models (DEM) containing only ground-classified points. These tiled raster outputs were then mosiaced together in ArcGIS Pro.

Please reach out to Michael Kalua (mkalua@ucmerced.edu) for any questions about this dataset.

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.

Area Covered: World

What can I do with this layer?
The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.


It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.

Attribute Information

• Latitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?
• Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.
• Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?
• Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.
  
• Acquisition Date: Derived Date/Time field combining Date and Time attributes.
• Satellite: Whether the detection was picked up by the Terra or Aqua satellite.
• Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.
• Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.
• Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.
• FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).
• DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.
• Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.

This map is provided for informational purposes and is not monitored 24/7 for accuracy and

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC) oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Map which allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC)oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Mapwhich allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire. Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable. Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC).  Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute. Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations. Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed. Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed. Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires. Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives. Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities. IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers. Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands. Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created. GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event. Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned. Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters) RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters. This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This feature layer spatially represents DriveNC//NCDOT’s TIMS incident data feed by Road Condition. The TIMS Incidents data contains the general location of and details about incidents that affect or will affect travel on roads maintained by the North Carolina Department of Transportation.This hosted feature layer view is intended for public viewing.NCDOT TIMS Incidents Points - Contains a point reference for all incidents, point and line.NCDOT TIMS Incidents Lines - Lines representing linear incidents. Generally, only select incidents types and road closed conditions will be represented as lines. A point feature will represent the same incident.This data includes all incidents including those recorded on concurrent routes. To remove these from the data, filter where "CreatedFromConcurrent = False".The data is provided through an automated routine that pulls data from the TIMS geojson feed every 5 minutes. Note that the data may disappear for a few moments while being refreshed.The feature layer contains all incidents; current and future. To only view current incidents in your web map, create a filter using the "StartDate" field. For example, filter by Start Date "in the last" 6 years. Note: DateTime fields are in UTC (as indicated in the field name). Text fields contain data/time values in Eastern Time.

Attributes/Fields:

Attribute/Field 


Description/Comments

Id

Unique Id of the Incident

Location

General description of the incident location.

Road

The road on which the incident occurred.

CommonName

Common name of the road on which the incident occurred or will occur

Direction

Direction of traffic impacted. Values include: North South East West All Inner Out

RouteType

Type of Route. Values include: Interstate US Route NC Route Secondary Road

RouteSuffix

Route Suffix. Values include: Alternate Business Bypass Connector Express Truck Toll

RouteId

NCDOT route id

City

Name of the nearest city to the incident.

CountyId

County number in which the incident occurred. Values from 1 to 100, where Alamance is 1 and Yancey is 100.

CountyName

Name of the county in which the incident occurred.

Division

Division number

EventId

Id of the Event designation. If the field is blank, the incident is not associated with an event.

EventName

Name of the Event designation. If the field is blank, the incident is not associated with an event.

Reason

Additional information about the incident.

IncidentType

Type of incident. Values include: Emergency Road Work Construction Night Time Construction Weekend Construction Maintenance Night Time Maintenance Road Obstruction Vehicle Crash Disabled Vehicle Congestion Signal Problem Weather Event Fog Fire Special Event Other Reported Incident

Severity

Severity of the incident. Values include: 1 = Low Impact 2 = Medium Impact 3 – High Impact

Condition

Road condition caused by the incident. Congestion Lane Closed Lane Shift Lanes Closed Lanes Narrowed Moving Closure Permanent Road Closure Ramp Closed Rest Area Closed Road Closed Road Impassable Shoulder Closed Lane Narrowed Ramp Lane Closed Ramp Lane Narrowed Road Closed with Detour

Detour

The detour or alternate route instructions

LanesClosed

The total number of lanes closed due to the incident

LanesTotal

The total number of lanes affected by the incident

DriveNCLink

Link to the DriveNC web page for the incident

StartDateUTC

Incident start date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours. To calculate EDT subtract 4 hours.

EndDateUTC

Incident end date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours.

LastUpdateDateUTC

Last update date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours

TIMCCreationDateUTC

TIMS Creation date/time in UTC. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours.To calculate EDT subtract 4 hours

StartDateET

Incident Start Date in ET (EDT or EST).This is a text field suitable for display. Use the UTC fields for filtering on time.

StartTimeET

Incident Start Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndDateET

Incident End Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndTimeET

Incident End Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateDateET

Last Update Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateTimeET

Last Update Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationDateET

TIMS Creation Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationTimeET

TIMS Creation Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

Latitude

Latitude

Longitude

Longitude

Note: Details about the incident are available through the NCDOT TIMS site. You can link directly to the incident details by combining https://tims.ncdot.gov/TIMS/IncidentDetail.aspx?id= and the TimsId/Incident ID. Note: The Last Modified and Created dates apply to this item entry in GO!NC/ArcGIS Online and may not reflect the actual dates of the data or map service itself.

This filtered version of the layer represents all IRWIN-tracked fires that originated in California or are are less than 100% contained.This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident ComplexArea Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

In addition to displaying earthquakes by magnitude, this service also provide earthquake impact details. Impact is measured by population as well as models for economic and fatality loss. For more details, see: PAGER Alerts. Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cache-able relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cache-able. Update Frequency: Events are updated as frequently as every 5 minutes and are available up to 30 days with the following exceptions:Events with a Magnitude LESS than 4.5 are retained for 7 daysEvents with a Significance value, "sig" field, of 600 or higher are retained for 90 days In addition to event points, ShakeMaps are also provided. These have been dissolved by Shake Intensity to reduce the Layer Complexity.The specific layers provided in this service have been Time Enabled and include:Events by Magnitude: The event’s seismic magnitude value.Contains PAGER Alert Level: USGS PAGER (Prompt Assessment of Global Earthquakes for Response) system provides an automated impact level assignment that estimates fatality and economic loss.Contains Significance Level: An event’s significance is determined by factors like magnitude, max MMI, ‘felt’ reports, and estimated impact.Shake Intensity: The Instrumental Intensity or Modified Mercalli Intensity (MMI) for available events. For field terms and technical details, see: ComCat Documentation Alternate SymbologiesVisit the Classic USGS Feature Layer item for a Rainbow view of Shakemap features. RevisionsAug 14, 2024: Added a default Minimum scale suppression of 1:6,000,000 on Shake Intensity layer. Jul 11, 2024: Updated event popup, setting "Tsunami Warning" text to "Alert Possible" when flag is present. Also included hyperlink to tsunami warning center. Feb 13, 2024: Updated feed logic to remove Superseded events This map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to USGS source for official guidance. If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC)oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Mapwhich allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

*****PLEASE NOTE: THIS SERVICE IS NOT CONSIDERED AUTHORITATIVE*****For authoritative case and death counts please see the data in the Department of Public Health's LA County COVID-19 Surveillance Dashboarddashboard.publichealth.lacounty.gov/covid19_surveillance_dashboard/Several tables of the data are made available to download, including the current daily count, by selecting a table from the menu on the left side of the dashboard and clicking the "Download his table" button at the top of the table's page.*********************************************************************************This is the hosted feature layer VIEW for Historic case counts that is being updated from the SDE data source through automated scripting.Additionally, this feature layer contains the Accumulated Cases and Death counts. To just view the accumulated totals, apply a filter for Community = County of Los Angeles.The script runs daily at 8pm and finishes around 8:15pm.This view layer replaces the older version. Please update your data source for historic or accumulated COVID-19 cases with this feature layer and remove the older version from your webmaps and applications. Please contact the GIS Unit with questions at gis@ceooem.lacounty.gov.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC)oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Mapwhich allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC)oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Mapwhich allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC)oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Mapwhich allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.