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.

description:

The boundary line between Central Time and Mountain Time in North Dakota. This data was compiled from multiple sources with the primary source being the ND Department of Transportation and the National Atlas.

Constraints: Not to be used for navigation, for informational purposes only. See full disclaimer for more information.

The boundary line between Central Time and Mountain Time in North Dakota. This data was compiled from multiple sources with the primary source being the ND Department of Transportation and the National Atlas.

Constraints: Not to be used for navigation, for informational purposes only. See full disclaimer for more information.

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.

Database contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules.

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.

Overview

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

Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative 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 Boundaries Database (GIS data, Geospatial 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 GIS data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

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

All GIS 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.

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.

Intermediate zones are a statistical geography that sit between data zones and local authorities, created for use with the Scottish Neighbourhood Statistics (SNS) programme. Intermediate zones are used for the dissemination of statistics that are not suitable for release at the data zone level because of the sensitive nature of the statistics, or for reasons of reliability. Intermediate Zones were designed to meet constraints on population thresholds (2,500 - 6,000 household residents), to nest within local authorities (as they were in 2001), and to be built up from data zones. The aim was also to build intermediate zones by grouping together data zones with similar social characteristics, to have fairly compact shape and to take into account physical boundaries. Intermediate zones are a stable geography and can be used to analyse change over time.

There are 1,235 intermediate zones across Scotland, and each have been assigned an individual code that follows the Scottish Government's standard naming and coding convention. The code prefix is S02, which has been assigned to designate intermediate zones. In most cases, intermediate zones were also been assigned a name by the relevant Community Planning Partnership. From time to time Local Authorities may choose to update these names, and this dataset will be updated to reflect these changes.

Comprehensive, weekly-updated polygon datasets covering postal and administrative boundaries for 247 countries, featuring up to 6 hierarchical levels, edge-matched polygons, and enriched with attributes like population, multilingual support, UNLOCODEs, IATA codes, and time zones.

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

The Climate Resilience Information System (CRIS) provides data and tools for developers of climate services. This layer has historical variables in decadal increments from 1950 to 2020 derived from historical observations of air temperature and precipitation. The variables included are:Annual number of days with a maximum temperature greater than or equal to 85°F Annual number of days with a maximum temperature greater than or equal to 86°F Annual number of days with a maximum temperature greater than or equal to 90°F Annual number of days with a maximum temperature greater than or equal to 95°F Annual number of days with a maximum temperature greater than or equal to 100°F Annual number of days with a maximum temperature greater than or equal to 105°F Annual number of days with a maximum temperature greater than or equal to 110°F Annual number of days with a maximum temperature greater than or equal to 115°F This layer uses data from the NOAA Monthly U.S. Climate Gridded Dataset (nClimGrid). Further processing by Esri is explained below.For each variable, there are mean values for the defined respective geography: counties, tribal areas, HUC-8 watersheds. The process for deriving these summaries is available from the CRIS Website’s About the Data. Other climate variables are available from the CRIS Data page. Additional geographies, including Alaska, Hawai’i and Puerto Rico will be made available in the future.GeographiesThis layer provides historic values for three geographies: county, tribal area, and HUC-8 watersheds.County: based on the U.S. Census TIGER/Line 2022 distribution. Tribal areas: based on the U.S. Census American Indian/Alaska Native/Native Hawaiian Area dataset 2022 distribution. This dataset includes federal- and state-recognized statistical areas.HUC-8 watershed: based on the USGS Washed Boundary Dataset, part of the National Hydrography Database Plus High Resolution. Time RangesHistoric climate threshold values (e.g. Days Over 90°F) were calculated for each year from 1950 to 2020. To ensure the layer displays time correctly, under 'Map properties' set Time zone to 'Universal Coordinated Time (UTC)' and under 'Time slider options' set Time intervals to '1 Decade'.Data CitationVose, Russell S., Applequist, Scott, Squires, Mike, Durre, Imke, Menne, Matthew J., Williams, Claude N. Jr., Fenimore, Chris, Gleason, Karin, and Arndt, Derek (2014): NOAA Monthly U.S. Climate Gridded Dataset (nClimGrid), Version 1. NOAA National Centers for Environmental Information. https://doi.org/10.7289/V5SX6B56.Data ExportExporting this data into shapefiles, geodatabases, GeoJSON, etc is enabled.

The Climate Resilience Information System (CRIS) provides data and tools for developers of climate services. This layer has historical variables in decadal increments from 1950 to 2020 derived from historical observations of air temperature and precipitation. The variables included are:Annual average daily maximum temperature (°F) Annual average daily temperature (°F) Annual average daily minimum temperature (°F) Annual single highest maximum temperature (°F) Annual single lowest minimum temperature (°F) Annual average summertime (June, July, August) temperature (°F) This layer uses data from the Livneh gridded precipitation and other meteorological variables for continental US, Mexico and southern Canada. Further processing by Esri is explained below.For each variable, there are mean values for the defined respective geography: counties, tribal areas, HUC-8 watersheds. The process for deriving these summaries is available from the CRIS Website’s About the Data. Other climate variables are available from the CRIS Data page. Additional geographies, including Alaska, Hawai’i and Puerto Rico will be made available in the future.GeographiesThis layer provides historic values for three geographies: county, tribal area, and HUC-8 watersheds.County: based on the U.S. Census TIGER/Line 2022 distribution. Tribal areas: based on the U.S. Census American Indian/Alaska Native/Native Hawaiian Area dataset 2022 distribution. This dataset includes federal- and state-recognized statistical areas.HUC-8 watershed: based on the USGS Washed Boundary Dataset, part of the National Hydrography Database Plus High Resolution. Time RangesHistoric climate threshold values (e.g. Days Over 90°F) were calculated for each year from 1950 to 2020. To ensure the layer displays time correctly, under 'Map properties' set Time zone to 'Universal Coordinated Time (UTC)' and under 'Time slider options' set Time intervals to '1 Decade'.Data CitationLivneh, B., T. J. Bohn, D. W. Pierce, F. Munoz-Arriola, B. Nijssen, R. Vose, D. R. Cayan, and L. Brekke, 2015: A spatially comprehensive, hydrometeorological data set for Mexico, the U.S., and Southern Canada 1950 - 2013. Scientific Data, 2, https://doi.org/10.1038/sdata.2015.42.Data ExportExporting this data into shapefiles, geodatabases, GeoJSON, etc is enabled.

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

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 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.

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

🇬🇧 영국 English Intermediate zones are a statistical geography that sit between data zones and local authorities, created for use with the Scottish Neighbourhood Statistics (SNS) programme. Intermediate zones are used for the dissemination of statistics that are not suitable for release at the data zone level because of the sensitive nature of the statistics, or for reasons of reliability. Intermediate Zones were designed to meet constraints on population thresholds (2,500 - 6,000 household residents), to nest within local authorities (as they were in 2001), and to be built up from data zones. The aim was also to build intermediate zones by grouping together data zones with similar social characteristics, to have fairly compact shape and to take into account physical boundaries. Intermediate zones are a stable geography and can be used to analyse change over time. There are 1,235 intermediate zones across Scotland, and each have been assigned an individual code that follows the Scottish Government's standard naming and coding convention. The code prefix is S02, which has been assigned to designate intermediate zones. In most cases, intermediate zones were also been assigned a name by the relevant Community Planning Partnership. From time to time Local Authorities may choose to update these names, and this dataset will be updated to reflect these changes.

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 accumulating 3-hourly snapshots of bushfire and prescribed burn boundaries, consistent across all jurisdictions who have the technical ability or appropriate licence conditions to provide this information. This dataset is derived from the National Near-Real-Time Bushfire Boundaries product. Currency Maintenance of the underlying data is the responsibility of the individual custodian. 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 3 Hours Spatial Extent

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

Source Information This dataset is derived from the National Near-Real-Time Bushfire Boundaries product. 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 – 3-Hourly Accumulation Lineage Statement Version 1 (2021/22): A 2021/22 version of the National 3 Hourly Cumulative 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 1 of this dataset began in August 2021 with delivery occurring in September 2021. The dataset was discontinued in May 2022 due to insufficient Government funding. Version 2 (2023/25): A 2023/25 version of 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 2 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 Contact: Geoscience Australia clientservices@ga.gov.au

These datasets represent management units within in-force water sharing plans across NSW, including regulated, unregulated and groundwater plans (or a combination of these). The data includes both water sources and management zones (where applicable) derived from plans gazetted under the NSW Water Management Act 2000. The boundaries of these water sources and management zones are used to define areas in which specific management rules apply. As such, this data may be used to understand which water sharing plan rules apply to a specific location. The plans are in place for 10 years but may be amended within this time. Any updates to water source or management zone boundaries as a result of a plan being amended during, or replaced following its 10 year term will be made available at that time. PLEASE NOTE: In the case of any discrepancy between this digital dataset and the published Water Sharing Plan (accessible on the www.legislation.nsw.gov.au site) the instrument as made by the Minister remains the authoritative source and should be used to both interpret the intent of the Plan and in subsequent decision making. Best endeavours have been made in collating relevant Water Sharing Plan boundary and attribution contained in this dataset. However, no warranty is provided as to the accuracy or currency of this representation. The department does not warrant and is not liable for the use of this material as per the licenced sharing conditions CC-BY 4.0.