The ArcGIS Online US Geological Survey (USGS) topographic map collection now contains over 177,000 historical quadrangle maps dating from 1882 to 2006. The USGS Historical Topographic Map Explorer app brings these maps to life through an interface that guides users through the steps for exploring the map collection:Find a location of interest.View the maps.Compare the maps.Download and share the maps or open them in ArcGIS Desktop (ArcGIS Pro or ArcMap) where places will appear in their correct geographic location. Save the maps in an ArcGIS Online web map.

Finding the maps of interest is simple. Users can see a footprint of the map in the map view before they decide to add it to the display, and thumbnails of the maps are shown in pop-ups on the timeline. The timeline also helps users find maps because they can zoom and pan, and maps at select scales can be turned on or off by using the legend boxes to the left of the timeline. Once maps have been added to the display, users can reorder them by dragging them. Users can also download maps as zipped GeoTIFF images. Users can also share the current state of the app through a hyperlink or social media. This ArcWatch article guides you through each of these steps: https://www.esri.com/esri-news/arcwatch/1014/envisioning-the-past.Once signed in, users can create a web map with the current map view and any maps they have selected. The web map will open in ArcGIS Online. The title of the web map will be the same as the top map on the side panel of the app. All historical maps that were selected in the app will appear in the Contents section of the web map with the earliest at the top and the latest at the bottom. Turning the historical maps on and off or setting the transparency on the layers allows users to compare the historical maps over time. Also, the web map can be opened in ArcGIS Desktop (ArcGIS Pro or ArcMap) and used for exploration or data capture.Users can find out more about the USGS topograhic map collection and the app by clicking on the information button at the upper right. This opens a pop-up with information about the maps and app. The pop-up includes a useful link to a USGS web page that provides access to documents with keys explaining the symbols on historic and current USGS topographic maps. The pop-up also has a link to send Esri questions or comments about the map collection or the app.We have shared the updated app on GitHub, so users can download it and configure it to work with their own map collections.

The ArcGIS Online USGS Topographic Maps image service contains over 181,000 historical topographic quadrangle maps (quads) dating from 1879 to 2006. These maps are part of the USGS Historical Topographic Map Collection (HTMC) which includes all the historical quads that had been printed since the USGS topographic mapping program was initiated in 1879. Previously available only as printed lithographic copies, the historical maps were scanned “as is” to create high-resolution images that capture the content and condition of each map sheet. All maps were georeferenced, and map metadata was captured as part of the process.

For the Esri collection, the scanned maps were published as this ArcGIS Online image service which can be viewed on the web and allows users to download individual scanned images. Esri’s collection contains historical quads (excluding orthophotos) dating from 1879 to 2006 with scales ranging from 1:10,000 to 1:250,000. The scanned maps can be used in ArcGIS Pro, ArcGIS Online, and ArcGIS Enterprise. They can also be downloaded as georeferenced TIFs for use in these and other applications.

We make it easy for you to explore and download these maps, or quickly create an ArcGIS Online map, using our Historical Topo Map Explorer app. The app provides a visual interface to search and explore the historical maps by geographic extent, publication year, and map scale. And you can overlay the historical maps on a satellite image or 3D hillshade and add labels for current geographic features.

The historic bathymetry maps were created using simple methods to determine lake depths and were meant for resource management purposes only.Bathymetry is the measurement of water depth in lakes. From the 1940s to the 1990s, the Ministry of Natural Resources and Forestry produced bathymetry maps for over 11,000 lakes across Ontario.The data can be used by the general public and GIS specialists for:climate change modellingfish monitoring and other ecological applicationshydrologic cycle modellingrecreational fishing mapswatershed-based water budgetingThe maps were created using simple methods to determine lake depths. They were meant for resource management purposes only. Little effort was made to identify shoals and other hazards when creating these bathymetric maps.Since this data was collected, many constructed and naturally occurring events could mean that the depth information is now inaccurate, so these maps should not be used for navigational purposes.In many cases, these maps still represent the only authoritative source of bathymetry data for lakes in Ontario.Technical informationThese maps are being converted to digital GIS line data which can be found in the Bathymetry Line data class.The Bathymetry Index data class identifies if GIS vector lines have been created and the location of mapped lakes.The historic paper maps have been scanned into digital files. We will add new digital files to this dataset if they become available.The digital files have been grouped and packaged by regions into 13 compressed (zipped) files for bulk download.Note: package 99 contains scanned maps where the location shown on the map could not be determined.Product PackagesHistoric Bathymetry Maps - Package 1 (ZIP)Historic Bathymetry Maps - Package 2 (ZIP)Historic Bathymetry Maps - Package 3 (ZIP)Historic Bathymetry Maps - Package 4 (ZIP)Historic Bathymetry Maps - Package 5 (ZIP)Historic Bathymetry Maps - Package 6 (ZIP)Historic Bathymetry Maps - Package 7 (ZIP)Historic Bathymetry Maps - Package 8 (ZIP)Historic Bathymetry Maps - Package 9 (ZIP)Historic Bathymetry Maps - Package 10 (ZIP)Historic Bathymetry Maps - Package 11 (ZIP)Historic Bathymetry Maps - Package 12 (ZIP)Historic Bathymetry Maps - Package 13 (ZIP)Historic Bathymetry Maps - Package 99 (ZIP)Additional DocumentationBathymetry User Guide (Word)Bathymetry Package Map (Word)Bathymetry Lookup Values (Excel)StatusCompleted: Production of the data has been completedMaintenance and Update FrequencyNot planned: There are no plans to update the dataContactOntario Ministry of Natural Resources - Geospatial Ontario,geospatial@ontario.ca

This application, HistoryQuest DC, is an interactive GIS map that provides historical data on approximately 193,000 extant buildings in Washington, D.C. The map offers several operational layers of information for the user including historic data on individual buildings and historic districts, links to documentation on properties listed in the National Register of Historic Places, information on historic residential subdivisions, and the identification and boundaries of the L’Enfant Plan, and the city’s Squares, and Wards. The featured layer in the map—the Historical Data on DC Buildings—provides information from a variety of sources on original dates of construction, architects, owners and builders of the city’s historic buildings. The application also includes a Query tool that allows the user to analyze the historic data within a specified geographic area or city-wide.This application has evolved out of the DC Historical Building Permits Database, begun in 2002, is on-going. Requests to correct or add new information can be made using the “Propose Data Change” drop-down form located on the banner at the top of the map.For questions or concerns, contact the Historic Preservation Office at historic.preservation@dc.gov.

Historical FiresLast updated on 06/17/2022OverviewThe national fire history perimeter data layer of conglomerated Agency Authoratative perimeters was developed in support of the WFDSS application and wildfire decision support for the 2021 fire season. The layer encompasses the final fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2021 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer:Alaska fire history USDA FS Regional Fire History Data BLM Fire Planning and Fuels National Park Service - Includes Prescribed Burns Fish and Wildlife ServiceBureau of Indian AffairsCalFire FRAS - Includes Prescribed BurnsWFIGS - BLM & BIA and other S&LData LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoratative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.AttributesThis dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer. (This unique identifier may NOT replace the GeometryID core attribute)INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name.FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT).AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin.SOURCE - System/agency source of record from which the perimeter came.DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy.MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; OtherGIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456.UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMPCOMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or UnknownGEO_ID - Primary 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. Globally Unique Identifier (GUID).Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4580 Records thru 2021), other federal sources for AK data removed. CA: GEOID = OBJECT ID of downloaded file geodatabase (12776 Records, federal fires removed, includes RX)FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2052 Records). Handful of WFIGS (11) fires added that were not in FWS record.BIA: GEOID = "FireID" 2017/2018 data (416 records) provided or WFDSS PID (415 records). An additional 917 fires from WFIGS were added, GEOID=GLOBALID in source.NPS: GEOID = EVENT ID (IRWINID or FRM_ID from FOD), 29,943 records includes RX.BLM: GEOID = GUID from BLM FPER and GLOBALID from WFIGS. Date Current = best available modify_date, create_date, fire_cntrl_dt or fire_dscvr_dt to reduce the number of 9999 entries in FireYear. Source FPER (25,389 features), WFIGS (5357 features)USFS: GEOID=GLOBALID in source, 46,574 features. Also fixed Date Current to best available date from perimeterdatetime, revdate, discoverydatetime, dbsourcedate to reduce number of 1899 entries in FireYear.Relevant Websites and ReferencesAlaska Fire Service: https://afs.ak.blm.gov/CALFIRE: https://frap.fire.ca.gov/mapping/gis-dataBIA - data prior to 2017 from WFDSS, 2017-2018 Agency Provided, 2019 and after WFIGSBLM: https://gis.blm.gov/arcgis/rest/services/fire/BLM_Natl_FirePerimeter/MapServerNPS: New data set provided from NPS Fire & Aviation GIS. cross checked against WFIGS for any missing perimeters in 2021.https://nifc.maps.arcgis.com/home/item.html?id=098ebc8e561143389ca3d42be3707caaFWS -https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/USFWS_Wildfire_History_gdb/FeatureServerUSFS - https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FireOccurrenceAndPerimeter_01/MapServerAgency Fire GIS ContactsRD&A Data ManagerVACANTSusan McClendonWFM RD&A GIS Specialist208-258-4244send emailJill KuenziUSFS-NIFC208.387.5283send email Joseph KafkaBIA-NIFC208.387.5572send emailCameron TongierUSFWS-NIFC208.387.5712send emailSkip EdelNPS-NIFC303.969.2947send emailJulie OsterkampBLM-NIFC208.258.0083send email Jennifer L. Jenkins Alaska Fire Service 907.356.5587 send email

This map service represents modeled streamflow metrics from the historical time period (1977-2006) in the United States. In addition to standard NHD attributes, the streamflow datasets include metrics on mean daily flow (annual and seasonal), flood levels associated with 1.5-year, 10-year, and 25-year floods; annual and decadal minimum weekly flows and date of minimum weekly flow, center of flow mass date; baseflow index, and average number of winter floods.�These files and additional information are available on the project� website,�https://www.fs.usda.gov/rm/boise/AWAE/projects/modeled_stream_flow_metrics.shtml. Streams without flow metrics (null values) were removed from this dataset to improve display speed; to see all stream lines, use an NHD flowline dataset.Hydro flow metrics data can be downloaded from�here.

The National Forest Climate Change Maps project was developed to meet the need of National Forest managers for information on projected climate changes at a scale relevant to decision making processes, including Forest Plans. The maps use state-of-the-art science and are available for every National Forest in the contiguous United States with relevant data coverage. Currently, the map sets include variables related to precipitation, air temperature, snow (including April 1 snow water equivalent (SWE), and snow residence time), and stream flow.

The year 2026 is an important one for not only Route 66, but the nation as a whole: the 250th anniversary of the Declaration of Independence will be celebrated July 4th, and November 11th marks one hundred years since the official dedication of the numbered highway system from which Route 66 was born. Both the country and the "Mother Road" share a rich history, with Route 66 serving as an icon through the nation's many eras of the past century.The route winds across the American West, a land with a history extending far beyond these anniversaries. One of the most interesting ways to explore the evolving identity of the region and the road is through the maps that were made to document them over the years. This contribution to the ROUTE 66 REMAP StoryMap series includes a collection of maps from the past several centuries, each adding a piece to the complex and fascinating story of Route 66. Using the power of GIS, we have not only georeferenced these maps, but also annotated them with different layers of data that enhance our understanding of the stories they tell.

The National Forest Climate Change Maps project was developed to meet the need of National Forest managers for information on projected climate changes at a scale relevant to decision making processes, including Forest Plans. The maps use state-of-the-art science and are available for every National Forest in the contiguous United States with relevant data coverage. Currently, the map sets include variables related to precipitation and air temperature, including both Alaskan and lower 48 datasets. Data from the lower 48 were downloaded from here: https://www.fs.usda.gov/rm/boise/AWAE/projects/national-forest-climate-change-maps.html, and Alaskan data came from here: https://www.snap.uaf.edu/tools/data-downloads. Historical data are compared with RCP 8.5 projections from the 2080s.A Raster Function Template is available in this service that will classify the data as originally intended by OSC. The RFT currently works in AGOL but not in ArcGIS Pro.

This tile service is derived from a digital raster graphic of the historical 15-minute USGS topographic quadrangle maps of coastal towns in Massachusetts. These quadrangles were mosaicked together to create a single data layer of the coast of Massachusetts and a large portion of the southeastern area of the state.The Massachusetts Office of Coastal Zone Management (CZM) obtained the map images from the Harvard Map Collection. The maps were produced in the late 1890s and early 20th century at a scale of 1:62,500 or 1:63,360 and are commonly known as 15-minute quadrangle maps because each map covers a four-sided area of 15 minutes of latitude and 15 minutes of longitude.

In the winter of 2013, the Detroit Blight Removal Task Force commissioned Data Driven Detroit (D3) to serve as the data management partner on Motor City Mapping, a comprehensive, city-wide data collection effort. As a part of this project, D3 was tasked with compiling existing information on historic districts in the City of Detroit, so that the city would be able to identify all areas and structures of historic significance. D3 compiled this dataset from a number of different sources, which ranged from existing shapefiles on the City of Detroit's website to drawing polygons manually based on descriptions from the Michigan State Historic Preservation Office (SHPO). D3 analysts then subjected the data to an extensive manual cleaning process, removing duplicates and reconciling conflicting boundaries. The resulting dataset contains boundaries for 656 features, including national, state, and locally-listed historic districts, as well as proposed/potential and eligible historic districts. This file is projected in NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113_Feet_Intl. Metadata associated with this file includes field description metadata and a narrative description of the process involved in creating this dataset. We look forward to seeing how this data can be used to inform decisions and conversations around historic preservation and historic buildings! If you would like to receive a more detailed process document that contains the step-by-step process of how this dataset was generated, please use the contact information contained in the above-listed files. For more information on the Motor City Mapping project, please visit www.motorcitymapping.org.

Abstract: This dataset displays locational information of the towns mapped by the Irish Historic Towns Atlas. The dataset provides links to the digital editions of each map, which include the full text (essay, topographical information, bibliography, appendices, notes) for each town or city, as well as select maps. Purpose: The Irish Historic Towns Atlas (IHTA) project was established in 1981. The aim of the project is to record the topographical development of a selection of Irish towns both large and small. Each town is published separately as a fascicle or folder and includes a series of maps complemented by a detailed text section. The Irish Historic Towns Atlas is part of a wider European scheme, with towns atlases containing broadly similar information available for a number of countries. Thus Irish towns can be studied in their European context.Metadata: https://www.arcgis.com/sharing/rest/content/items/d0f29ab3f3124d309823447e3e2ac192/data Link: https://www.ria.ie/irish-historic-towns-atlas-online

Bathymetry is the measurement of water depth in lakes. From the 1940s to the 1990s, the Ministry of Natural Resources and Forestry produced bathymetry maps for over 11,000 lakes across Ontario. The data can be used by the general public and GIS specialists for: * climate change modelling * fish monitoring and other ecological applications * hydrologic cycle modelling * recreational fishing maps * watershed-based water budgeting The maps were created using simple methods to determine lake depths. They were meant for resource management purposes only. Little effort was made to identify shoals and other hazards when creating these bathymetric maps. Since this data was collected, many constructed and naturally occurring events could mean that the depth information is now inaccurate, so these maps should not be used for navigational purposes. In many cases, these maps still represent the only authoritative source of bathymetry data for lakes in Ontario. Technical information These maps are being converted to digital GIS line data which can be found in the Bathymetry Line data class. The Bathymetry Index data class identifies if GIS vector lines have been created and the location of mapped lakes. The historic paper maps have been scanned into digital files. We will add new digital files to this dataset if they become available. The digital files have been grouped and packaged by regions into 13 compressed (zipped) files for download. Note: package 99 contains scanned maps where the location shown on the map could not be determined.

The data set identifies the six county-administered Historic and Cultural Conservation District areas within Loudoun County. The County-designated districts include six Historic and Cultural Conservation Districts (Aldie, Bluemont, Goose Creek, Oatlands, Taylorstown, and Waterford) and one Historic Roadways District (Beaverdam Creek). The Historic Districts are Zoning Overlay Districts and are subject to Loudoun County Zoning Ordinance, Article VI, Section 6-1800, Designation of Historic Districts and Section 6-1900, Permits in Historic Districts. The Beaverdam Creek Historic Roadways District differs from the other districts, as the Roadways District only includes the part of the parcel located within a 35-foot buffer in each direction from the centerline of a designated roadway. The Planning Department administers the County's Historic Districts Program.

This data set contains small-scale base GIS data layers compiled by the National Park Service Servicewide Inventory and Monitoring Program and Water Resources Division for use in a Baseline Water Quality Data Inventory and Analysis Report that was prepared for the park. The report presents the results of surface water quality data retrievals for the park from six of the United States Environmental Protection Agency's (EPA) national databases: (1) Storage and Retrieval (STORET) water quality database management system; (2) River Reach File (RF3) Hydrography; (3) Industrial Facilities Discharges; (4) Drinking Water Supplies; (5) Water Gages; and (6) Water Impoundments. The small-scale GIS data layers were used to prepare the maps included in the report that depict the locations of water quality monitoring stations, industrial discharges, drinking intakes, water gages, and water impoundments. The data layers included in the maps (and this dataset) vary depending on availability, but generally include roads, hydrography, political boundaries, USGS 7.5' minute quadrangle outlines, hydrologic units, trails, and others as appropriate. The scales of each layer vary depending on data source but are generally 1:100,000.

This data set contains small-scale base GIS data layers compiled by the National Park Service Servicewide Inventory and Monitoring Program and Water Resources Division for use in a Baseline Water Quality Data Inventory and Analysis Report that was prepared for the park. The report presents the results of surface water quality data retrievals for the park from six of the United States Environmental Protection Agency's (EPA) national databases: (1) Storage and Retrieval (STORET) water quality database management system; (2) River Reach File (RF3) Hydrography; (3) Industrial Facilities Discharges; (4) Drinking Water Supplies; (5) Water Gages; and (6) Water Impoundments. The small-scale GIS data layers were used to prepare the maps included in the report that depict the locations of water quality monitoring stations, industrial discharges, drinking intakes, water gages, and water impoundments. The data layers included in the maps (and this dataset) vary depending on availability, but generally include roads, hydrography, political boundaries, USGS 7.5' minute quadrangle outlines, hydrologic units, trails, and others as appropriate. The scales of each layer vary depending on data source but are generally 1:100,000.

CAL FIRE's Fire and Resource Assessment Program (FRAP) annually maintains and distributes an historical fire perimeter dataset from across public and private lands in California. The GIS data is developed with the cooperation of the United States Forest Service Region 5, the Bureau of Land Management, the National Park Service and the United States Fish and Wildlife Service and is released in the spring with added data from the previous calendar year. Although the dataset represents the most complete digital record of fire perimeters in California, it is still incomplete, and users should be cautious when drawing conclusions based on the data.

This app contains three pages of maps and documentation of the historical fire perimeter metadata:

Historical Fire Perimeters: The landing page highlights the recent large fires (≥5,000 acres) on a backdrop of all of the dataset's documented fire perimeters dating back to 1878. This map includes perimeters symbolized by decade, county boundaries, California Vegetation, and NAIP imagery back to 2005. This page provides users the ability to add their own data or filter the fire perimeter data. It cleanly lists fire perimeters shown on the map with their name, year, and GIS calculated acreage. The user can navigate to the CAL FIRE current incident webpage or provide comments to the dataset's steward.

Times Burned: The second page provides a map showing an analysis performed annually on the fire perimeter dataset to show case burn frequency from 1950 to present for fires greater than one acre.

Fire Across Time: This third page provides a time enabled layer of the fire perimeter dataset, featuring a time slider to allow users to view the perimeter dataset across time.

The final page provides the user with the dataset's metadata, including its most current data dictionary.

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

This GIS dataset contains growth tier maps adopted by local (county and municipal) jurisdictions under SB236. Data are generally collected from county and municipal jurisdictions by the Maryland Department of Planning (Planning) or digitized by Planning in coordination with local jurisdictions. For more information about SB236, see Planning’s Septics Law Implementation Website at https://planning.maryland.gov/Pages/OurWork/SB236Implementation.aspxThis document describes standard operating procedures for aggregating growth tier map GIS data. These procedures may not apply to historical data (i.e. records for which both the SRC_DATE and GIS_SRC fields are blank). For example, Planning may have realigned historical data from local jurisdictions to parcel polygon boundaries or used different procedures to represent municipal tiers when municipalities concurred with county tier maps.Planning generally requests updated GIS data once a jurisdiction notifies Planning that a growth tier map has been amended. Aggregated data may be outdated or incomplete if Planning has not yet received or processed GIS updates from jurisdictions. Planning generally does not alter geometries received from the local jurisdictions except to divide municipal tiers at the county boundary (see JURSCODE field description). This dataset may contain overlap where multiple jurisdictions designate tiers in the same area.Fields include:JURSCODE – MdProperty Viewjurisdiction code (four-letter county or Baltimore City code). For tiers designated by counties, this is the jurisdiction responsible for designating the growth tier. For tiers designated by municipalities, this is the jurisdiction in which the growth tier is physically located. Municipal tiers that cross counties are divided at the county boundary so this field can be populated. See the MUNI field for the municipality responsible for designating a municipal tier.County – Full name of the jurisdiction represented by the JURSCODE.MUNI – The name of the municipality responsible for designating the tier. This field will be blank (‘ ‘) if the tier has been designated by a county. The MUNI field is formatted consistently with municipality names in the Planning’s municipal boundary datasets. When municipalities adopt tier maps by concurring with county tiers instead of submitting tier data independently, the MUNI field remains blank within the entire county tier map dataset. Depending on internal needs, an independent municipal tier dataset may or may not be generated by Planning and included within the aggregated tiers.TIER – Growth tier identifier used by the source jurisdiction and standardized as Tier 1, Tier 1A, Tier 2, Tier 2A, Tier 3, and Tier 4. May include additional alphabetical annotations used by the jurisdictions such as Tier 2B. If the TIER_CODE field is 99, the TIER field retains the descriptor provided by the jurisdiction, which may be a blank or null value.TIER_CODE – Integer field containing the growth tier standardized by Planning: 1 (Tier I); 11 (Tier IA or any other annotated version of Tier I, such as IB, etc.); 2 (Tier II), 22 (Tier IIA or any other annotated version of Tier II, such as IIB, etc.); 3 (Tier III); 4 (Tier IV); 44 (Areas annotated as Tier IVA for municipal greenbelts or any other annotated version of Tier IV); 99 – Areas included in the jurisdiction’s growth tier GIS data that are not assigned a tier, such as rights-of-way or water.Adopt_Date – Date growth tier map was adopted or amended. When a local jurisdiction updates its growth tier map, Planning generally requests a comprehensive GIS update to replace all existing data for the jurisdiction.Acres – GIS acres calculated by Planning in NAD83 Meters (EPSG 26985)GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information Planning obtained, which concatenates the JURSCODE field (or MUNI field for municipal tier maps), followed by a space, followed by the name of the shapefile or feature class received from the jurisdiction. Field contains “MDP” if tiers were digitized by Planning, and is blank (‘ ‘) for historical data.SRC_DATE (GIS Source Date) – The date (YYYYMMDD) the GIS data were obtained by Planning from the local jurisdiction. If the month or day is unknown, the date is YYYY0000. If Planning digitized the growth tier map in coordination with a local jurisdiction, this should be the date Planning’s edits are verified by the jurisdiction. This field will be blank (‘ ’) if Planning’s edits have not been verified or if the dataset is historical and the source is unknown.NOTE – Text field containing additional notes about the dataLast Updated: 7/26/2023This is a Maryland Department of Planning hosted service. Find more information on https://imap.maryland.govMap Service Link: https://mdpgis.mdp.state.md.us/arcgis/rest/services/PlanningCadastre/Septic_Growth_Tiers/MapServer

Eelgrass Beds Historic Set:

Historic Eelgrass Points is a 1:24,000-scale, point feature-based layer that depicts the locations of historic eelgrass beds (Zostera marina) in Long Island Sound, the Connecticut River, the Quinnipiac River and other bays, harbors and waterbodies in Connecticut's coastal area. It also includes several points located along the north shore of Long Island. There are a total of 131 point features, the majority of which are located east of the Connecticut River. Point features in this layer are compiled from two major sources: 1) the polygon feature label points in the Historic Eelgrass Beds polygon layer representing sources with a mapping component; and 2) additional points that were based on historic literature review that had no mapping component. Source information including source description and collection date for each point is described in the layer's table data. Feature locations are inexact. Because of the variety of source maps and methods used for their automation, this coverage should be considered to have limited spatial accuracy and is appropriate for general uses only. Actual data collection ranged from 1873 through 1996. This layer was published in 1997 and is not updated. It does not represent current conditions.

Historic Eelgrass Bed Polygons is a 1:24,000-scale, polygon feature-based layer that depicts the locations of historic eelgrass beds (Zostera marina) in Long Island Sound and the Niantic River, as well as in other bays, harbors and waterbodies in Connecticut's coastal area. It also includes several points located along the north shore of Long Island. There are a total of 52 polygon features, all of which (except the Long Island points), are located within or east of the Niantic River. This layer can be used with Historic Eelgrass Points. This layer does not represent current conditions. Rather, it depicts historic eelgrass bed locations that were observed and defined either cartographically or narratively over the course of many years and from various sources. The dates of each source's data collection are noted in the attribute table. Feature locations are inexact. Because of the variety of source maps and methods used for their automation, this information should be considered to have limited spatial accuracy and is appropriate for general uses only. The data was taken from maps of various scales and projections that were drawn between 1905 and 1996. These maps were reduced to approximately 1:24,000 scale and adjusted for best fit; eelgrass areas were redrafted onto USGS Topographic Quadrangle maps for digitizing. In order to create a single polygon coverage, areas were considered to represent a maximum extent of eelgrass beds. This layer was published in 1997 and is not updated.

Historical Data on the Buildings of Washington DC, collected over 15 years by Brian Kraft, with support from JMT Inc., for the DC Historic Preservation Office. Most of the data comes from the building permits issued by the city, especially from 1877 to 1949. Sources are named for all buildings and other sources include real estate maps, tax assessments, newspaper reports, and the DC Office of Tax and Revenue, mostly for buildings after 1949. Work on this data is ongoing but we feel that this will be a valuable and enjoyable research tool as it is.