REST API endpoint that includes the city's mapping services.

Service provided by HED articulates, as guidance, zones indicating to planners on when HED should be consulted in respect of proposals in the vicinity of heritage assets. It does not articulate the setting of assets but provides a baseline to ensure that HED are consulted in respect of applications within these areas. Data produced from HED data and updated monthly. Data contains attribution values providing unique id for each record, layer each record is derived from and buffer value (NULL where buffer=0).

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Base_Layers/FeatureServer

Webservices for HED data: • NI Sites and Monuments Record • Listed Buildings • Industrial Heritage Record • Built Heritage at Risk • Defense Heritage Record • Ship and Aircraft Wrecks • Areas of Archaeological Potential • Areas of Significant Archaeological Interest • Battlesites • Historic Parks, Gardens and Demesnes • Scheduled Zones

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Base_Layers/MapServer

This web mapping service contains datasets related to biodiversity such as Ecosystem components maps, HELCOM MPAs

The service is created with ArcGIS Server 10.9 and can be accessed via ArcGIS REST interface or OGC WMS.

The service is used by HELCOM Map and Data service.

Mosaics are published as ArcGIS image serviceswhich circumvent the need to download or order data. GEO-IDS image services are different from standard web services as they provide access to the raw imagery data. This enhances user experiences by allowing for user driven dynamic area of interest image display enhancement, raw data querying through tools such as the ArcPro information tool, full geospatial analysis, and automation through scripting tools such as ArcPy. Image services are best accessed through the ArcGIS REST APIand REST endpoints (URL's). You can copy the OPS ArcGIS REST API link below into a web browser to gain access to a directory containing all OPS image services. Individual services can be added into ArcPro for display and analysis by using Add Data -> Add Data From Path and copying one of the image service ArcGIS REST endpoint below into the resultant text box. They can also be accessed by setting up an ArcGIS server connectionin ESRI software using the ArcGIS Image Server REST endpoint/URL. Services can also be accessed in open-source software. For example, in QGIS you can right click on the type of service you want to add in the browser pane (e.g., ArcGIS REST Server, WCS, WMS/WMTS) and copy and paste the appropriate URL below into the resultant popup window. All services are in Web Mercator projection. For more information on what functionality is available and how to work with the service, read the Ontario Web Raster Services User Guide. If you have questions about how to use the service, email Geospatial Ontario (GEO) at geospatial@ontario.ca Available Products: ArcGIS REST APIhttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/ Image Service ArcGIS REST endpoint / URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer https://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer https://ws.geoservices.lrc.gov.on.ca/arcgis5/rest/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServerWeb Coverage Services (WCS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WCSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WCSServer/Web Mapping Service (WMS) URL'shttps://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2013to2017/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2018to2022/ImageServer/WMSServer/https://ws.geoservices.lrc.gov.on.ca/arcgis5/services/AerialImagery/GEO_Imagery_Data_Service_2023to2027/ImageServer/WMSServer/ Metadata for all imagery products available in GEO-IDS can be accessed at the links below:South Central Ontario Orthophotography Project (SCOOP) 2023North-Western Ontario Orthophotography Project (NWOOP) 2022 Central Ontario Orthophotography Project (COOP) 2021 South-Western Ontario Orthophotography Project (SWOOP) 2020 Digital Raster Acquisition Project Eastern Ontario (DRAPE) 2019-2020 South Central Ontario Orthophotography Project (SCOOP) 2018 North-Western Ontario Orthophotography Project (NWOOP) 2017 Central Ontario Orthophotography Project (COOP) 2016 South-Western Ontario Orthophotography Project (SWOOP) 2015 Algonquin Orthophotography Project (2015) Additional Documentation: Ontario Web Raster Services User Guide (Word) Status:Completed: Production of the data has been completed Maintenance and Update Frequency:Annually: Data is updated every year Contact:Geospatial Ontario (GEO), geospatial@ontario.ca

Beautify The BurghMetadata: https://www.arcgis.com/sharing/rest/content/items/bcd39ed918714385ac1c135b3e122582/info/metadata/metadata.xml?format=default&output=html

🇺🇸 미국

Airport defines area on land or water intended to be used either wholly or in part for the arrival; departure and surface movement of aircraft/helicopters. This airport data is provided as a vector geospatial-enabled file format and depicted on Enroute charts.Airport information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.Current Effective Date: 0901Z 02 Oct 2025 to 0901Z 27 Nov 2025

This Server provides the following REST API Feature services: GEOLOGIC CONTACTS: Base of Quaternary (Kvarter talp), Base of Upper Pannonian (Felső-pannóniai talp), Base of Pannoanian (Pannóniai talp), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_fdt_szint/MapServer ,

ISOTHERMS IN THE PANNONIAN BASIN: Top of the pre-Cenozoic basement (Prekainozoos aljzat felszíne), Depth of the 30°C isotherm (A 30 °C izoterma becsült mélysége), Depth of the 50°C isotherm (Az 50 °C izoterma becsült mélysége), Depth of the 75°C isotherm (A 75 °C izoterma becsült mélysége), Depth of the 100°C isotherm (A 100 °C izoterma becsült mélysége), Depth of the 125°C isotherm (A 125 °C izoterma becsült mélysége), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_izoterma/MapServer ,

WELLS AND WATER SOURCES: Thermal water well (Hévízkút), Status of thermal water wells (Hévízkút állapot), Geothermal gradient of thermal water wells (Hévízkutak geotermikus gradiense), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_kutak/MapServer ,

TEMPERATURE of pre-Cenozoic basement (A prekainozoos aljzatfelszín hőmérséklete (konduktív modell)), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_prekain_hom/MapServer ,

GEOTHERMAL PROJECTS (Geotermikus projektek), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_projekt/MapServer

POTENTIAL REZERVOIRS: Quaternary 30-50 °C top (Kvarter 30–50 °C tető), Quaternary 30-50 °C bottom (Kvarter 30–50 °C talp), Upper Pannonian 30-50 °C top (Felső-pannóniai 30–50 °C tető), Upper Pannonian 30-50 °C bottom (Felső-pannóniai 30–50 °C talp), Upper Pannonian 50-75 °C top (Felső-pannóniai 50–75 °C tető), Upper Pannonian 50-75 °C bottom (Felső-pannóniai 50–75 °C talp), Upper Pannonian 75-100 °C top (Felső-pannóniai 75–100 °C tető), Upper Pannonian 75-100 °C bottom (Felső-pannóniai 75–100 °C talp), Upper Pannonian 100-125 °C top (Felső-pannóniai 100–125 °C tető), Upper Pannonian 100-125 °C bottom (Felső-pannóniai 100–125 °C talp), Upper Pannonian 125°C < top (Felső-pannóniai 125 °C < tető), Upper Pannonian 125°C < bottom (Felső-pannóniai 125 °C < talp), Drilled pre-Cenozoic limestone-dolomite below 2500 m (2500 m alatt megfúrt prekainozoos mészkő–dolomit réteg), Drilled pre-Cenozoic formations below 2500 m (2500 m alatt megfúrt prekainozoos réteg), Borehole deeper than 2500 m (2500 méternél mélyebb fúrás), Carbonate basement formation below 2500 m (2500 m-nél mélyebb karbonátos aljzatfelszín képződmény), Magmatic, metamorphic basement formation below 2500 m (2500 m-nél mélyebb mélységi magmás, metamorf aljzatfelszín képződmény), Unknown geology below 2500 m (2500 m-nél mélyebb ismeretlen aljzatú terület), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_rezervoar/MapServer ,

DISTRICT HEATING: Geothermal district heating (Geotermikus távfűtés), District heating (Egyéb távfűtés), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_tavfutes/MapServer ,

GROUNDWATER BODIES: Thermal groundwater body (Termálvíztest (VGT2)), https://map.mbfsz.gov.hu/arcgis/rest/services/geoterm/MGT_termalviztest/MapServer

LfULG Sachsen has developed a method for recording medium soil sealing for the entire state area from existing data sets. Information from the ATKIS base DLM (Land Survey, as of 2018) is used, and the mean soil sealing is assigned to the respective legend units. For the use of the information in the 3 planning areas of regional, regional and municipal planning, the information is classified into 3 different grids with the following cell sizes: 1000 × 1000 meters: Country planning; 100 × 100 meters: Regional planning; 25 × 25 meters: Local planning. Each cell carries the mean degree of sealing of the soil as surface information. The information will be gradually updated over the next few years and new levels of knowledge will be incorporated. This information will be published with updates.

The ArcGIS Server REST service presents the soil sensitivity maps based on the soil estimate in scale 1: 5,000 and deliver them. The information on the creation of soil sensitivity maps can be found in the corresponding data set. The REST service provides three layers. These are the layer erodability by water, sensitivity to drying and sensitivity to irrigation.

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Land_Estate_Layers/FeatureServer

Last Revised: February 2016 Map InformationThis nowCOAST™ time-enabled map service provides maps depicting the latest surface weather and marine weather observations at observing sites using the international station model. The station model is a method for representing information collected at an observing station using symbols and numbers. The station model depicts current weather conditions, cloud cover, wind speed, wind direction, visibility, air temperature, dew point temperature, sea surface water temperature, significant wave height, air pressure adjusted to mean sea level, and the change in air pressure over the last 3 hours. The circle in the model is centered over the latitude and longitude coordinates of the station. The total cloud cover is expressed as a fraction of cloud covering the sky and is indicated by the amount of circle filled in; however, all cloud cover values are presently displayed using the "Missing" symbol due to a problem with the source data. Present weather information is also not available for display at this time. Wind speed and direction are represented by a wind barb whose line extends from the cover cloud circle towards the direction from which the wind is blowing. The short lines or flags coming off the end of the long line are called barbs, which indicate wind speed in knots. Each normal barb represents 10 knots, while short barbs indicate 5 knots. A flag represents 50 knots. If there is no wind barb depicted, an outer circle around the cloud cover symbol indicates calm winds.Due to software limitations, the observations included in this map service are organized into three separate group layers: 1) Wind velocity (wind barb) observations, 2) Cloud Cover observations, and 3) All other observations, which are displayed as numerical values (e.g. Air Temperature, Wind Gust, Visibility, Sea Surface Temperature, etc.).Additionally, due to the density of weather/ocean observations in this map service, each of these group data layers has been split into ten individual "Scale Band" layers, with each one visible for a certain range of map scales. Thus, to ensure observations are displayed at any scale, users should make sure to always specify all ten corresponding scale band layers in every map request. This will result in the scale band most appropriate for your present zoom level being shown, resulting in a clean, uncluttered display. As you zoom in, additional observations will appear.The observations in this nowCOAST™ map service are updated approximately every 10 minutes. However, since the reporting frequency varies by network or station, the observations for a particular station may update only once per hour. For more detailed information about layer update frequency and timing, please reference the nowCOAST™ Dataset Update Schedule.Background InformationThe maps of near-real-time surface weather and ocean observations are based on non-restricted data obtained from the NWS Family of Services courtesy of NESDIS/OPSD and also the NWS Meteorological Assimilation Data Ingest System (MADIS). The data includes observations from terrestrial and maritime observing stations from the U.S.A. and other countries. For terrestrial networks, the platforms include but are not limited to ASOS, AWOS, RAWS, non-automated stations, U.S. Climate Reference Networks, many U.S. Geological Survey Stations via NWS HADS, several state DOT Road Weather Information Systems, and U.S. Historical Climatology Network-Modernization. For maritime areas, the platforms include NOS/CO-OPS National Water Level Observation Network (NWLON), NOS/CO-OPS Physical Oceanographic Real-Time System (PORTS), NWS/NDBC Fixed Buoys, NDBC Coastal-Marine Automated Network (C-MAN), drifting buoys, ferries, Regional Ocean Observing System (ROOS) coastal stations and buoys, and ships participating in the Voluntary Ship Observing (VOS) Program. Observations from MADIS are updated approximately every 10 minutes in the map service and those from NESDIS are updated every hour. However, not all stations report that frequently. Many stations only report once per hour sometime between 15 minutes before the hour and 30 minutes past the hour. For these stations, new observations will not appear until approximately 23 minutes past top of the hour for land-based stations and 33 minutes past the top of the hour for maritime stations.Time InformationThis map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:Issue a returnUpdates=true request (ArcGIS REST protocol only) for an individual layer or for the service itself, which will return the current start and end times of available data, in epoch time format (milliseconds since 00:00 January 1, 1970). To see an example, click on the "Return Updates" link at the bottom of the REST Service page under "Supported Operations". Refer to the ArcGIS REST API Map Service Documentation for more information.Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against the proper layer corresponding with the target dataset. For raster data, this would be the "Image Footprints with Time Attributes" layer in the same group as the target "Image" layer being displayed. For vector (point, line, or polygon) data, the target layer can be queried directly. In either case, the attributes returned for the matching raster(s) or vector feature(s) will include the following:validtime: Valid timestamp.starttime: Display start time.endtime: Display end time.reftime: Reference time (sometimes referred to as issuance time, cycle time, or initialization time).projmins: Number of minutes from reference time to valid time.desigreftime: Designated reference time; used as a common reference time for all items when individual reference times do not match.desigprojmins: Number of minutes from designated reference time to valid time.Query the nowCOAST™ LayerInfo web service, which has been created to provide additional information about each data layer in a service, including a list of all available "time stops" (i.e. "valid times"), individual timestamps, or the valid time of a layer's latest available data (i.e. "Product Time"). For more information about the LayerInfo web service, including examples of various types of requests, refer to the nowCOAST™ LayerInfo Help DocumentationReferencesNWS, 2013: Sample Station Plot, NWS/NCEP/WPC, College Park, MD (Available at http://www.wpc.ncep.noaa.gov/html/stationplot.shtml).NWS, 2013: Terminology and Weather Symbols, NWS/NCEP/OPC, College Park, MD (Available at http://www.opc.ncep.noaa.gov/product_description/keyterm.shtml).NWS, 2013: How to read Surface weather maps, JetStream an Online School for Weather (Available at http://www.srh.noaa.gov/jetstream/synoptic/wxmaps.htm).

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Mineral_Estate_Layers/MapServer

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Water_Estate_Layers/MapServer

This Feature Service provides a database of worldwide airport locations and aviation information. It includes information about codenames, elevation, frequency, runways and wikipedia links.Additional Information All the data are crowdsourced by the community of OurAirports.com. SourceOurAirports.com/data/ | Last accessed on: 23.05.2025Processing procedureBy using the CSV table 'Airports' dated Feb 09, 2024, we have joined the tables 'Runways' and 'Airport-Frequencies' for additional information using the key:"ident". The points were projected and released as an ArcGIS Online feature service.Data2024

This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria:

Vermont composite geocoding service built with VT E911 data. This service can be used by ArcGIS Pro 2.8.x+ to batch geocode addresses stored in a table. It also can be used as a geocoder with most ArcGIS Online apps, as well as QGIS. [How To Use The Vermont Geocoding Service]This ArcGIS Online item utilizes the ArcGIS Server geocoding service at this REST Endpoint: https://maps.vcgi.vermont.gov/arcgis/rest/services/EGC_services/GCS_E911_COMPOSITE_SP_v2/GeocodeServer