The Time Zones dataset was compiled on October 04, 2019 and was updated January 05, 2023 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This layer is a digital representation of the geographic boundaries of the nine time zones that cover the United States and its territories (the Atlantic, Eastern, Central, Mountain, Pacific, Alaska, Hawaii–Aleutian, Samoa, and Chamorro time zones). The U.S. Department of Transportation (DOT) oversees the Nation's time zones and the uniform observance of Daylight-Saving Time. The oversight of time zones was assigned to DOT due to the importance of time coordination for transportation related activities. The time zones were established by the Standard Time Act of 1918 and amended by the Uniform Time Act of 1966. Time zones in the U.S. are defined in the U.S. Code, Title 15, Chapter 6, Subchapter IX - Standard Time. The time zone boundaries are defined in the Code of Federal Regulations (CFR), Title 49, Subtitle A, Part 71 - Standard Time Zone Boundaries. Segments used to compile the geospatial layer were derived from the CFR’s time zone descriptions (https://www.ecfr.gov/current/title-49/subtitle-A/part-71). Descriptions consist of segments referencing administrative boundaries, infrastructure, natural features, and geodesic lines. These segments are contained in various data layers in the National Geospatial Data Asset (NGDA) portfolio, the federal government’s authoritative geospatial data repository. Referenced segments were extracted from their NGDA and then merged to form continuous boundaries. In instances where there were multiple scales for a given dataset, the largest scale or most detailed layer was used. The standard time of the Atlantic zone is the Coordinated Universal Time (UTC) minus 4 hours; Eastern zone is UTC minus 5 hours; Central zone is UTC minus 6 hours; Mountain zone is UTC minus 7 hours; Pacific zone is UTC minus 8 hours; Alaska zone is UTC minus 9 hours; Hawaii–Aleutian zone is UTC minus 10 hours; Samoa zone is UTC minus 11 hours; and Chamorro zone is UTC plus 10 hours. For more information, please visit: https://doi.org/10.21949/1519143.

Captures the boundaries of the World TZ time zones.

Actual time zone offsets are not present in this layer.

Sourced from efele.net/maps/tz/world/. Please visit this link for more information about this layer.

Note this layer differs from this one in that there is one feature (i.e. multi-polygons where appropriate) for each timezone.

Contained within the 5th Edition (1978 to 1995) of the National Atlas of Canada is a map that shows Canada's six time zones as legislated and as observed; also gives internationally accepted names and designators.

A map showing Canada's six time zones as legislated and as observed; also gives internationally accepted names and designators.

Contained within the 4th Edition (1974) of the Atlas of Canada is a plate map that shows 2 maps. The first map shows the locations of airports and aerodromes as of 1967, and also time zone boundaries. Airports and aerodromes are denoted as being an international airport, a Department of National Defense aerodrome or other airport / aerodrome and as having precision approach capability, non precision approach capability or no approach instrumentation. The length of each airport or aerodrome's runway is also indicated. The second map, at a scale of 1:35 000 000, shows the locations of water aerodromes and heliports for all of Canada.

There are six time zones in Canada. From west to east the main time zones are: Pacific, Mountain, Central, Eastern and Atlantic. The island of Newfoundland observes a sixth time: it decided to set its clock at the halfway point of its time zone or 3 hours and 30 minutes behind Greenwich time instead of four hours (which would be Atlantic time). Finally, many parts of the country do not observe the official hour, choosing instead to adopt the time in a neighbouring zone in order to facilitate trade between adjacent regions. This is particularly common in eastern British Columbia which often uses Mountain time rather than the Pacific time of the rest of the province.

Historic Boundaries for City of Pittsburgh City Council Districts

For more recent and current council district boundaries, see https://data.wprdc.org/dataset/resources/city-council-districts-2012

Our World Administrative Boundaries Database offers comprehensive postal code data for spatial analysis, including postal and administrative areas. This dataset contains accurate and up-to-date information on all administrative divisions, cities, and zip codes, making it an invaluable resource for various applications such as address capture and validation, map and visualization, reporting and business intelligence (BI), master data management, logistics and supply chain management, and sales and marketing. Our location data packages are available in various formats, including CSV, optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more. Product features include fully and accurately geocoded data, multi-language support with address names in local and foreign languages, comprehensive city definitions, and the option to combine map data with UNLOCODE and IATA codes, time zones, and daylight saving times. Companies choose our location databases for their enterprise-grade service, reduction in integration time and cost by 30%, and weekly updates to ensure the highest quality.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted geospatial data cover postal divisions for the whole world. The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Boundaries Database (Geospatial data, Map data, Polygon daa)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the map data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

Village (Neighborhood) Boundaries across the Nation

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted geospatial data cover administrative and postal divisions with up to 5 precision levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Administrative Boundaries Database (Geospatial data, Map data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the map data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

Please zoom in to a town or local area for data to display.Abstract The Historical Bushfire Boundaries Dataset (version 2) represents the aggregation of jurisdictional supplied burnt areas polygons that date from the early 1900s through to 2023 (excluding the Northern Territory). The burnt areas represent curated jurisdictional owned polygons of bushfires and prescribed (planned) burns. This dataset was produced under Work Stream 1C - Activity 3 of the National Bushfire Intelligence Capability (NBIC) , a collaborative partnership between:

Australian Climate Service CSIRO (NBIC) Geoscience Australia Emergency Management Spatial Information Network (EMSINA)

Under agreement this Project (Activity 3) will release a nationally consistent, harmonised and standardised historical bushfire boundary dataset derived from the authoritative state and territory agencies in both 2023 (this dataset) and again in November 2024.
The information released within this dataset is reflective of the data supplied by participating authoritative agencies. It may, or may not, represent all fire history within that jurisdiction. Geoscience Australia's role within this project is to:

negotiate access to the state/territory historic bushfire boundary datasets aggregate, harmonise and standardise the jurisdictional data against the Australasian Fire Authorities Council (AFAC) National Bushfire Boundary Standards host the completed spatial product(s) arrange for the 'Historical Bushfire Boundaries' spatial dataset to be accessible through Geoscience Australia’s external data catalogues and through the new Digital Atlas of Australia platform ensure stakeholders have access to regular project updates.

To harmonsise and standardise this dataset Geoscience Australia have utilised the AFAC endorsed data dictionary for fire history. This data dictionary and the definitions provided allowed Geoscience Australia to map common attributes from both sources. Unfortunately, not all attributes mapped across like-for-like. This resulted in Geoscience Australia either modifying or joining some of the jurisdictional attributes to fit or Geoscience Australia added them during the processing stage. Currency Date created: 03 March 2023 Date modified: November 2023 Next modification date: November 2024 Spatial Extent

West Bounding Longitude: 112° South Bounding Latitude: -44° East Bounding Longitude: 154° North Bounding Latitude: -9°

Source Information Catalog entry: Bushfire Boundaries – Historical Lineage Statement This dataset extends upon the first version of this dataset to be built and released under the Australia Research Data Commons Project in early 2023.
This dataset (version 2) represents an updated aggregation of each jurisdiction (except the Northern Territory) fire history data to include information from the 2022-23 bushfire season.
Agencies that have provided data include:

Australian Capital Territory Parks and Conservation
New South Wales Parks and Wildlife Service Queensland Parks and Wildlife Service South Australia Department of Environment, Water and Natural Resources Tasmania Department of Natural Resources and Environment Victorian Department of Environment, Land, Water and Planning Western Australia Department of Fire and Emergency Services

The Northern Territory Government is progressing in the development of their Bushfire Boundary Capabilities. Work is underway with the relevant agencies to incorporate Northern Territory Government approved Historical Bushfire Boundary data in the future.
Product standardisation: The data provided by each jurisdiction is standardised and harmonised. This process maps the existing state/territory attributes to the National Data Schema that was agreed to and endorsed by the participating state agencies and the Australian Fire and Emergency Services Authorities Council. The Digital Atlas of Australia data team published an optimised Bushfire Boundaries Historic dataset designed to perform efficiently in either a desktop application or a web service.
This process utilised FME to reduce the processing time on millions of vertices within the complex dataset:

Dataset projected to epsg:4326 to align with the near real time services hosted on the Digital Atlas of Australia Removes island or donut polygons within a fire extent, therefore a fire extent is shown with an outline and no internal parts Create separate polygon chunks based on 10000 vertices while maintaining the same attributes for each chunk of the identified fire, if a fire consists of multiple polygons each polygon is counted separately within the identified fire

As a result the Bushfire Boundaries Historic dataset hosted in the Digital Atlas of Australia has more records than the original dataset. Data Dictionary All Layers

Attribute Name Description

fire_id ID attached to fire (e.g. incident ID, Event ID, Burn ID).

fire_name Incident name. If available.

fire_type Binary variable to describe whether a fire was a bushfire or prescribed burn.

ignition_date The date of the ignition of a fire event. Date and time are local time zone from the State where the fire is located and stored as a string.

capt_date The date of the incident boundary was captured or updated. Date and time are local time zone from the Jurisdiction where the fire is located and stored as a string.

capt_method Categorical variable to describe the source of data used for defining the spatial extent of the fire.

area_ha Burnt area in Hectares. Currently calculated field so that all areas calculations are done in the same map projection. Jurisdiction supply area in appropriate projection to match state incident reporting system.

perim_km ) Burnt perimeter in Kilometres. Calculated field so that all areas calculations are done in the same map projection. Jurisdiction preference is that supplied perimeter calculations are used for consistency with jurisdictional reporting.

state State custodian of the data. NOTE: Currently some states use and have in their feeds cross border data

agency Agency that is responsible for the incident

date_retrieved The date and time that Geoscience Australia retrieved this data from the jurisdictions, stored as UTC. Please note when viewed in ArcGIS Online, the date is converted from UTC to your local time.

Fire Type definitions

Data Source Category Description

Bushfire Unplanned vegetation fire. A generic term which includes grass fires, forest fires and scrub fires both with and without a suppression objective. Also known as wildfire, accident, arson, lightning.

Prescribed Burn The controlled application of fire under specified environmental conditions to a predetermined area and at the time, intensity, and rate of spread required to attain planned resource management objectives. Also known as planned burning, fuel reduction, traditional owner, ecological, hazard reduction

Unknown Fire type is undetermined.

Ignition Cause definitions

Data Source Category Description

Accidental Fires that are not the result of a deliberate (intentional) act.

Natural Fires that ignite without human intervention.

Incendiary Fires result from deliberate acts, intentional actions, or circumstances for the fire to occur in areas where it should not have occurred.

Undetermined Fires that have not yet been investigated, under investigation or fires that have been investigated and the cause is not proven to an acceptable level of certainty.

Capture Method definitions

Data Source Category Description

Aerial photography Derived from Aerial photography including manual interpretation as well as partially automated and fully automated methods.

Linescanner Mapped against airborne sensor systems.

Ground intelligence Mud map from ground observation.

Ground intelligence GPS Fire boundary derived from ground (e.g. GPS tracker, Avenza).

Air intelligence Mud map from air observation.

Air intelligence GPS Fire boundary derived from air (e.g. helicopter, spotter).

Himawari Derived from geostationary satellite Himawari and includes manual interpretation as well as partially automated and fully automated methods (spatial accuracy ± 2 kilometres).

NOAA AVHRR Derived from Low Resolution - NOAA AVHRR satellite including manual interpretation, partially automated and fully automated methods (spatial accuracy ± 1 kilometres).

MODIS Derived from Low Resolution - MODIS satellite imagery including manual interpretation as well as partially automated and fully automated methods (spatial accuracy ± 250 metres).

VIIRS Derived from Low Resolution - VIIRS satellite imagery including manual interpretation as well as partially automated and fully automated methods (spatial accuracy ± 375 metres).

Landsat Derived from Medium Resolution - Landsat satellite imagery including manual interpretation as well as partially automated and fully automated methods (spatial accuracy ± 30 metres).

Sentinel Derived from Medium Resolution - Sentinel satellite imagery including manual interpretation as well as partially automated and fully automated methods (spatial accuracy ± 10 - 20 metres).

Multiple Derived from multiple sources e.g. combination of ground intel and linescanner. For detailed information contact agency or state responsible.

Unknown Data Source is unknown.

Contact Geoscience Australia, clientservices@ga.gov.au

Important: Our technical support team is available to assist you during business hours only. Please keep in mind that we can only address technical difficulties during these hours. When using the product to make decisions, please take this into consideration.

Abstract This spatial product shows consistent ‘near real-time’ bushfire and prescribed burn boundaries for all jurisdictions who have the technical ability or appropriate licence conditions to provide this information. Currency Maintenance of the underlying data is the responsibility of the custodian. Geoscience Australia has automated methods of regularly checking for changes in source data. Once detected the dataset and feeds will be updated as soon as possible. NOTE: The update frequency of the underlying data from the jurisdictions varies and, in most cases, does not line up to this product’s update cycle. Date created: November 2023 Modification frequency: Every 15 Minutes Spatial Extent

West Bounding Longitude: 113° South Bounding Latitude: -44° East Bounding Longitude: 154° North Bounding Latitude: -10°

Source Information The project team initially identified a list of potential source data through jurisdictional websites and the Emergency Management LINK catalogue. These were then confirmed by each jurisdiction through the EMSINA National and EMSINA Developers networks. This Webservice contains authoritative data sourced from:

Australian Capital Territory - Emergency Service Agency (ESA) New South Wales - Rural Fire Service (RFS) Queensland - Queensland Fire and Emergency Service (QFES) South Australia - Country Fire Service (CFS)
Tasmania - Tasmania Fire Service (TFS)
Victoria – Department of Environment, Land, Water and Planning (DELWP)
Western Australia – Department of Fire and Emergency Services (DFES)

The completeness of the data within this webservice is reliant on each jurisdictional source and the information they elect to publish into their Operational Bushfire Boundary webservices. Known Limitations:

This dataset does not contain information from the Northern Territory government. This dataset contains a subset of the Queensland bushfire boundary data. The Queensland ‘Operational’ feed that is consumed within this National Database displays a the last six (6) months of incident boundaries. In order to make this dataset best represent a ‘near-real-time’ or current view of operational bushfire boundaries Geoscience Australia has filtered the Queensland data to only incorporate the last two (2) weeks data. Geoscience Australia is aware of duplicate data (features) may appear within this dataset. This duplicate data is commonly represented in the regions around state borders where it is operationally necessary for one jurisdiction to understand cross border situations. Care must be taken when summing the values to obtain a total area burnt. The data within this aggregated National product is a spatial representation of the input data received from the custodian agencies. Therefore, data quality and data completion will vary. If you wish to assess more information about specific jurisdictional data and/or data feature(s) it is strongly recommended that you contact the appropriate custodian.

The accuracy of the data attributes within this webservice is reliant on each jurisdictional source and the information they elect to publish into their Operational Bushfire Boundary webservices. Note: Geoscience Australia has, where possible, attempted to align the data to the (as of October 2023) draft National Current Incident Extent Feeds Data Dictionary. However, this has not been possible in all cases. Work to progress this alignment will be undertaken after the publication of this dataset, once this project enters a maintenance period. Catalog entry: Bushfire Boundaries – Near Real-Time Lineage Statement Version 1 and 2 (2019/20): This dataset was first built by EMSINA, Geoscience Australia, and Esri Australia staff in early January 2020 in response to the Black Summer Bushfires. The product was aimed at providing a nationally consistent dataset of bushfire boundaries. Version 1 was released publicly on 8 January 2020 through Esri AGOL software.
Version 2 of the product was released in mid-February as EMSINA and Geoscience Australia began automating the product. The release of version 2 exhibited a reformatted attributed table to accommodate these new automation scripts. The product was continuously developed by the three entities above until early May 2020 when both the scripts and data were handed over to the National Bushfire Recovery Agency. The EMSINA Group formally ended their technical involvement with this project on June 30, 2020. Version 3 (2020/21): A 2020/21 version of the National Operational Bushfire Boundaries dataset was agreed to by the Australian Government. It continued to extend upon EMSINA’s 2019/20 Version 2 product. This product was owned and managed by the Australian Government Department of Home Affairs, with Geoscience Australia identified as the technical partners responsible for development and delivery. Work on Version 3 began in August 2020 with delivery of this product occurring on 14 September 2020. Version 4 (2021/22): A 2021/22 version of the National Operational Bushfire Boundaries dataset was produced by Geoscience Australia. This product was owned and managed by Geoscience Australia, who provided both development and delivery. Work on Version 4 began in August 2021 with delivery of this product occurring on 1 September 2021. The dataset was discontinued in May 2022 because of insufficient Government funding. Version 5 (2023/25): A 2023/25 version of the National Near-Real-Time Bushfire Boundaries dataset is produced by Geoscience Australia under funding from the National Bushfire Intelligence Capability (NBIC) - CSIRO. NBIC and Geoscience Australia have also partnered with the EMSINA Group to assist with accessing and delivering this dataset. This dataset is the first time where the jurisdictional attributes are aligned to AFAC’s National Bushfire Schema.
Work on Version 5 began in August 2023 and was released in late 2023 under formal access arrangements with the States and Territories. Data Dictionary Geoscience Australia has not included attributes added automatically by spatial software processes in the table below.

Attribute Name Description

fire_id ID attached to fire (e.g. incident ID, Event ID, Burn ID).

fire_name Incident name. If available.

fire_type Binary variable to describe whether a fire was a bushfire or prescribed burn.

ignition_date The date of the ignition of a fire event. Date and time are local time zone from the State where the fire is located and stored as a string.

capt_date The date of the incident boundary was captured or updated. Date and time are local time zone from the Jurisdiction where the fire is located and stored as a string.

capt_method Categorical variable to describe the source of data used for defining the spatial extent of the fire.

area_ha Burnt area in Hectares. Currently calculated field so that all areas calculations are done in the same map projection. Jurisdiction supply area in appropriate projection to match state incident reporting system.

perim_km ) Burnt perimeter in Kilometres. Calculated field so that all areas calculations are done in the same map projection. Jurisdiction preference is that supplied perimeter calculations are used for consistency with jurisdictional reporting.

state State custodian of the data. NOTE: Currently some states use and have in their feeds cross border data

agency Agency that is responsible for the incident

date_retrieved The date and time that Geoscience Australia retrieved this data from the jurisdictions, stored as UTC. Please note when viewed in ArcGIS Online, the date is converted from UTC to your local time.

Contact Geoscience Australia, clientservices@ga.gov.au

This layer delineates the four (4) management zones that exist within Glacier National Park, Montana. Management zoning is intended to spatially guide appropriate park management activities. The four zones are:Visitor Services Zone – developed zones, paved roads, and utility corridors.Rustic Zone – unpaved and preserved “back in time” areas with historical context (e.g. 1913 Ranger Station)Day Use Zone – destination oriented trails (e.g. Highline Trail)Backcountry Zone – backcountry areas not included in the other three management zonesManagement zones for Glacier National Park were described conceptually in the park's 1999 General Management Plan (GMP). Over time, and through other planning processes, zones have been more clearly defined on the ground beginning with the Visitor Service Zone definition as part of the 2004 Commercial Services Plan. Zone boundaries have been modified as new and better information has become available. Utility information (electric and gas lines), for example, that was lacking in 2004 and became available in 2012 and 2013 allowed for mapping new areas into the Visitor Service Zone.Definition of all zones other than the Backcountry Zone involved buffers from paved/unpaved road centerlines, utility lines or points, trail centerlines, or developed area footprints. A brief description of how each zone was delineated follows:The Visitor Service Zone was last revised in May 2013 and included the following areas: 1) developed area footprints (as delineated by the extent of development) plus a 300-ft buffer; 2) paved roads plus a 200-ft buffer from road centerline; 3) selected non-paved roads plus a 50-ft buffer from road centerline; 4) utility point or line features buffered 25-ft; and 5) selected large lakes identified in the GMP: McDonald, Saint Mary, and Lower Two Medicine.The RusticZone was created using the following general GIS processing steps: 1) select included non-paved roads and buffer 50-ft from centerline; 2) capture rustic area footprints (extent of development) and buffer 50-ft.; and 3) buffer known utility lines and points 25-ft. All buffer areas were merged to create the rustic zone areas.The Day Use zone was revised in May 2013 to include the following: 1) trails, buffered 50-feet; and 2) selected lakes identified in the General Management Plan: Swiftcurrent, Josephine, and Two Medicine.

© Glacier NP GIS Program

This layer is a component of Glacier National Park.

This map service provides layers covering a variety of different datasets and themes for Glacier National Park. It is meant to be consumed by internet mapping applications and for general reference. It is for internal NPS use only. Produced November 2014.

© Denver Service Center Planning Division, IMR Geographic Resources Division, Glacier National Park

It is difficult to imagine boundaries existing in the open ocean. In reality, boundaries have divided the waters of the United States throughout most of the nation's history. These marine boundaries have changed over time, with reference points serving to delineate the extent of federal statutes, regulations, and jurisdictions. This story map outlines the history of U.S. marine boundaries, how they have changed over time, and how current boundary data have been developed for MarineCadastre.gov.

This data identifies current as well as proposed zoning and land use designations that are adopted by ordinances for unincorporated Pierce County. Zoning for cities is not included in this dataset. Zones are adopted by ordinances with specific technicalities for each community. Land Use designations offer a broad spectrum of allowable uses within a community. It is used to create a Comprehensive Plan Map or used for a Generalized Proposed Land Use Map or GPLUM. This dataset is also used to create the Land Use Designations theme, which covers proposed zoning use. The meaning of proposed is that the property might not be currently used for the purpose stated. It should be noted that Council adopted amendments to land use designations/zoning that will be effective at the beginning of 2006. Also, the Council is in the process of adopting the Mid-County Community Plan which amends land use designations/zoning as well. The Cities polygons found in the zoning data does not necessarily match the current cities boundaries. This is because the zoning data is updated once a year per the "Pierce County Comprehensive Plan" and does not allow for changes to be made during the year. The Comprehensive Plan is generally updated in November and generally becomes effective the following March. Use the "Cities in Pierce County" data set to determine current city boundaries. City boundaries can change more often than the current adopted Pierce County Zoning data. The zoning data contains the "Cities in Pierce County" boundaries at the time that the Pierce County Zoning was adopted. When determining the current zoning of a parcel near a city, the current "Cities in Pierce County" data set needs to be reviewed. Zoning codes for parcels within incorporated cities are determined by the city that the parcel is within. Please read metadata for additional information (https://matterhorn.piercecountywa.gov/GISmetadata/pdbplan_zoning.html). Any use or data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/disclaimer/PierceCountyGISDataTermsofUse.pdf).

This data represents the Ministry of Natural Resources (MNR) administrative boundaries from 1997-2022. Ministry of Natural Resources (MNR) administrative areas divide Ontario into smaller organizational units. These units were used to manage ministry programs and resources at a district and regional level. Regional and district boundaries were originally created based on: * metes and bounds * topographic features * geographic townships boundaries * territorial district boundaries We made changes to district boundaries over time. We are no longer updating this data. It is best suited for historical research and analysis. MNR regions MNR regions were created to help manage ministry programs and resources at a regional level. Regions consist of several districts. MNR districts MNR regions were divided into smaller organizational units called districts. MNR areas MNR districts were further divided into areas.

USNG is standard that established a nationally consistent grid reference system. It provides a seamless plane coordinate system across jurisdictional boundaries and map scales; it enables precise position referencing with GPS, web map portals, and hardcopy maps. USNG enables a practical system of geoaddresses and a universal map index. This data resides in the GCS 1983 coordinate system and is most suitable for viewing over North America.

The data is separated into three groups, Small Scale Grids, 1000m Grids, and 100m Grids. The small scale grid group contains grids shown at smaller scales including the 6 x 8 decimal degree grids, the 100000m grids, and the 10000m grids. The 1000m grid group shows 1,000 meter grid squares. Due to the large volume of 1000m data, the 1000m grids are separate into UTM zones. This speeds up the querying time of the 1000m grids. The 100m grid group contains 100m grids for various metropolitan area in the U.S. and Puerto Rico. These metropolitan areas are further separate into time zones so it's easier to navigate through the Table of Contents to find a metro area.

The California Flood Management Districts geodatabase contains several spatial data layers indicating boundaries of various local flood management agencies throughout the state. There are also attribute tables indicating current contact information, updated as of Spring, 2006, as included in the Directory of Flood Officials, produced by the California Department of Water Resources Division of Flood Management. Of the various layers, the most numerous are referred to as reclamation districts. The reclamation districts layer is an indication of the approximate jurisdictional boundary of both currently active or once-active-but-now-inactive reclamation districts. Districts have in some cases merged, dissolved, divided, and been modified since their original formation. The reclamation districts indicated here were generated from a variety of sources, including (in order of boundary accuracy preference) complete legal descriptions submitted at the time of District formation, CAD boundary files provided by District engineers, boundaries digitized by Department of Water Resources Delta-Suisun Office over orthophotography, incomplete legal descriptions submitted at the time of District formation, DWR Land Use maps, a 1997 California Office of Emergency Services effort to map boundaries, and sundry other means. The work has essentially been an ongoing effort since the production of the original 1997 layer, in order to improve that first effort somewhat. Most of the improvements have focused on Districts within the Sacramento-San Joaquin Delta region, since DWR's office responsible for that area has undertaken most of the improvement work. As a result, there are probably many remaining data gaps and inaccuracies, particularly in areas outside of the Delta. This is particularly true of DWR maintenance areas and for levee districts, both of which will certainly require updating in the future.