Attachment regarding request by Mark Ashness, P.E. on behalf of Flying Crown Ranch, LLC Construction Plan review and approval of The Retreat on Haw River Phase 1 and 2, consisting of 177 lots on 375.9 acres, located off Bynum Road, parcels 3027, 87217, and 81274.

In the Delta Anatomy Mapping Project, all levee anatomies were delineated using slope grids built from available 2007 Delta LIDAR data points. LIDAR data points were converted to digital elevation models and subsequently into slope grids. Thresholds were identified that capture the levee crown, levee landside, levee waterside, ramps and toe ditches. Visual interpretations of slope thresholds were used in conjunction with heads-up digitizing to maintain smooth boundaries at a scale of 1:550. The delineation thresholds were derived from a combination of mapping scale, slope grid resolution and slope thresholds used for each anatomy classification. All anatomy has gone through internal quality control processes to ensure a minimum accuracy of +/- 3 feet.Anatomy data was further reviewed and tested by DWR for compliance with an interpretive mapping standard of 80% accuracy. Once the levee anatomy was created and accepted, isolation and export of the levee crown was used in conjucture with ET Geowizards to collapse the crown to a singular centerline which details the levee route. This data depicts the levee anatomy at the time of the LiDAR survey (2007) and are only accurate for that time. Users should be aware that temporal changes may have occurred since this data set was created and some parts of this data may no longer represent actual surface conditions. Changes in some linework and attribution were performed by CA DWR Division of Engineering in September, 2018, and current version was posted to DWR GIS Atlas at that time

Data type: multipoint shape file (ESRI format) of 20 sample plots

Sampling design: 20 sample plots (10 upper treelines + 10 lower treelines) along the Toiyabe range of Nevada, US

Data sources and methods: on-screen photointerpretation of high-resolution (30 cm) aerial photographs (Bing Maps Microsoft Virtual Earth; year 2012) available from the ArcGIS Online service (ESRI, 2012). The approach consists of a manual segmentation of the image at a map scale ranging between 1:400 and 1:600 to identify tree crown polygons, and subsequently the canopy cover and the centroid of each detected tree. The minimum mapping unit (MMU) adopted in the image analysis was 0.78 m2 corresponding to a crown radius of at least 0.5 m.

Validation: The 20 vector maps resulting from this process were validated through accuracy assessment by ground control plots (GCPs) collected in the field during June and July of 2015. The accuracy of the image classification was obtained by calculating the number of correctly classified trees (matches =M), trees detected in the image but absent on the field (false presence = FP) and trees present on the field but not detected on the image (false absence = FA). The final accuracy, calculated on a total of 104 ground control points (GCPs) was 83% total matches, 10% false absences and 7% false presences.

The 'Stems' data are from an individual tree segmentation (Swetnam and Falk 2014) derived from the 2010 snow-off lidar and biomass-carbon allometric equations. The purpose of the dataset is to evaluate the distribution of aboveground carbon across an elevation gradient in temperature and precipitation.

The '10m Topo points' data are derived from a bare earth digital elevation model (DEM) generated from the 2010 snow-off lidar flight, these include the topographic metrics and the biomass-carbon for each pixel derived from the sum of STEMS. The purpose of the dataset is to evaluate the distribution of aboveground carbon across an elevation gradient in temperature and precipitation.

A total of three catchments in Boulder Creek were analyzed: Como Creek, Gordon Gulch, and Betasso Preserve.

Significance Statement: Forest carbon reservoirs in complex terrain along an elevation-climate gradient spanning an 11 Celsius range in mean annual temperature (MAT) and a 50 cm yr-1 range in mean annual precipitation (MAP) did not exhibit the expected response of increasing in size with greater MAP and idealized MAT. Within catchments, the distribution of mean and peak carbon storage doubled in size for valleys versus ridges. These results suggest spatial variations in carbon storage relate more to topographically mediated water availability, as well as aspect (energy-balance) and topographic curvature (a proxy for soil depth and depth to ground water), than elevation-climate gradients. Consequently, lateral redistribution of precipitation across topographic position may either moderate or exacerbate regional climatic controls over ecosystem productivity and tree-level responses during drought.

This web mapping application is meant for public use. It displays the control monuments used in legal land surveys and includes NAD83 CSRS values in addition to the condition of the monuments. There are three types of survey monuments included; Conventional Survey monuments, GPS and High Precision GPS. Section 65 of the Newfoundland and Labrador Lands Act states:65. (1) A person who interrupts, molests or hinders a surveyor while in the discharge of his or her duties, or knowingly or willfully pulls down, defaces, alters or removes a mound, post, monument or control survey marker erected, planted or placed in a survey under this Part is guilty of an offence and liable on summary conviction to a fine not exceeding $500 or imprisonment for a period not exceeding 3 months.

Forest Ecosystem Dynamics (FED) Project Spatial Data Archive: Howland Township Forest Map

The Biospheric Sciences Branch (formerly Earth Resources Branch) within the Laboratory for Terrestrial Physics at NASA's Goddard Space Flight Center and associated University investigators are involved in a research program entitled Forest Ecosystem Dynamics (FED) which is fundamentally concerned with vegetation change of forest ecosystems at local to regional spatial scales (100 to 10,000 meters) and temporal scales ranging from monthly to decadal periods (10 to 100 years). The nature and extent of the impacts of these changes, as well as the feedbacks to global climate, may be addressed through modeling the interactions of the vegetation, soil, and energy components of the boreal ecosystem.

The Howland Forest research site lies within the Northern Experimental Forest of International Paper. The natural stands in this boreal-northern hardwood transitional forest consist of spruce-hemlock-fir, aspen-birch, and hemlock-hardwood mixtures. The topography of the region varies from flat to gently rolling, with a maximum elevation change of less than 68 m within 10 km. Due to the region's glacial history, soil drainage classes within a small area may vary widely, from well drained to poorly drained. Consequently, an elaborate patchwork of forest communities has developed, supporting exceptional local species diversity.

This data layer contains forest polygons with information on cover type, volume, and crown closure for both the forest overstory and understory for the Township of Howland located in Penobscot County, Maine. The map was digitized, projected and differentially corrected using Global Positioning System points. Forest types were determined by delineation from color infrared photographs. Note that the USGS records show that the orthophotoquads from which the data were digitized are in the Transverse Mercator projection. The printed map grid on both Howland and Edinburg maps is in the Universal Transverse Mercator projection. So, although the Edinburg map states that base map and control are from a Polyconic projection, (the Howland does not mention projection) the original base maps were assumed to be in the Transverse Mercator.

Forest Ecosystem Dynamics (FED) Project Spatial Data Archive: Edinburg Township Area Cuts Map

The Biospheric Sciences Branch (formerly Earth Resources Branch) within the Laboratory for Terrestrial Physics at NASA's Goddard Space Flight Center and associated University investigators are involved in a research program entitled Forest Ecosystem Dynamics (FED) which is fundamentally concerned with vegetation change of forest ecosystems at local to regional spatial scales (100 to 10,000 meters) and temporal scales ranging from monthly to decadal periods (10 to 100 years). The nature and extent of the impacts of these changes, as well as the feedbacks to global climate, may be addressed through modeling the interactions of the vegetation, soil, and energy components of the boreal ecosystem.

The Howland Forest research site lies within the Northern Experimental Forest of International Paper. The natural stands in this boreal-northern hardwood transitional forest consist of spruce-hemlock-fir, aspen-birch, and hemlock-hardwood mixtures. The topography of the region varies from flat to gently rolling, with a maximum elevation change of less than 68 m within 10 km. Due to the region's glacial history, soil drainage classes within a small area may vary widely, from well drained to poorly drained. Consequently, an elaborate patchwork of forest communities has developed, supporting exceptional local species diversity.

This data layer contains harvested forest polygons with information on cover type, volume, cut date, cut type, and crown closure for the Township of Edinburg located in Penobscot County, Maine. The map was digitized, projected and differentially corrected using Global Positioning System points. Forest types were determined by delineation from color infrared photographs.

Note that the USGS records show that the orthophotoquads from which the data were digitized are in the Transverse Mercator projection. The printed map grid on both Howland and Edinburg maps is in the Universal Transverse Mercator projection. So, although the Edinburg map states that base map and control are from a Polyconic projection, (the Howland does not mention projection) the original base maps were assumed to be in the Transverse Mercator.

Purpose: To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 1-meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.Product: These are Digital Elevation Model (DEM) data for Northern Maine as part of the required deliverables for the Crown of Maine 2018 QL2 LiDAR project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 1-meter hydro-flattened raster DEM.This lidar data set includes unclassified swath LAS 1.4 files, classified LAS 1.4 files, hydro and bridge breaklines, hydro-flattened digital elevation models (DEMs), and intensity imagery. Geographic Extent: 4 partial counties in Northern Maine, covering approximately 6,732 total square miles. Dataset Description: The Crown of Maine 2018 QL2 LiDAR project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.71 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.2. The data were developed based on a horizontal projection/datum of NAD 1983 (2011), UTM Zone 19, meters and vertical datum of NAVD 1988 (GEOID 12B), meters. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 8,056 individual 1,500-meter x 1,500-meter tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1,500-meter x 1,500-meter schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in spring of 2018 and 2019, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Quantum Spatial, Inc. utilized a total of 150 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 256 independent accuracy checkpoints, 149 in Bare Earth and Urban landcovers (149 NVA points), 107 in Tall Weeds categories (107 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.

This layer includes all Crown Land and Properties managed by LINZ which have been identified spatially and can include properties managed by LINZ on behalf of other agencies. The attributes in this dataset are derived from the National Property and Land Information System (NaPALIS), which is a centralised database for all Land Information New Zealand (LINZ) and Department of Conservation (DOC) administered land.

The boundaries of many properties are linked to the applicable Landonline Primary Parcel(s), but in some cases the boundaries may have been drawn in as unsurveyed parcels to varying degrees of accuracy. As such please note that the boundaries are indicative only. The layer excludes any LINZ managed properties which do not have an identified location or extent.

More information on Crown Property can be found under the Crown Property section on the LINZ Website. A subset of Crown Property can be found in the South Island Pastoral Leases layer. A table of Property associations to Primary Parcels is published in the LDS here.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services

Date :First published: January 19, 2017Data Captured: N/ALast Updated: Updates are based on the availability of data.Creator: Taranaki Regional Council (TRC)Publisher: TRCSubject: Marae, Maori, IwiPurpose: To be utilized for Open Data within the Web Map on Local Maps.Language: EnglishFormat: Feature Layer (hosted)Type: Vector (Polygon)Coverage: Top (Latitude) -38.668783, Bottom (Latitude) -39.879076, Left (Longitude) 173.745239, Right (Longitude) 175.103509Full ExtentXMin: 1642470.7543000001YMin: 5559412.4576XMax: 1783106.8887999998YMax: 5796276.5538Spatial Reference: 2193 (2193)Spatial Coverage: Taranaki Region, New ZealandProjection: New Zealand Transverse Mercator 2000 (NZTM2000)Description: This dataset displays Iwi Statutory Acknowledgements (SA) in the Taranaki Region, depicting redress commitments outlined in Deeds of Settlement. Redress details are captured from signed Deeds of Settlement to reflect commitments made as of the settlement date. Redress sites are sourced directly from shapefiles created for Deed of Settlement plans where available. Other sources include Land Information cadastral parcels or Department of Conservation properties listed in redress tables. The Deeds of Settlement redress is categorized into 16 types according to Te Arawhiti definitions, grouping similar types of redress. Data attributes include Iwi name, Deed date, Settlement date, Redress type, Plan number, Site name, Leaseback, Parcel ID, Legal description, comments, etc. This feature layer is used for Web Maps in Local Maps, covering the Taranaki Region. "Note: The data is as at settlement date for each settlement and will not reflect any subsequent transfer of land from the Iwi to private individuals." (Te Arawhiti, 02 Sep 2024)Attributes:Iwi Name: Name of the Iwi named in the settlement.Deed_Date: Date on which the Deed of Settlement was signed.Settlement_Date: Date generally 20 business days after the settlement legislation comes into effect, or the date/time frame specified in the legislation.Redress_Type: Type of redress as described in the Deed of Settlement.Plan_Number: Plan number of the document supporting the definition of the redress in the Deed of Settlement.Site_Name: Name of the redress site as described in the Deed of Settlement.Leaseback: Indicates if a leaseback to the Crown agency is required as part of the conditions of transfer (Yes/No).Parcel_ID: Land Information New Zealand (LINZ) parcel ID.Legal_Description: Legal description of the parcel(s) describing the redress.Comments: Additional information regarding the redress, including shared redress details and amendments to Deeds.Redress_Category: Categories of redress used to group related types of redress for symbolization.Originating Agency: Agency administering the property at the time of settlement.PropertyID: Te Arawhiti settlement database property ID for Crown land held in the Te Arawhiti settlement database, for Te Arawhiti purposes only.Fields:OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )Parcel_ID ( type: esriFieldTypeDouble, alias: PARCEL_ID )Shape ( type: esriFieldTypeGeometry, alias: Shape )Shape_Area ( type: esriFieldTypeDouble, alias: Shape.STArea() )Shape_Length ( type: esriFieldTypeDouble, alias: Shape.STLength() )Iwi ( type: esriFieldTypeString, alias: Iwi, length: 150 )Deed_Date ( type: esriFieldTypeDate, alias: Deed_Date, length: 8 )Settlement_Date ( type: esriFieldTypeDate, alias: Settlement_Date, length: 8 )Redress_Type ( type: esriFieldTypeString, alias: Redress_Type, length: 255 )Plan_Number ( type: esriFieldTypeString, alias: Plan_Number, length: 30 )Site_Name ( type: esriFieldTypeString, alias: Site_Name, length: 200 )Legal_Description ( type: esriFieldTypeString, alias: Legal_Description, length: 255 )Area ( type: esriFieldTypeDouble, alias: SDEData_NZTM.SDEADMIN.IWI_Statutory_Acknowledgements.Area )Redress_Category ( type: esriFieldTypeString, alias: Redress_Category, length: 50 )OriginalName ( type: esriFieldTypeString, alias: OriginalName, length: 250 )RFRTerm_Years ( type: esriFieldTypeDouble, alias: RFRTerm_Years )DSPTerm_Years ( type: esriFieldTypeDouble, alias: DSPTerm_Years )LegislationPassed ( type: esriFieldTypeDate, alias: LegislationPassed, length: 8 )Relation: https://trcnz.maps.arcgis.com/home/item.html?id=9a30ea3d3b4a43d18077ba46a5a3af98Original Data from Te Arawhiti https://services9.arcgis.com/eNX73FDxjlKFtCtH/arcgis/rest/services/Treaty_Settlement_Layers/FeatureServerSource: Data were sourced from Te Arawhiti, Land Information New Zealand (LINZ), and the Department of Conservation (DOC), and were subsequently clipped to SA boundaries within the Taranaki Region. Data was source from Te Arawhiti (https://takutai-moana-data-portal-maca-nds.hub.arcgis.com/datasets/maca-nds::dos/explore?location=-39.191267%2C173.807622%2C11.79). The original dataset includes Areas of Interest, Right of First Refusal (RFR) areas, and a Deed of Settlement (DOS) layer, with the latter able to be split into various categories for mapping. It reflects the redress committed in Deeds of Settlement (DOS), based on the signed agreements and capturing information as of each settlement date, excluding any subsequent transfers of land. Redress sites are sourced from Deed of Settlement (DOS) shapefiles, Land Information cadastral data, or Department of Conservation (DOC) properties. The data is grouped into 16 categories defined by Te Arawhiti, with attributes such as Iwi, Deed and Settlement dates, redress type, plan numbers, and legal descriptions. The data also includes details like leasebacks, comments, and the originating agency. Publication and distribution have been managed by TRC since January 19, 2017. This item was created by the TRC GIS Team (check the item updated date on ArcGIS Online). Identifier: 8a7c04a2d4074c2ba5d3d62405269c2bVersion Control: May 26, 2025 (Dataset source: Te Arawhiti https://takutai-moana-data-portal-maca-nds.hub.arcgis.com/datasets/maca-nds::dos/explore?location=-39.191267%2C173.807622%2C11.79) - Source Date - Info Updated on September 2, 2024 | Data Updated on May 02, 2025 | Published Date on September 2, 2024.Previous version:January 13, 2025 (Dataset source: Te Arawhiti https://takutai-moana-data-portal-maca-nds.hub.arcgis.com/datasets/maca-nds::dos/explore?location=-39.191267%2C173.807622%2C11.79) - Source Date - Info Updated on September 2, 2024 | Data Updated on January 10, 2025 | Published Date on September 2, 2024.October 16, 2023 (Dataset source: Te Arawhiti, Land Information New Zealand (LINZ), and the Department of Conservation (DOC))

This web map shows the current wildfires and fire danger zones within Canada. The layers used within this web map are Esri Canada's wildfire live feature services that are updated daily along with NRCan's current fire danger WMS. A description of each layer can be found below along with the link to their respective items on ArcGIS Online.***The live feature services within this webmap are now paused and will not receive data updates until next fire season. April 1st, 2025 is the predicated date for this service to resume***Active Wildfires in CanadaReported active fire locations are updated daily as provided by fire management agencies (provinces, territories and Parks Canada). The fires data is managed through a national Data Integration Project (DIP) coordinated by the Canadian Interagency Forest Fire Centre (CIFFC) and Natural Resources Canada with participation from all partner agencies. The active fires data includes attributes for agency, fire name, latitude, longitude, start date, fire size (ha) and stage of control (fire status). Possible values for stage of control include: OC (Out of Control), BH (Being Held), UC (Under Control), EX (Out).Supplemental InformationThe national Data Integration Project (DIP) is coordinated by the Canadian Interagency Forest Fire Centre (CIFFC) and Natural Resources Canada with participation from all partner agencies. This initiative focuses on development and implementation of data standards and enabling the exchange and access of national fire data. More details are available in the CIFFC IM/IT Strategy, available at: https://ciffc.ca/publications/general-publications.Feux de végétation actifs au CanadaLes positions rapportées des feux de végétation actifs sont mises à jour quotidiennement d'après les données fournies par les agences de gestion des feux (provinces, territoires et Parcs Canada). Les données sur les feux sont gérées dans le cadre d'un Projet d'intégration de données national coordonné par le Centre interservices des feux de forêt du Canada (CIFFC) et par Ressources naturelles Canada, avec la participation de tous les organismes partenaires. Les données sur les feux actifs comprennent les champs d'attributs des agences, le nom du feu, la latitude, la longitude, le début du feu, la taille du feu (ha) et le stade de contrôle (état du feu). Les valeurs possibles pour le stade de contrôle sont les suivantes : OC (out of control/hors de contrôle), BH (being held/contenu), UC (under control/maîtrisé) et EX (out/éteint).Renseignements complémentairesLe Projet d'intégration de données national est coordonné par le CIFFC et par Ressources naturelles Canada, avec la participation de tous les organismes partenaires. Cette initiative a pour but d'élaborer et de mettre en œuvre des normes de données, ainsi que de rendre possible l'accès aux données nationales sur les feux et l'échange de ces données. On trouvera plus de détails à ce sujet dans la Stratégie de GI/TI du CIFFC, à l'adresse suivante : https://ciffc.ca/publications/general-publicationsActive Wildfire Perimeters in CanadaThis dataset displays active wildfire perimeters derived from hotspots identified in satellite imagery provided by the Canadian Wildland Fire Information System (CWFIS) and Natural Resources Canada (NRCan) updated every 3 hours. || Ce jeu de données, mis à jour toutes les trois heures, affiche les périmètres de feux de forêt actifs dérivés des points chauds relevés dans l’imagerie satellite fournie par le Système canadien d’information sur les feux de végétation (SCIFV) et Ressources naturelles Canada (RNCan).Wildfire Smoke Forecast in CanadaThis layer displays forecasted wildfire smoke across Canada sourced from BlueSky Canada's FireSmoke Canada app, updated every 6 hours. The wildfire smoke layer consists of hourly concentrations of particulate matter 2.5 microns and smaller (PM2.5) in units of micrograms per meter cubed (µg/m3) observed at ground level from wildfires. It is an approximation of when and where wildfire smoke events may occur over the next two days. This layer is sourced from BlueSky Canada's FireSmoke Canada app.Current Fire DangerFire Danger is a relative index of how easy it is to ignite vegetation, how difficult a fire may be to control, and how much damage a fire may do. Fire Danger is a reclassification of the CFFDRS fire weather index (FWI) which is a numeric rating of fire intensity.These general fire descriptions apply to most coniferous forests. The national fire danger maps show conditions as classified by the provincial and territorial fire management agencies. Choice and interpretation of classes may vary between provinces. For fuel-specific fire behavior, consult the Fire Behavior Prediction maps.• Low: Fires likely to be self-extinguishing and new ignitions unlikely. Any existing fires limited to smoldering in deep, drier layers.• Moderate: Creeping or gentle surface fires. Fires easily contained by ground crews with pumps and hand tools.• High: Moderate to vigorous surface fire with intermittent crown involvement. Challenging for ground crews to handle; heavy equipment (bulldozers, tanker trucks, aircraft) often required to contain fire.• Very High: High-intensity fire with partial to full crown involvement. Head fire conditions beyond the ability of ground crews; air attack with retardant required to effectively attack fire's head.• Extreme: Fast-spreading, high-intensity crown fire. Very difficult to control. Suppression actions limited to flanks, with only indirect actions possible against the fire's head.Forecasted weather data provided by Environment Canada. More information about forecasted weather is available at https://cwfis.cfs.nrcan.gc.ca/background/dsm/fwiMore information about the Canadian Forest Fire Weather Index (FWI) System is available at https://cwfis.cfs.nrcan.gc.ca/background/summary/fwiMaps are produced using Spatial Fire Management System and are updated multiple times per day.Maps updated daily, year-round.Supplemental InformationThe Canadian Forest Fire Danger Rating System (CFFDRS). is a national system for rating the risk of forest fires in Canada.Forest fire danger is a general term used to express a variety of factors in the fire environment, such as ease of ignition and difficulty of control. Fire danger rating systems produce qualitative and/or numeric indices of fire potential, which are used as guides in a wide variety of fire management activities.The CFFDRS has been under development since 1968. Currently, two subsystems–the Canadian Forest Fire Weather Index (FWI) System and the Canadian Forest Fire Behavior Prediction (FBP) System–are being used extensively in Canada and internationally.Risque d'incendie actuelLe risque d'incendie est un indice relatif indiquant le niveau de facilité pour allumer un incendie de végétation, le niveau de difficulté qu'un incendie peut demander pour être contrôlé ainsi que la quantité de dommages qu'un incendie peut causer.Ces descriptions générales des incendies s'appliquent à la plupart des forêts de conifères. Les cartes nationales sur le danger d'incendie illustrent les conditions telles qu'elles sont classées par les agences provinciales et territoriales de gestion des feux. Le choix et l'interprétation des classes peuvent varier entre les provinces. En ce qui a trait au comportement des incendies en regard du combustible spécifique, veuillez consulter les cartes de prédiction du comportement des incendies.• Faible: Incendie possiblement auto-extincteur; de nouveaux allumages sont invraisemblables. Tout incendie existant est limité à couver dans des couches profondes plus sèches.• Modéré: Incendie de surface rampant modéré. Il est facilement circonscrit par les équipes au sol munies de pompes et d'outils manuels.• Élevé: Incendie de surface modéré à vigoureux avec implication intermittente des cimes. Pose des défis aux équipes chargées de le combattre sur le terrain; les équipements lourds (bouteurs, camions-citernes à eau et avions) sont souvent requis pour contenir l'incendie.• Très élevé: Incendie de forte intensité avec implication partielle ou complète des cimes. Les conditions au front de l'incendie sont au-delà de la capacité des équipes sur le terrain à y faire face; les attaques aériennes avec largage de produits ignifugeants sont requises pour combattre effectivement le front de l'incendie.• Extrême: Feu de cimes à forte intensité et à propagation rapide. Très difficile à contrôler. Les actions de suppression sont limitées aux flancs alors que seules des actions indirectes sont possibles au front de l'incendie.Prévisions météorologiques fournies par Environnement Canada. Pour de plus amples renseignements sur les prévisions, consultez la section Renseignements généraux.De plus amples informations sur la Méthode canadienne de l'indice Forêt-Météo (IFM) sont disponibles à la rubrique Renseignements généraux.Les cartes sont produites à l'aide du Système de gestion spatiale des feux de forêt et sont mises à jour plusieurs fois par jour.Les cartes sont mises à jour quotidiennement, tout au long de l'année l'année.Renseignements complémentairesLa Méthode canadienne d'évaluation des dangers d'incendie de forêt (MCEDIF) est une méthode nationale pour classer le risque d'incendie de forêt au Canada.Le danger d'incendie de forêt est un terme général employé pour exprimer une diversité de facteurs dans les conditions de brûlage tels que la facilité d'allumage et la difficulté de contrôle. Les méthodes d'évaluation du danger d'incendie génèrent des indices qualitatifs ou numériques du potentiel d'incendie qui sont utilisés comme guides dans une grande variété d'activités de gestion des incendies de forêt.La MCEDIF est en cours d'élaboration depuis 1968. En ce moment, deux sous-systèmes – la Méthode

Light Poles is a Point FeatureClass representing light posts distributed throughout the city. It is primarily used for identifying and tracking assets and necessary maintenance and repairs. The layer is updated as needed by the GIS division and by field staff. Light Poles has the following fields:

AssetID: Cupertino maintained GIS primary key type: String, length: 20, domain: none

Location: Further description of the location type: String, length: 50, domain: none

Status: The active or construction status of the asset in the field type: String, length: 20, domain: pwStatus domain values:['Abandoned', 'Proposed', 'Auction', 'Denied', 'Active', 'Removed', 'Not Connected']

OwnedBy: Organization which owns the asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

MaintainedBy: Organization who is responsible for maintenance of asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

Rotation: Field used for assigning rotation degree in Maplex Labeling Engine type: Double, length: 8, domain: none

BadgeNumber: The badge number assigned to the light pole type: String, length: 6, domain: none

ServiceID: Service identification number type: String, length: 20, domain: none

PoleType: Field describing the type of pole found at the location type: String, length: 20, domain: utilLightPoleType domain values:['Mast Arm Pole', 'Taper 4 Bolt', '33', 'PBP Pole', 'Taper 3 Bolt', '1A', 'Type15', '1B', 'Taper 1 Bolt', 'Top Mount', 'Flute 1 Bolt', 'Taper 2 Bolt']

PoleMaterial: Field indicating what material the pole is made of type: String, length: 20, domain: utilLightPoleMaterial domain values:['Steel', 'Concrete', 'Aluminium', 'Galvanized', 'Wood']

PoleHeight: The height of the light pole type: SmallInteger, length: 2, domain: none

ArmLength: The length of the light pole arm - in feet type: SmallInteger, length: 2, domain: utilLightArmLength domain values:["65'", "3'", "6'", "8'", "10'", "12'", "45'", "15'", "40'", "50'", "35'", "20'", "55'", "25'", "60'", "30'"]

LightFunction: Field indicating the function of the light pole type: String, length: 20, domain: utilLightFunction domain values:['Street Light', 'Tennis Court Light', 'Parking Lot Light', 'Park Light', 'Flood Light', 'Safety Light']

NumberOfHeads: Field indicating the number of heads on the light pole type: SmallInteger, length: 2, domain: utilLampNumberOf domain values:['1', '2', '3', '4']

LampType: Field identifying the type of lamp used in the light pole type: String, length: 10, domain: utilLampType domain values:['High Pressure Sodium', 'Mercury Vapor', 'LED', 'Metal Halide', 'Inductive']

Wattage: Field indicating the number of watts type: SmallInteger, length: 2, domain: none

Volts: Field indicating the number of volts type: SmallInteger, length: 2, domain: utilLampVoltage domain values:['120V', '240V', '480V', '277V']

Base: Field indicating the type of base that light pole uses type: String, length: 10, domain: utilLightBase domain values:['Anchor', 'Buried']

Fixture: Field indicating which type of fixture style the light pole has type: String, length: 20, domain: utilLightFixture domain values:['Park Dome', 'Ornamental', 'Cobra', 'Shoe Box']

ControlType: Field indicating what type of control method is used type: String, length: 20, domain: utilLightControlType domain values:['Time Clock', 'Photo Electronic Control']

HasBeacon: Field indicating whether or not the light pole has a beacon type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsFused: Field indicating whether or not the light pole is fused type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsUnderground: Field indicating if the light pole is secured underground type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsMetered: Field indicating whether or not the light pole is metered type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasStencil: Field indicating whether or not the light pole has a stencil type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasSticker: Field indicating whether or not the light pole has a sticker type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

RateSchedule:

type: String, length: 10, domain: utilLightRateSchedule domain values:['LS1-F1', 'LS1-F', 'LS1-E', 'LS1-B', 'LS1-C', 'LS1-A', 'LS2-A']

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none

POINT_X: The X coordinate of the light pole type: Double, length: 8, domain: none

POINT_Y: The Y coordinate of the light pole type: Double, length: 8, domain: none

NoVehicleHds: Field indicating the number of vehicle heads on the light pole type: SmallInteger, length: 2, domain: trafNoOfVehHeads NoPedHds: Field indicating the number of pedestrian heads on the light pole type: SmallInteger, length: 2, domain: trafNoOfPedHeads domain values:['0', '1', '2']

NoPedButtons: Field indicating the number of pedestrian buttons on the light pole type: SmallInteger, length: 2, domain: trafNoOfPedButtons domain values:['0', '1', '2', '3']

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

IsTrafficSignal: Field indicating whether or not the light pole is used as a traffic signal type: String, length: 3, domain: shd_BooleanYesNo domain values:['Yes', 'No']

hasHandPoleCover: Field indicating whether or not the light pole has a hand pole cover type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

isStreetlight: Field indicating whether or not the light pole is designated as a streetlight type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

isSmallCell: Field indicating whether or not the light pole has a small cell attatched type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

SmallCellCarrier: Carrier associated with the small cell type: String, length: 50, domain: utilSmallCellCarrier domain values:['Mobilitie', 'ATT', 'Crown Castle', 'Verizon']

hasFlagHolder: Field indicating whether or not the light pole has a flag holder type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

FlagHolderInstallDate: The date when the flag holder was installed type: Date, length: 8, domain: none

hasSafeRouteBanner: Field indicating whether or not the light pole has a Safe Routes 2 School banner type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

The use of high-resolution LiDAR, and the products derived from it, allow for levee anatomy to be captured for the surveyed area. The resulting data is a catalog of precise levee location and components. This data can further be used for levee maintenance and management, flood modeling and prediction, as well as levee inventories. In the Delta Anatomy Mapping Project all levee anatomies were delineated using slope grids built from available LIDAR data points. LIDAR data points were converted to digital elevation models and subsequently into slope grids. Thresholds were identified that capture the levee crown, levee landside, levee waterside, ramps and toe ditches. Visual interpretations of slope thresholds were used in conjunction with heads-up digitizing to maintain smooth boundaries at a scale of 1:550. The delineation thresholds were derived from a combination of mapping scale, slope grid resolution and slope thresholds used for each anatomy classification. All anatomy has gone through an internal quality control process to ensure a minimum accuracy of +/- 3 feet. Anatomy was further reviewed and tested by DWR for compliance with an interpretive mapping standard of 80% accuracy. This data depicts the levee anatomy at the time of the LiDAR survey (2007) and are only accurate for that time. Users should be aware that temporal changes may have occurred since this data set was created and some parts of this data may no longer represent actual surface conditions. This version created by mapping from the 2007 Delta LIDAR. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.1, dated September 11, 2019. DWR makes no warranties or guarantees — either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be sent to GIS@water.ca.gov

Traffic Poles is a Point FeatureClass representing traffic poles in the City of Cupertino. It is primarily used as an inventory layer in Cityworks and as a reference layer. The layer is updated as needed by the Public Works Department and the GIS Division. Traffic Poles has the following fields: OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

AssetID: Cupertino maintained GIS primary key type: String, length: 20, domain: none

Location: Further description of the location type: String, length: 50, domain: none

Status: The active or construction status of the asset in the field type: String, length: 20, domain: pwStatus domain values:['Abandoned', 'Proposed', 'Auction', 'Denied', 'Active', 'Removed', 'Not Connected']

OwnedBy: Organization which owns the asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

MaintainedBy: Organization who is responsible for maintenance of asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA'] AsbuiltDate:

The completion date listed on the plans type: Date, length: 8, domain: none

Date Install:

The date of the most recent maintenance on this asset type: Date, length: 8, domain: none

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

Rotation: Field used for assigning rotation degree in Maplex Labeling Engine type: Double, length: 8, domain: none

BadgeNumber: The badge number assigned to the traffic pole type: String, length: 6, domain: none

ServiceID: Service identification number type: String, length: 20, domain: none

PoleType: Field describing the type of pole found at the location type: String, length: 20, domain: utilLightPoleType domain values:['Mast Arm Pole', 'Taper 4 Bolt', '33', 'PBP Pole', 'Taper 3 Bolt', '1A', 'Type15', '1B', 'Taper 1 Bolt', 'Top Mount', 'Flute 1 Bolt', 'Taper 2 Bolt']

PoleMaterial: Field indicating what material the pole is made of type: String, length: 20, domain: utilLightPoleMaterial domain values:['Steel', 'Concrete', 'Aluminium', 'Galvanized', 'Wood']

PoleHeight: Field indicating the height of the pole type: SmallInteger, length: 2, domain: none

ArmLength: The length of the traffic pole arm - in feet type: SmallInteger, length: 2, domain: utilLightArmLength domain values:["65'", "3'", "6'", "8'", "10'", "12'", "45'", "15'", "40'", "50'", "35'", "20'", "55'", "25'", "60'", "30'"]

LightFunction: Field indicating the function of the light on the pole type: String, length: 20, domain: utilLightFunction domain values:['Street Light', 'Tennis Court Light', 'Parking Lot Light', 'Park Light', 'Flood Light', 'Safety Light']

NumberofHeads: Field indicating the number of heads on the pole type: SmallInteger, length: 2, domain: utilLampNumberOf domain values:['1', '2', '3', '4']

LampType: Field identifying the type of lamp used in the light on pole type: String, length: 10, domain: utilLampType domain values:['High Pressure Sodium', 'Mercury Vapor', 'LED', 'Metal Halide', 'Inductive']

Wattage: Field indicating the number of watts type: SmallInteger, length: 2, domain: none

Volts: Field indicating the number of volts type: SmallInteger, length: 2, domain: utilLampVoltage domain values:['120V', '240V', '480V', '277V']

Base: Field indicating the type of base that pole uses type: String, length: 10, domain: utilLightBase domain values:['Anchor', 'Buried']

Fixture: Field indicating which type of fixture style the pole has type: String, length: 20, domain: utilLightFixture domain values:['Park Dome', 'Ornamental', 'Cobra', 'Shoe Box']

ControlType: Field indicating what type of control method is used type: String, length: 20, domain: utilLightControlType domain values:['Time Clock', 'Photo Electronic Control']

HasBeacon: Field indicating whether or not the pole has a beacon type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsFused: Field indicating whether or not the pole is fused type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsUnderground: Field indicating if the pole is secured underground type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsMetered: Field indicating whether or not the pole is metered type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasStencil: Field indicating whether or not the pipe has a stencil type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasSticker: Field indicating whether or not the pole has a sticker type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

RateSchedule:

type: String, length: 10, domain: utilLightRateSchedule domain values:['LS1-F1', 'LS1-F', 'LS1-E', 'LS1-B', 'LS1-C', 'LS1-A', 'LS2-A']

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none

POINT_X: The X coordinate of the traffic pole type: Double, length: 8, domain: none

POINT_Y: The Y coordinate of the traffic pole type: Double, length: 8, domain: none

NoVehicleHds: Field indicating the number of vehicle heads on the pole type: SmallInteger, length: 2, domain: trafNoOfVehHeads NoPedHds: Field indicating the number of pedestrian heads on the pole type: SmallInteger, length: 2, domain: trafNoOfPedHeads domain values:['0', '1', '2']

NoPedButtons: Field indicating the number of pedestrian buttons on the pole type: SmallInteger, length: 2, domain: trafNoOfPedButtons domain values:['0', '1', '2', '3']

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

IsTrafficSignal: Field indicating whether or not the pole is used as a traffic signal type: String, length: 3, domain: shd_BooleanYesNo domain values:['Yes', 'No']

hasHandPoleCover: Field indicating whether or not the pole has a hand pole cover type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

isStreetlight: Field indicating whether or not the pole is designated as a streetlight type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

isSmallCell: Field indicating whether or not the pole has a small cell attatched type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

SmallCellCarrier: Carrier associated with the small cell type: String, length: 50, domain: utilSmallCellCarrier domain values:['Mobilitie', 'ATT', 'Crown Castle', 'Verizon']

hasFlagHolder: Field indicating whether or not the pole has a flag holder type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

FlagHolderInstallDate: The date when the flag holder was installed type: Date, length: 8, domain: none

hasSafeRouteBanner: Field indicating whether or not the pole has a Safe Routes 2 School banner type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']