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

🇺🇸 미국

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.

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

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

Collection of Feature Layers for early Broadband Initiative Work. 9-1-1 systems and telecommunications infrastructure also including mobile broadband deployment by technology type and by carrier.Non-DCRA data - collected by MatSu Borough from other Sources for very early Broadband Initiative research July 2021. Original Source as NotedPublic Safety Answering Points: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Public_Safety_Answering_Points/FeatureServer (Phone and email survey July 2020)Call Routing: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/FINAL_Call_Routing/FeatureServer (ATA Call Routing Survey 2020)Telecommunication Towers from FCC: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Cell_Towers_from_FCC/FeatureServer (8/3/2020 FCC Antenna Structure Registration (ASR) download Circa Jan 2024 see https://www.fcc.gov/wireless/systems-utilities/antenna-structure-registration. This may be already distributed in GIS form by the Homeland Infrastructure Foundation-Level Data (HIFLD) Portal (broken into various layers) see https://hifld-geoplatform.opendata.arcgis.com/Wireless Coverage 4G LTE: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_4GLTE_Wireless_Coverage/FeatureServer (FCC Form 477 data for Alaska using combined carriers delivering technology code 83)Wireless Coverage 3G 4G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_3G_4G_Wireless_Coverage/FeatureServer (FCC Form 477 data for Alaska using combined carriers delivering technology code 81, HSPA+)Wireless Coverage 3G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_3G_Wireless_Coverage/FeatureServer (Geographic extent of 3G wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)Wireless Coverage Analog: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_Analog_Wireless_Coverage/FeatureServer (Geographic extent of analog wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)Wireless Coverage 2G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_2G_Wireless_Coverage/FeatureServer (Geographic extent of 2G wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)State Trooper Detachments (other than North Slope): https://services3.arcgis.com/3NvWZvRqANiCzqqd/ArcGIS/rest/services/AST_Detachments/FeatureServer (Alaska State Trooper Jurisdictions and Operational Area by Detachment. Revised 9/2020)This data has been visualized in a Geographic Information Systems (GIS) format and is provided as a service in the DCRA Information Portal by the Alaska Department of Commerce, Community, and Economic Development Division of Community and Regional Affairs (SOA DCCED DCRA), Research and Analysis section and was last posted on July 1, 2021. SOA DCCED DCRA Research and Analysis is not the authoritative source for this data. For more information and for questions about this data, see: Mat-Su Open Data

🇺🇸 미국

U.S. soil property maps in a raster format that meet the GlobalSoilMap standards. Services: GlobalSoilMap_v05/available_water_supply (MapServer) GlobalSoilMap_v05/bulk_density_lessthan_2mm (MapServer) GlobalSoilMap_v05/bulk_density_whole_soil (MapServer) GlobalSoilMap_v05/clay (MapServer) GlobalSoilMap_v05/effective_cation_exchange_capacity (MapServer) GlobalSoilMap_v05/electric_conductivity (MapServer) GlobalSoilMap_v05/gravel (MapServer) GlobalSoilMap_v05/pH (MapServer) GlobalSoilMap_v05/sand (MapServer) GlobalSoilMap_v05/silt (MapServer) GlobalSoilMap_v05/soil_depth (MapServer) GlobalSoilMap_v05/soil_organic_carbon (MapServer) Resources in this dataset:Resource Title: GlobalSoilMaps. File Name: Web Page, url: https://nrcsgeoservices.sc.egov.usda.gov/arcgis/rest/services/GlobalSoilMap_v05 ArcGIS REST Services Directory Folder: GlobalSoilMap_v05

This package contains National, Statewide, and Palm Beach County elements. Links are provided where available but do note that staff geoprocess files to create a more personalized MPO-purposed basemap.MPO Basemap PackageLayer/Groups*Additional InformationCounty BoundaryThis layer utilizes staff defined Definition Queries depending on the scenario (i.e. only PBC vs the Region).API: https://services1.arcgis.com/T0NPfOCJr9tmBN93/arcgis/rest/services/Florida_Counties/FeatureServerRoadway Labels*This following group contains several FDOT maintained layers bulleted below. Additional these roadway layers utilize specialized icon labels along with staff defined Definition Queries (DQs) to help manipulate them based on the current need.InterstatesAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Interstates_TDA/FeatureServerUS HighwaysAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/US_Routes_TDA/FeatureServerToll RoadsAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Toll_Roads_TDA/FeatureServerThis layer's labels utilized two classes each incorporating SQL queries to separate Toll symbologies from the main Turnpike one.State RoadsAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/State_Roads_TDA/FeatureServerCounty RoadwaysAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/County_Roads_TDA/FeatureServerMajor RoadwaysThis FDOT Functional Classification layer utilizes staff defined Definition Queries for Major Roadway symbolization.API: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Functional_Classification_TDA/FeatureServerRailroadsThis ESRI layer utilizes staff defined Definition Queries for general Railroad symbolization.API: https://services.arcgis.com/xOi1kZaI0eWDREZv/arcgis/rest/services/NTAD_North_American_Rail_Network_Lines/FeatureServerstate_fl_uabThis geoprocessed layer is clip to the state_fl_basemap for a cleaner version of the FDOT Smoothed Urban Boundaries layer along coastlines; linked below for reference.API: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/FDOT_FHWA_Smoothed_Urban_Boundaries_TDA/FeatureServercounty_pal*This following group contains several Palm Beach County and MPO maintained layers bulleted below. Additional staff defined Definition Queries (DQ) and noted below:county_pal_roadways (County)API: https://maps.co.palm-beach.fl.us/arcgis/rest/services/OpenData/Transportation_Open_Data/MapServerPBC localized road network. If not using DQs note that is may lag on older/slower systems to render.county_pal_water (County)API: https://maps.co.palm-beach.fl.us/arcgis/rest/services/OpenData/Environment_Open_Data/MapServerDQ: Detailed and Not Detailed (automatically enabled) versions of PBC water features. Detailed may lag somewhat.county_pal_municipal (MPO)API: https://services5.arcgis.com/79IoFXBn9ZeqmVlC/arcgis/rest/services/Test_File/FeatureServerDQ: Automatically enabled the “geo” attribute to “Municipality” to render only PBC municipalities. This MPO file also contains commissioner districts, special districts, community redevelopment agency (CRA) districts, the Port of Palm Beach, and a County outline if needed.natural_areas*This following group contains State and MPO maintained layers bulleted below. These layers and their symbologies are used to help match the ESRI Topographic Basemap.all_natural_areas (State)API: https://services.arcgis.com/9Jk4Zl9KofTtvg3x/ArcGIS/rest/services/FL_Conservation_Lands_web/FeatureServerUtilizes the marsh style symbology.static_county_natural_areas (MPO)API: Geoprocessed in file.A clipped version of the api layer below. This was to make geometry along coastlines cleaner.api_county_natural_areas (State)API: https://services.arcgis.com/9Jk4Zl9KofTtvg3x/ArcGIS/rest/services/FL_Conservation_Lands_web/FeatureServerDQ: To match the ESRI Topographic Basemap, a staff defined Definition Query was developed to highlight certain areas. The OBJECTID's included are: 105,109,755,823,1260,1359,1410,1723,1724,2426,2539,2713,2046,2045,1297,2654,826,592,2643,1404,204,900,832,2200,2803,233,53,2680,2056,747,1302,1397state_fl_basemapThis staff created layer was developed to consolidate the previous many separate county, Lake Okeechobee, and coastline geometries for easier use.API: Geoprocessed in file.State Boundary's API used as a base: https://geodata.myfwc.com/datasets/myfwc::florida-state-waters-and-land-boundary/explore?location=25.629877%2C-81.683769%2C6.98state_fl_waterThis staff created layer was developed to consolidate the previous many separate water layers by county for easier use.API: Geoprocessed in file.Lake Okeechobee water used as a base: https://services.arcgis.com/V4Rx2DXlIHdEvTZA/arcgis/rest/services/Okeechobee_lake/FeatureServer

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.

🇺🇸 미국

🇺🇸 미국

🇺🇸 미국

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/Land_Estate_Layers/FeatureServer

Collection of Feature Layers for early Broadband Initiative Work. 9-1-1 systems and telecommunications infrastructure also including mobile broadband deployment by technology type and by carrier.Non-DCRA data - collected by MatSu Borough from other Sources for very early Broadband Initiative research July 2021. Original Source as NotedPublic Safety Answering Points: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Public_Safety_Answering_Points/FeatureServer (Phone and email survey July 2020)Call Routing: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/FINAL_Call_Routing/FeatureServer (ATA Call Routing Survey 2020)Telecommunication Towers from FCC: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Cell_Towers_from_FCC/FeatureServer (8/3/2020 FCC Antenna Structure Registration (ASR) download Circa Jan 2024 see https://www.fcc.gov/wireless/systems-utilities/antenna-structure-registration. This may be already distributed in GIS form by the Homeland Infrastructure Foundation-Level Data (HIFLD) Portal (broken into various layers) see https://hifld-geoplatform.opendata.arcgis.com/Wireless Coverage 4G LTE: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_4GLTE_Wireless_Coverage/FeatureServer (FCC Form 477 data for Alaska using combined carriers delivering technology code 83)Wireless Coverage 3G 4G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_3G_4G_Wireless_Coverage/FeatureServer (FCC Form 477 data for Alaska using combined carriers delivering technology code 81, HSPA+)Wireless Coverage 3G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_3G_Wireless_Coverage/FeatureServer (Geographic extent of 3G wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)Wireless Coverage Analog: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_Analog_Wireless_Coverage/FeatureServer (Geographic extent of analog wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)Wireless Coverage 2G: https://services.arcgis.com/fX5IGselyy1TirdY/ArcGIS/rest/services/Alaska_2G_Wireless_Coverage/FeatureServer (Geographic extent of 2G wireless technology in Alaska compiled from all providers. Data from FCC Form 477 current as of June 2019)State Trooper Detachments (other than North Slope): https://services3.arcgis.com/3NvWZvRqANiCzqqd/ArcGIS/rest/services/AST_Detachments/FeatureServer (Alaska State Trooper Jurisdictions and Operational Area by Detachment. Revised 9/2020)This data has been visualized in a Geographic Information Systems (GIS) format and is provided as a service in the DCRA Information Portal by the Alaska Department of Commerce, Community, and Economic Development Division of Community and Regional Affairs (SOA DCCED DCRA), Research and Analysis section and was last posted on July 1, 2021. SOA DCCED DCRA Research and Analysis is not the authoritative source for this data. For more information and for questions about this data, see: Mat-Su Open Data