A point layer showing the geodetic control monuments in King George County. The file contains links to each control monument's respective datasheet.
The water tower layer was created using a Service Authority utility spreadsheet and aerial imagery to fix any spatial inaccuracies.
The Transforming Neighborhoods Initiative (TNI) focuses and aligns government efforts in six geographic areas throughout the county with the goal to improve the quality of life. The map below represents the areas that are part of this initiative. This map is refreshed when needed.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Esri ArcGIS Online (AGOL) Map Image Layer for accessing the Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product.Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones consists of polygon geometric features which represent the geographic areas throughout the State of Maryland that are impacted by CRAB inundation (0 to 1ft, 1 to 2ft, and 2ft or more).The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created using a GIS spatial analysis model, unique for each county in the State of Maryland. Coastal counties follow an analysis methodology that incorporates FEMA Stillwater wave action as it is understood from the FEMA identified VE zones. A Water Surface Elevation (WSE) and Still Water Elevation (SWEL) rasters are used as the baseline to identify existing water depths within each county. For all flood zones that are not classified as VE the WSE three feet was added to reflect a three-foot rise in the base flood elevations. For those WSEs falling within a FEMA floodplain identified V Zone, six feet was added (three feet for the increase in flood elevations for the CS-CRAB, and 3 feet to compensate for the minimum of 3 foot wave action typically mapped by FEMA) / wave heights greater than 3 feet were reduced to the 3 foot minimum for consistency across the shoreline. The newly calculated WSE plus three datasets were then converted to points and merged. Next, an Inverse Distance Weighted (IDW) Interpolation was used to compute the proportional weighted values between the WSE point locations based on proximity. The DEM for each county is then subtracted from the new IDW raster in order to show precise water locations as they relate to the land elevation, producing a freeboard depth grid representing the depth of flood waters above the existing ground elevation given a 3 foot increase in water level. A course resolution QAQC was applied to remove “islands” of data associated with DEM inaccuracies and other elevation anomalies. The analysis was run at a1 ft x 1 ft raster resolution. The DEM accuracy for each county varies based what is currently available. Here the breakdown of DEM accuracy for each county used in this project: Anne Arundel County DEM year is 2017 and horizontal resolution is 1ft. Baltimore County DEM year is 2015 and horizontal resolution is 2.5ft. Baltimore City DEM year is 2015 and horizontal resolution is 0.7m. Calvert County DEM year is 2017 and horizontal resolution is 1ft. Caroline County DEM year is 2013 and horizontal resolution is 3.125ft. Cecil county DEM year is 2013 and horizontal resolution is 0.6m. Charles County DEM year is 2014 and horizontal resolution is 0.9m. Dorchester County DEM year is 2013 and horizontal resolution is 0.9m. Harford County DEM is 2013 and horizontal accuracy is 1.5m. Kent County DEM year is 2015 and horizontal resolution is 0.7m. Prince George’s County DEM year is 2014 and horizontal resolution is 0.7m. Queen Anne’s County DEM year is 2013 and horizontal resolution is 0.6m. Somerset County DEM year is 2012 and horizontal accuracy is 1m. St Mary’s County DEM year is 2014 and Horizontal accuracy is 0.9m. Talbot County DEM year is 2015 and Horizontal accuracy is 0.7m. Wicomico County DEM year is 2012 and horizontal accuracy is 1m. Worchester County DEM year is 2011 and horizontal accuracy is 1m.The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created by the Maryland Environmental Service (MES) in partnership with the Maryland Department of Environment (MDE) and the Coast Smart Council, under the guidance of the Maryland Department of Natural Resource (DNR).For additional information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.
State of Maryland municipality boundary dataset.Maryland Department of Planning (MDP) maps annexations from municipalities. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:MUN_NAME (Municipality Name): Name of Municipality located in Maryland.RESOLUTION_NUMBER (Resolution Number): Local Municipality Annexation Resolution Number.ANNEXATION_DATE (Annexation Date) (DD/MM/YYYY): The Annexation Date field shows when there's been a change in the boundary. This date is known as the “Effective Date” from the municipality. The date 1/1/1997 is used as a default date of when annexation changes were first indicated in the GIS layer and not necessarily of when it was actually annexed. If there's a date of 1/1/1997, it can be assumed that the annexation occurred on this date or before. For example, for Baltimore City, the city boundary was determined hundreds of years ago. Other than that default date, the date will show when the property was annexed. ACRES (GIS Acres): GIS calculated acresJURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).
REQUIRED: A brief narrative summary of the data set.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.
On March 12, 1813, the legislators of the State of New York signed into law a bill that removed the area today known as Warren County from its parent county of Washington. It was named Warren County after Revolutionary War General Joseph Warren. At the time of its formation, 9 of 11 towns were already operating their municipal governments! A popular tourist and recreation destination, Warren County, together with its towns, the City of Glens Falls, and the Village of Lake George work diligently every day to serve the residents and visitors alike!
State of Maryland Priority Funding Area boundary dataset.This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:CPFA (Certified PFA): If field is populated as “IN” then the PFA has been designated at a Priority Funding Area locally. MUN_CODE (Municipality Code): MUN = within Priority Funding Area (PFA); MUNCOM = PFA with comment; MUN_NONPFA = not in PFARural Village Code (RUVI_CODE): RV = within a Rural VillageRural Village Name (RUVI_NAME): Name of the Rural VillageCOMMENT_STATUS (Comment Status): If field is populated with “NO” then there is no state-placed comment on the area. If the field is populated with “YES” then the state has placed a comment on the area based on eligibility.ACRES (GIS Acres): GIS calculated acres.JURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).CERT_DATE (Certification Date) (DD/MM/YYYY): This date is known as the “Certification Date” of the PFA. The date 1/1/1997, or NULL, is used as a default date of when the PFA was certified were first indicated in the GIS layer and not necessarily of when it was actually certified. If there's a date of 1/1/1997, it can be assumed that the PFA was certified on, or before this date. STATE_ELIGIBLE_STATUS (State Eligible): This field is based on whether the PFA has a comment. If there is no comment, then the field will be populated with YES; if there is a state-placed comment, the field will be populated with NO. "Date Last Updated 07/15/2024
Not seeing a result you expected?
Learn how you can add new datasets to our index.
A point layer showing the geodetic control monuments in King George County. The file contains links to each control monument's respective datasheet.