description: Geometry service for use in web applications.

This document links to the ArcGIS Server REST endpoint for NG9-1-1 boundary geometry. See the Working with VGIN Feature Services document for guidance in using these in desktop mapping software.Feature services are supported in ArcGIS Pro. ArcMap support started in version 10.1. If you are working with a version of ArcGIS Desktop 10.0 or older, please contact us at NG911GIS@vita.virginia.gov for support.Note: these service offerings are being updated and may not be immediately available. Please contact us at NG911GIS@vita.virginia.gov if you have questions or concerns. Link updated to the new https://vginmaps.vdem.virginia.gov/arcgis/rest/ environment 5 September 2024.Additional resources and recommendations on GIS related topics are available on the VGIN 9-1-1 & GIS page.

Water system boundaries sourced from various repositories spanning the five county study area joined with the WSP attribute table via PWSID field.

Jurisdictional Unit, 2022-05-21. For use with WFDSS, IFTDSS, IRWIN, and InFORM.This is a feature service which provides Identify and Copy Feature capabilities. If fast-drawing at coarse zoom levels is a requirement, consider using the tile (map) service layer located at https://nifc.maps.arcgis.com/home/item.html?id=3b2c5daad00742cd9f9b676c09d03d13.OverviewThe Jurisdictional Agencies dataset is developed as a national land management geospatial layer, focused on representing wildland fire jurisdictional responsibility, for interagency wildland fire applications, including WFDSS (Wildland Fire Decision Support System), IFTDSS (Interagency Fuels Treatment Decision Support System), IRWIN (Interagency Reporting of Wildland Fire Information), and InFORM (Interagency Fire Occurrence Reporting Modules). It is intended to provide federal wildland fire jurisdictional boundaries on a national scale. The agency and unit names are an indication of the primary manager name and unit name, respectively, recognizing that:There may be multiple owner names.Jurisdiction may be held jointly by agencies at different levels of government (ie State and Local), especially on private lands, Some owner names may be blocked for security reasons.Some jurisdictions may not allow the distribution of owner names. Private ownerships are shown in this layer with JurisdictionalUnitIdentifier=null,JurisdictionalUnitAgency=null, JurisdictionalUnitKind=null, and LandownerKind="Private", LandownerCategory="Private". All land inside the US country boundary is covered by a polygon.Jurisdiction for privately owned land varies widely depending on state, county, or local laws and ordinances, fire workload, and other factors, and is not available in a national dataset in most cases.For publicly held lands the agency name is the surface managing agency, such as Bureau of Land Management, United States Forest Service, etc. The unit name refers to the descriptive name of the polygon (i.e. Northern California District, Boise National Forest, etc.).These data are used to automatically populate fields on the WFDSS Incident Information page.This data layer implements the NWCG Jurisdictional Unit Polygon Geospatial Data Layer Standard.Relevant NWCG Definitions and StandardsUnit2. A generic term that represents an organizational entity that only has meaning when it is contextualized by a descriptor, e.g. jurisdictional.Definition Extension: When referring to an organizational entity, a unit refers to the smallest area or lowest level. Higher levels of an organization (region, agency, department, etc) can be derived from a unit based on organization hierarchy.Unit, JurisdictionalThe governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.Definition Extension: 1) Ultimately responsible for the fire report to account for statistical fire occurrence; 2) Responsible for setting fire management objectives; 3) Jurisdiction cannot be re-assigned by agreement; 4) The nature and extent of the incident determines jurisdiction (for example, Wildfire vs. All Hazard); 5) Responsible for signing a Delegation of Authority to the Incident Commander.See also: Unit, Protecting; LandownerUnit IdentifierThis data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit.Landowner Kind & CategoryThis data standard provides a two-tier classification (kind and category) of landownership. Attribute Fields JurisdictionalAgencyKind Describes the type of unit Jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, and Other. A value may not be populated for all polygons.JurisdictionalAgencyCategoryDescribes the type of unit Jurisdiction using the NWCG Landowner Category data standard. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State. A value may not be populated for all polygons.JurisdictionalUnitNameThe name of the Jurisdictional Unit. Where an NWCG Unit ID exists for a polygon, this is the name used in the Name field from the NWCG Unit ID database. Where no NWCG Unit ID exists, this is the “Unit Name” or other specific, descriptive unit name field from the source dataset. A value is populated for all polygons.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Standard Unit Identifier (Unit ID). Where it is unknown, the value is ‘Null’. Null Unit IDs can occur because a unit may not have a Unit ID, or because one could not be reliably determined from the source data. Not every land ownership has an NWCG Unit ID. Unit ID assignment rules are available from the Unit ID standard, linked above.LandownerKindThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. There are three valid values: Federal, Private, or Other.LandownerCategoryThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State, Private.DataSourceThe database from which the polygon originated. Be as specific as possible, identify the geodatabase name and feature class in which the polygon originated.SecondaryDataSourceIf the Data Source is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if Data Source is "PAD-US 2.1", then for a USDA Forest Service polygon, the Secondary Data Source would be "USDA FS Automated Lands Program (ALP)". For a BLM polygon in the same dataset, Secondary Source would be "Surface Management Agency (SMA)."SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.MapMethod:Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality. MapMethod will be Mixed Method by default for this layer as the data are from mixed sources. Valid Values include: GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; DigitizedTopo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Phone/Tablet; OtherDateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using 24 hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature. GeometryIDPrimary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JoinMethodAdditional information on how the polygon was matched information in the NWCG Unit ID database.LocalNameLocalName for the polygon provided from PADUS or other source.LegendJurisdictionalAgencyJurisdictional Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.LegendLandownerAgencyLandowner Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.DataSourceYearYear that the source data for the polygon were acquired.Data InputThis dataset is based on an aggregation of 4 spatial data sources: Protected Areas Database US (PAD-US 2.1), data from Bureau of Indian Affairs regional offices, the BLM Alaska Fire Service/State of Alaska, and Census Block-Group Geometry. NWCG Unit ID and Agency Kind/Category data are tabular and sourced from UnitIDActive.txt, in the WFMI Unit ID application (https://wfmi.nifc.gov/unit_id/Publish.html). Areas of with unknown Landowner Kind/Category and Jurisdictional Agency Kind/Category are assigned LandownerKind and LandownerCategory values of "Private" by use of the non-water polygons from the Census Block-Group geometry.PAD-US 2.1:This dataset is based in large part on the USGS Protected Areas Database of the United States - PAD-US 2.`. PAD-US is a compilation of authoritative protected areas data between agencies and organizations that ultimately results in a comprehensive and accurate inventory of protected areas for the United States to meet a variety of needs (e.g. conservation, recreation, public health, transportation, energy siting, ecological, or watershed assessments and planning). Extensive documentation on PAD-US processes and data sources is available.How these data were aggregated:Boundaries, and their descriptors, available in spatial databases (i.e. shapefiles or geodatabase feature classes) from land management agencies are the desired and primary data sources in PAD-US. If these authoritative sources are unavailable, or the agency recommends another source, data may be incorporated by other aggregators such as non-governmental organizations. Data sources are tracked for each record in the PAD-US geodatabase (see below).BIA and Tribal Data:BIA and Tribal land management data are not available in PAD-US. As such, data were aggregated from BIA regional offices. These data date from 2012 and were substantially updated in 2022. Indian Trust Land affiliated with Tribes, Reservations, or BIA Agencies: These data are not considered the system of record and are not intended to be used as such. The Bureau of Indian Affairs (BIA), Branch of Wildland Fire Management (BWFM) is not the originator of these data. The

This layer is a component of Fairfield Parcel Geometry Service.

© Town of Fairfield

This layer is a component of Stratford Parcel Geometry Service.

© Town of Stratford, GBRC

Polygon geometry with attributes displaying barricade services areas in East Baton Rouge Parish, Louisiana.Metadata

Polygon geometry with attributes displaying public service commission districts in East Baton Rouge Parish, Louisiana.

Point geometry with attributes displaying food service program locations for summer youth meals in East Baton Rouge Parish, Louisiana.

Analysis of ‘Wake County Public Schools’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/511b0308-3986-4d24-ab11-b9d2cccc85b9 on 27 January 2022.

--- Dataset description provided by original source is as follows ---

Wake County Public School System schools data - locations, grade levels, magnet, Title 1, capacity

Updated 8-31-2015

Source: https://services1.arcgis.com/a7CWfuGP5ZnLYE7I/arcgis/rest/services/WakeCountyPublicSchools/FeatureServer/0

Metadata: Wake County Public Schools

License Wake County Geographic Information Services

--- Original source retains full ownership of the source dataset ---

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

Polygon geometry with attributes displaying garbage service pick-up days in East Baton Rouge Parish, Louisiana.Metadata

The Utility Coverage Area map service displays polygon geometry and attributes for all electricity utility service areas in East Baton Rouge Parish, Louisiana. Information was gathered from the Louisiana Public Service Commission website at https://www.lpsc.louisiana.gov/Maps_Electric_Distribution_Areas.aspx and from the City-Parish Department of Transportation and Drainage.

Please see FAQ for latest information on COVID-19 Data Hub data flows: https://covid-19.geohive.ie/pages/helpfaqs.Notice:See the Technical Data Issues section in the FAQ for information about issues in data: https://covid-19.geohive.ie/pages/helpfaqs.Deaths: From 16th May 2022 onwards, reporting of Notified Deaths will be weekly (each Wednesday) with total deaths notified since the previous Wednesday reported. This is based on the date on which a death was notified on CIDR, not the date on which the death occurred. Data on deaths by date of death is available on the new HPSC Epidemiology of COVID-19 Data Hub https://epi-covid-19-hpscireland.hub.arcgis.com/.This Layer contains Covid-19 Daily Statistics for Ireland by County polygon as reported by the Health Protection Surveillance Centre. This service is updated once a week, each Wednesday, which includes data for the full time series.

Point geometry with attributes displaying 311 service requests in East Baton Rouge Parish, Louisiana.Data points represent closed requests

Polygon geometry with attributes displaying recycling service pick-up days in East Baton Rouge Parish, Louisiana.Metadata

This dataset provides the centreline of railway track, each polyline segment representing a KiwiRail asset record. Depiction of each main line, yard track, loop, and link, and identifies it's nearest location (using a KiwiRail location name) and asset ID number. Does not include Private Sidings or privately owned track.

This data is suitable for mapping but not for survey accurate information or exporting to CAD for design (does not include true track geometry/design or elevation).

Supplied as ESRI Feature Service (polyline) in NZTM, spatial accuracy +/- 0.5m

NOTE: for a simplified version of the track data for more generic mapping, please use the NZ Railway Network dataset.

Polygon geometry with attributes displaying United States Postal Service Zone Improvement Plan (ZIP) Codes in East Baton Rouge Parish, Louisiana.

This layer was deprecated on 12/31The layer will still be publicly available, but no longer update. Information and links on how to access the new updated feature service in ArcGIS Marketplace will be posted here soonSafeGraph is just a data company. That's all we do.Social Distancing MetricsDue to the COVID-19 pandemic, people are currently engaging in social distancing. In order to understand what is actually occurring at a census block group level, SafeGraph is offering a temporary Social Distancing Metrics product. This product is delivered daily (3 days delayed from actual).The data was generated using a panel of GPS pings from anonymous mobile devices. We determine the common nighttime location of each mobile device over a 6 week period to a Geohash-7 granularity (~153m x ~153m). For ease of reference, we call this common nighttime location, the device's "home". We then aggregate the devices by home census block group and provide the metrics set out below for each census block group.To preserve privacy, we apply differential privacy to all of the device count metrics other than the device_count.SchemaColumn NameDescriptionTypeExampleorigin_census_block_groupThe unique 12-digit FIPS code for the Census Block Group. Please note that some CBGs have leading zeros.String131000000000date_range_startStart time for measurement period in ISO 8601 format of YYYY-MM-DDTHH:mm:SS±hh:mm (local time with offset from GMT). The start time will be 12 a.m. of any day.String2020-03-01T00:00:00-06:00date_range_endEnd time for measurement period in ISO 8601 format of YYYY-MM-DDTHH:mm:SS±hh:mm (local time with offset from GMT). The end time will be the following 12 a.m.String2020-03-02T00:00:00-06:00device_countNumber of devices seen in our panel during the date range whose home is in this census_block_group. Home is defined as the common nighttime location for the device over a 6 week period where nighttime is 6 pm - 7 am. Note that we do not include any census_block_groups where the count <5.Integer100distance_traveled_from_homeMedian distance traveled from the geohash-7 of the home by the devices included in the device_count during the time period (excluding any distances of 0). We first find the median for each device and then find the median for all of the devices.Integer200completely_home_device_countOut of the device_count, the number of devices which did not leave the geohash-7 in which their home is located during the time period.Integer40median_home_dwell_timeMedian dwell time at home geohash-7 ("home") in minutes for all devices in the device_count during the time period. For each device, we summed the observed minutes at home across the day (whether or not these were contiguous) to get the total minutes for each device. Then we calculate the median of all these devices.Integer1200part_time_work_behavior_devicesOut of the device_count, the number of devices that spent one period of between 3 and 6 hours at one location other than their geohash-7 home during the period of 8 am - 6 pm in local time. This does not include any device that spent 6 or more hours at a location other than home.Integer10full_time_work_behavior_devicesOut of the device_count, the number of devices that spent greater than 6 hours at a location other than their home geohash-7 during the period of 8 am - 6 pm in local time.Integer0For data definitions and complete documentation visit SafeGraph Developer and Data Scientist Docs.For statistics on the dataset, see SafeGraph 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

This service provides all the information for the Roadway Weather Information System (RWIS) camera photos. It contains the last 10 photos for each RWIS camera position. This data is updated every 5 minutes. This service feeds Iowa DOT's WeatherView ApplicationNote: This data is designed to be used with other RWIS feature services, like RWIS_Atmospheric_Data to get geometry.The weather data provided here by the Iowa Department of Transportation only reflects conditions at the specified site. Because of Iowa weather patterns, conditions can vary greatly in a small area; i.e., weather conditions a few miles away from the sensor could be completely different. In addition, failure of the sensors, or the equipment processing the information, may occur and produce unreliable information. Therefore, this information should not be used as the only factor in determining whether to travel in a particular area. The Iowa DOT recommends you check a number of sources, including media weather reports, in making your travel plans.