Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Point data set created from latitude and longitude coordinates containing the location of surface wells in Alaska. Created from Alaska Oil and Gas Conservation Commission (AOGCC) data extract, which is published monthly.

The new Oregon Address Geocoder is used to find the location coordinates for street addresses in the State of Oregon. This service is:FreePublicUpdated regularlyOutputs location coordinates in Oregon Lambert, feet (SRID 2992)Uses over 2 million address points and 288,000 streets for referenceIt is an ArcGIS multirole locator with two roles:Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.Street Address - Less accurate results from an estimated distance along a street centerline address range if a Point Address was not found.Instructions for using the Geocoder via ArcGIS Pro, ArcGIS Online, and REST Services are below:ArcGIS ProWeb ServicesArcGIS Online

Township boundaries were generated from radian measurements of township corner coordinates, represented to the nearest 0.001 second, recorded on official protraction diagrams of the state from BLM and ADNR. ADNR used 1994 AEH coordinate files from BLM as the basis of its work. BLM provided information for 18,654 land-based townships, and ADNR added another 774 (prior to 1996) townships that cover marine areas. Based on ADNR research, corner coordinates were modified for approximately 600 townships to correct the east-west and/or north-south alignment of neighboring townships. ADNR research also ensured that townships match across meridian lines.

Out of a total 19,425 townships currently defined for the state, 52 were identified by BLM as being irregular, that is, they cannot be describe by four corner points. During ADNR processing, many other minor adjustments were made to resolve spatial anomalies. Irregular townships are outlined using as many corner points as necessary, which was typically six to represent L-shaped townships. Many complex townships, including those along the US/Canadian border and those where meridians join, are described by more than six corner points; a few by only 3 points.

Using a geographic projection, ADNR created a double-precision coverage for the entire state from a compilation of the regular and irregular townships. Several iterations using ARC/INFO were required to find and resolve discrepancies in the tabular database. Arcs were densified while the township outlines were still in a geographic projection, to maintain the proper curvature of boundary lines during subsequent projection to other coordinate systems. The final result is a set of statewide coverages, both single-precision and double-precision, in both the Albers projection and geographic coordinates. The final coverages maintain as closely as possible the original protracted coordinate values.

Township boundaries were generated from radian measurements of township corner coordinates, represented to the nearest 0.001 second, recorded on official protraction diagrams of the state from BLM and ADNR. ADNR used 1994 AEH coordinate files from BLM as the basis of its work. BLM provided information for 18,654 land-based townships, and ADNR added another 774 (prior to 1996) townships that cover marine areas. Based on ADNR research, corner coordinates were modified for approximately 600 townships to correct the east-west and/or north-south alignment of neighboring townships. ADNR research also ensured that townships match across meridian lines.

Out of a total 19,425 townships currently defined for the state, 52 were identified by BLM as being irregular, that is, they cannot be describe by four corner points. During ADNR processing, many other minor adjustments were made to resolve spatial anomalies. Irregular townships are outlined using as many corner points as necessary, which was typically six to represent L-shaped townships. Many complex townships, including those along the US/Canadian border and those where meridians join, are described by more than six corner points; a few by only 3 points.

Using a geographic projection, ADNR created a double-precision coverage for the entire state from a compilation of the regular and irregular townships. Several iterations using ARC/INFO were required to find and resolve discrepancies in the tabular database. Arcs were densified while the township outlines were still in a geographic projection, to maintain the proper curvature of boundary lines during subsequent projection to other coordinate systems. The final result is a set of statewide coverages, both single-precision and double-precision, in both the Albers projection and geographic coordinates. The final coverages maintain as closely as possible the original protracted coordinate values.

This dataset provides a digital geospatial representation of regulated facility outfalls using data derived from various source data. The process by which this data set has been developed has been guided by Maryland Department of the Environment (MDE) and is the result of multiple geoprocesses. It is important to note that point locations are approximate and many do not represent exact geographic locations of outfalls, rather the parcel that they are located in. It is also important to note that in some cases, due to the way the data was processed, outfalls and facilities may have the same coordinates, leading to points being stacked.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://geodata.md.gov/imap/rest/services/Environment/MD_PointSourceDischarges/FeatureServer/1

SafeGraph is just a data company. That's all we do.SafeGraph Places for ArcGIS is a subset of SafeGraph Places. SafeGraph Places is a points-of-interest (POI) dataset with business listing, building footprint, visitor insights, & foot-traffic data for every place people spend money in the U.S.The complete SafeGraph Places dataset has ~ 5.4 million points-of-interest in the USA and is updated monthly (to reflect store openings & closings).Here, for free on this listing, SafeGraph offers a subset of attributes from SafeGraph Places: POI business listing information and POI locations (building centroids).Columns in this dataset:safegraph_place_idparent_safegraph_place_idlocation_namesafegraph_brand_idsbrandstop_categorystreet_addresscitystatezip_codeNAICS codeGeometry Point data. Latitude and longitude of building centroid.For data definitions and complete documentation visit SafeGraph Developer and Data Scientist Docs.For statistics on the dataset, see SafeGraph Places Summary Statistics.Data is available as a hosted Feature Service to easily integrate with all ESRI products in the ArcGIS ecosystem.Want More? Want this POI data for use outside of ArcGIS Online? Want POI data for Canada? Want POI building footprints (Geometry)?Want more detailed category information (Core Places)?Want phone numbers or operating hours (Core Places)?Want POI visitor insights & foot-traffic data (Places Patterns)?To see more, preview & download all SafeGraph Places, Patterns, & Geometry data from SafeGraph’s Data Bar.Or drop us a line! Your data needs are our data delights. Contact: support-esri@safegraph.comView Terms of Use

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID.This data set represents lake water qality monitoring sites based on the generation of points from latitude, longitude coordinates furnished by the Utah Department of Environmental Quality, Division of Water Quality (DWQ).

This feature service displays all disclosable soil descriptions (pedons) mined directly from the USDA-NRCS National Soil Information System (NASIS) Database. It is intended for NRCS-Soil and Plant Science Division (SPSD) employees, NRCS soil scientists, and National Cooperative Soil Survey Cooperators.The service can be opened in an ArcMap or ArcGIS Pro session by clicking on the upper right option ‘Open in ArcGIS Desktop’ and choose ArcMap or ArcGIS Pro. To add the service to an existing ArcGIS Pro session following the instructions here. To download all NASIS Pedon related tables use the NCSS-Pedons ArcGIS Toolbox. The feature service can also be accessed through other popular platforms such as QGIS and R by authenticating with your NRCS ArcGIS Online username and password.FYI for SPSD users: Pedons are rendered into a point layer using the Std Latitude and Std Longitude coordinates from the Site table with attributes from the pedon table as sourced from the NASIS Pedon Object. If a pedon does not have coordinates populated in the Site table, then a Longitude (X) and Latitude (Y) of 0.0 E and 90.0 N are used to represent the pedon. Pedons with an “Undisclosed Location” attribute in the Subcategory field from the Site Text table will not be published in this feature service.A pedon is a three-dimensional body of soil that has sufficient area (roughly 1 to 10 m2) and depth (up to 200 cm) to be used in describing the internal arrangement of horizons and in collecting representative samples for laboratory analysis.Currently, the NASIS Pedons feature layer contains 795,481 pedons and was last updated November 09 2023 at 10:21 PM CST.

The layer provides point coverage for known solid waste facilities in the State of New Hampshire. Points were identified through a combination of GPS, latitude and longitude, and aerial photography. Some points were taken from other DES-regulated program data co-located at the same facility.

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.

Area Covered: World

What can I do with this layer?
The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.


It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.

Attribute Information

• Latitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?
• Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.
• Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?
• Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.
  
• Acquisition Date: Derived Date/Time field combining Date and Time attributes.
• Satellite: Whether the detection was picked up by the Terra or Aqua satellite.
• Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.
• Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.
• Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.
• FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).
• DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.
• Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.

This map is provided for informational purposes and is not monitored 24/7 for accuracy and

A layer item maintained by a Live Feed routine that regularly computes the approximate location of the Sun, perpendicular to the planet, using the current UTC date and time. Watch as the Sun, Day/Night Terminator, and Horizon pass over your map, highlighting what areas are in dusk, darkness, and dawn. Terminator Polygons include a GeoEnriched attribute containing the approximate Total Population experiencing twilight or darkness.Originally inspired by Jim Blaney's JSAPI item, the data is maintained by a modified Python routine adapted from John Gravois' GitHub JSAPI "midnight-commander" project. Small corrections and enhancements provide the Sub-Solar Point (Sun's location on the planet), the Horizon line (mid-line of the Sun that meets the horizon), and the Twilight features showing dusk and dawn as the Sun reflects light in the atmosphere.Twilight, also known as Dawn and Dusk, is the visible reflective light in the atmosphere as the Sun dips below (Dusk) or approaches (Dawn) the Horizon. Three stages of Twilight are classified at 6 degree increments, producing various shades of darkness and vibrant colors.Civil Twilight is the first stage as the Sun moves below the Horizon (Dusk) or the last as the Sun approaches the Horizon (Dawn). Enough natural light exists for people to see without needing artificial light. Celestial objects are not yet visible.Nautical Twilight is the second stage. Artificial light is now helpful and Celestial objects can be seen with ease. Ships find it difficult to navigate by the Horizon.Astronomical Twilight is the last stage before darkness sets in. Only distant clouds are a glow on the Horizon with bright stars in full view.What can I do with this layer?A continually updated visual representation of this daily cycle provides an additional source of information for planners and decision makers that operate in an environment that is impacted by the day/night cycle. This may include logistics and fleet management, maritime, law enforcement, as well as other first responders who are engaged in search and rescue operations where daylight is critical to mission execution.Example item using Terminator to blend the Earth at Night tile image.Source:Calculation for the Position of the Sun (declination angle of the Sun)Alternate calculation for Equation of time (used to compute Sun's position)Reference details for TwilightUpdate Frequency:  Every 10 minutes (at 5, 15, 25, ...) using the Aggregated Live Feed MethodologyArea Covered: The worldCoordinate System: GCS_WGS_1984, wkid: 4326, with Latitude limited to ±87.5 degrees for maximum compatibility.Layers:Celestial Bodies: Point layer containing current location of the Sun as it is passes directly overhead, perpendicular to the planet.Horizon: Polyline layer containing the mid-line of the Sun as it sets in the horizon.Terminator: Polygon layer containing the 6 degree transitions from sunlight to civil, nautical, and astronomical Twilight (dawn and dusk) plus areas experiencing the dark of night. Also includes output from ArcGIS Online GeoEnrichment attribute field "KeyGlobalFacts.TOTPOP" containing the approximate Total Population covered by each Polygon.Sample: See animation of data mapped at midnight each day for one year.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

This Africa Geocoding locator is a view of the World Geocoding Service constrained to search for places in the countries of Africa. The World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The result might be displayed on the map, but the result is not stored in any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a database. Mapping is not always involved, but placing the results on a map may be part of a workflow. Batch geocoding falls into this category. Geocoding requires a subscription. An ArcGIS Online subscription will provide you access to the World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the World Geocoding service documentation.

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX) recordFire Discovery Date is in the year 2025Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. For a complete set of features that meet the same IRWIN criteria, see the 2025 Wildland Fire Incident Locations to Date service.No "fall-off" rules are applied to this service. Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_InitialResponseDateTimeThe date/time of the initial response to the incident. More specifically when the IC arrives and performs initial size up. attr_IrwinIDUnique identifier assigned to each incident record in IRWIN.attr_IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.attr_IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.attr_IsMultiJurisdictionalIndicates if the

U.S. Census Populated Place Areas represents the 2020 U.S. Census populated place areas of the United States that include incorporated places, cities, and census designated places identified by the U.S. Census Bureau.This layer is updated annually. The geography is sourced from U.S. Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrography to add a detailed coastline for cartographic purposes. Attribute fields include 2020 total population from the U.S. Census Public Law 94 data. The Population Class field values represent population ranges as follows:Population from 0 - 249Population from 250 - 499Population from 500 - 999Population from 1,000 - 2,499Population from 2,500 - 9,999Population from 10,000 - 49,999Population from 50,000 - 99,999Population from 100,000 - 249,999Population from 250,000 - 499,999Population 500,000 and overThis ready-to-use layer can be used in ArcGIS Pro and in ArcGIS Online and its configurable apps, dashboards, StoryMaps, custom apps, and mobile apps. The data can also be exported for offline workflows. Cite the 'U.S. Census Bureau' when using this data.

This is a Locator for finding British National Grid references. It provides lookups on the British National Grid, which can be applied to all Ordnance Survey maps of Great Britain. You can use it to query by absolute coordinates or by tile. Both types of query return the centre point of the corresponding 10k grid square BNG tile. Enter grid coordinates as absolute XY: 123456, 654321 Enter tile queries as Grid squares: TL44; as sub tile: TQ1234 or; as quadrant SN1234SE

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. These datasets exist in raster and vector formats. The vector format was created from the SHA Shoreline file and graphic representations in the Lippson book (See bibliography below). These areas were then overlane with a point file created from lat/long collected during the surveys conducted by O'dell - Mowrer - and Uphoff of MD DNR Fisheries Service. This was done to verify that the graphic representations were accurate. These data sets were then converted to raster format and reclassified with a rank determined by DNR biologists. This rank determines level of habitat importance with spawning areas ranking highest and adult areas of bay depth below 3 feet ranking the lowest. These ranked rasters were then stacked and an output raster was created showing areas of high habitat diversity. These rasters were then clipped by county. Lippson - Alice Jane.the Chesapeake Bay in Maryland. an atlas of natural resources."" the Johns Hopkins University Press. Baltimore and London - 1973.Last Update: 05/2014Feature Service Link:http://geodata.md.gov/imap/rest/services/Biota/MD_Finfish/FeatureServer/6 ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively the ""Data"") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

Community Boundaries from Survey Points - Dukes County.This datalayer provides the legislatively authorized town boundary survey points for the 7 communities/Towns of Dukes County, Massachusetts. This layer contains points representing the coordinates of town corners and witness marks.Attribute Coordinates of North83 and East83 are in in NAD83 Mass. State Plane meters. The original dataset from MassGIS is in Mass Stateplane Mainland NAD83 meters. The dataset was NOT reprojected prior to upload into ArcGIS OnLine.The survey point locations depicted in this data set are based on coordinate values extracted from the 68-volume Harbor and Lands Commission Town Boundary Atlas for the 351 communities (cities and towns) in Massachusetts. The Atlas was published in the early 1900's and is maintained by the Survey Section of Massachusetts Highway Department.The Martha's Vineyard Commission downloaded the full MassGIS Town Survey Points dataset in June of 2020 and extracted only those points within Dukes County. While the State-wide dataset has been updated, since this download, not modifications have applied to Dukes County towns.Full MassGIS Metadata

The U.S. Fish and Wildlife Service Corporate Master Table (CMT) is the official source of Service organization codes and related information. Information in the CMT includes, but is not limited to, organization codes, organization names, Federal Budget Management System (FBMS), cost center codes, fire unit identifiers, program names, mailing and physical/shipping addresses, telephone and fax numbers as well as latitude and longitude coordinates. The CMT enables all Service automated systems to utilize a corporate data set of known quality, eliminating the workload required to maintain each system's data set, and thereby facilitating data sharing. Other customers for the CMT are Service personnel who maintain directories, communicate with Congress and with the Public, maintain World Wide Web sites, etc. These spatial data were created using the information in the CMT. The CMT contains location information on all the offices within the Service that have an organization code. Unstaffed offices and some other facilities may not be included. The latitude and longitude points used are usually the location of the main administrative site. The latitude and longitude data is not completely verified but is the best we have at this time. This data set is intended to give an overview of where USFWS has stations across the United States and Territories, including locations outside the 50 states. It is not intended to be the exact location of every USFWS office. The CMT is primarily used for accounting purposes and therefore one location in the CMT can represent many different offices. Some points are duplicates where a station, most usually an Ecological Field Office, may be associated with more than one USFWS program. This data is updated from an internal authoritative source every night at 2:30am EST.For a direct link to the official Enterprise Geospatial dataset and metadata: https://ecos.fws.gov/ServCat/Reference/Profile/60076.Dataset contact: fwsgis@fws.gov

The NAD is a spatial database containing address data, point location coordinates, jurisdictions, record level metadata and other supporting data for addressable locations including structures, some sub-units within those structures and landmarks as included in the aggregated datasets from providers included therein.