This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

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.

MRGP NewsIf you already have an ArcGIS named user, join the MRGP Group. Doing so allows you complete the permit requirements under your organization's umbrella. As a group member you get access to the all the MRGP items without having to log-in and log-out. If you don’t have an ArcGIS member account please contact Chad McGann (MRGP Program Lead) at 802-636-7239 or your Regional Planning Commission’s Transportation Planner. April 9, 2025. Conditional logic in webform for the newly published Open Drainage Survey was not calculating properly leading to some records with "Undetermined" status and priority. Records have been rescored and survey was republished with corrective logic. Field App version not impacted.March 11, 2025. The Road Erosion Inventory Survey123 questions for Open Drainage Roads are being streamlined to make assessments faster. Coming April 1st, the survey will be changed to only ask if there is erosion depending on if the corresponding practice type is failing. This aims at using erosion as an indicator to measure the success of each of the four Open Drainage road elements to handle stormwater: crown, berm, drainage, turnout.March 29, 2023. For MRGP permitting, Lyndonville Village (GEOID 5041950) has merged with Lyndonville Town (GEOID 5000541725). 121 segments and 14 outlets have been updated to reflect the administrative change. December 8, 2023. The Open Drainage Road Inventory survey has been updated for the 2024 field season. We added and modified a few notes for clarification and corrected an issue with users submitting incomplete surveys. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update, and execute it, but we've experienced select-one questions with duplicate entries.November 29, 2023. The Closed Drainage Road Inventory survey has been updated for the 2024 field season. There's a new outlet status option called "Not accessible" and conditional follow-up question. This has been added to support MS4 requirements. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update and execute it for you but we've experienced select-one questions with duplicate entries. Reporter for MRGPThe Reporter for MRGP doesn't require you to download any apps to complete an inventory; all you need is an internet connection and web browser. The Reporter includes culverts and bridges from VTCULVERTS, town highways from Vtrans, current status for MRGP segments and outlets and second cycle progress. The Reporter is a great way to submit work completed to meet the MRGP standards. MRGP Fieldworker SolutionStep 1: Download the free mobile appsFor fieldworkers to collect and submit data to VT DEC, two free apps are required: ArcGIS Field Maps and Survey123. ArcGIS Field Maps is used first to locate the segment or outlet for inventory, and Survey123, for completing the Road Erosion Inventory.• You can download ArcGIS Fields Maps and Survey123 from the Google Play Store.• You can download ArcGIS Field Maps and Survey123 from Apple Store.Step 2: Sign into the mobile appYou will need appropriate credentials to access fieldworker solution, Please contact your Regional Planning Commission’s Transportation Planner or Chad McGann (MRGP Program Lead) at 802-636-7239.Open Field Maps, select ‘ArcGIS Online’ as shown below, and enter the user name and password. The credential is saved unless you sign out. Step 3: Open the MRGP Mobile MapIf you’re working in an area that has a reliable data connection (e.g. LTE or 4G), open the map below by selecting it.Step 4: Select a road segment or outlet for inventoryUsing your location, highlighted in red below, select the segment or outlet you need to inventory, and select 'Update Road Segment Status' from the pop-up to launch Survey123.

Step 5: Complete the Road Erosion Inventory and submit inventory to DECSelecting 'Update Road Segment Status' opens Survey123, downloads the relevant survey and pre-populates the REI with important information for reporting to DEC. You will have to enter the same username and password to access the REI forms. The credential is saved unless you sign out of Survey123.Complete the survey using the appropriate supplement below and submit the assessment directly to VT DEC.Paved Roads with Catch Basin SupplementPaved and Gravel Roads with Drainage Ditches Supplement

Step 6: Repeat!Go back to the ArcGIS Field Maps and select the next segment for inventory and repeat steps 1-5.

If you have question related to inventory protocol reach out to Chad McGann, MRGP Program Lead, at chad.mcgann@vermont.gov, 802-636-7396.If you have questions about implementing the mobile data collection piece please contact Ryan Knox, ADS-ANR IT, at ryan.knox@vermont.gov, (802) 793-0297

How do I update a survey when a new one is available?While the Survey123 app will notify you and update it for you, we've experienced some select-one questions having duplicate choices. It's a best practice to delete the old survey and download the new one. See this document for step-by-step instructions.I already have an ArcGIS member account with my organization, can I use it to complete MRGP inventories?Yes! The MRGP solution is shared within an ArcGIS Group that allows outside organizations. Click "join this group" and send an request to the ANR GIS team. This will allow you complete MRGP requirements for the REI and stay logged into your organization. Win-win situation for us both!AGOL Group: https://www.arcgis.com/home/group.html?id=027e1696b97a48c4bc50cbb931de992d#overviewThe location where I'm doing inventory does not have data coverage (LTE or 4G). What can I do?ArcGIS Field Maps allows you take map areas offline when you think there will be spotty or no data coverage. I made a video to demonstrate the steps for taking map areas offline - https://youtu.be/ScpQnenDp7wSurvey123 operates offline by default but you need to download the survey. My recommendation is to test the fieldworker solution (Steps 1-5) before you go into the field but don't submit the test survey.How do remove an offline area and create a new one? Check out this how-to document for instructions. Delete and Download Offline AreaWhere can I download the Road Erosion Scoring shown on the the Atlas? You can download the scoring for both outlets and road segments through the VT Open Geodata Portal.https://geodata.vermont.gov/search?q=mrgpHow do I use my own map for launching the official MRGP REI survey form? You can use the following custom url for launching Survey123, open the REI and prepopulate answers in the form. More information is here. TIP: add what's below directly in the HTML view of the popup not the link as described in the post I provided.

Segments (lines):Update Road Segment StatusOutlets (points):Update Outlet Status

How do I save my name and organization information used in subsequent surveys? Watch this short video or execute the steps below:

Open Survey123 and open a blank REI form (Collect button) Note: it's important to open a blank form so you don't save the same segment id for all your surveys Fill-in your 'Name' and 'Organization' and clear the 'Date of Assessment field' (x button). Using the favorites menu in the top-right corner you can use the current state of your survey to 'Set as favorite answers.' Close survey and 'Save this survey in Drafts.' Use Collector to launch survey from selected feature (segment or outlet). Using the favorites menu again, 'Paste answers from favorite.

What if the map doesn't have the outlet or road segment I need to inventory for the MRGP? Go Directly to Survey123 and complete the appropriate Road Erosion Inventory and submit the data to DEC. The survey includes a Geopoint (location) that we can use to determine where you completed the inventory.

Where can I view the Road Erosion Inventories completed with Survey123? Use the web map below to view second cycle inventories completed with Survey123. The first cycle inventories can be downloaded below. First cycle inventories are those collected 2018-2022.Web map - Completed Road Erosion Inventories for MRGPWhere can I download the 2020-2022 data collected with Survey123?Road Segments (lines) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_segments.zipOutlets (points) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_outlets.zipWhere can I download the 2019 data collected with Survey123?

Road Segments (lines) -

Granite Falls stormwater utility information. This version of the data has undergone a large review in November of 2025, removing many duplicate features to provide a more accurate representation of the city's storm system.

Lineworks copied directly from NHDHighRes data thats present on SGID10 database. UDWR Water Names and Water Id's have been assigned to the features. Oringial NHD features copied from the NHDHighRes feature class around 2014. Please note that some of the line work could of been captured prior to 2014 and be from an earlier version of the NHDHighRes data set.Permanent_Identifier and ReachCode were copied directly from the NHDHighRes data set. Updated on 10/01/2019 to remove duplicates linework.

Polygon features copied directly from NHDHighRes data thats present on SGID10 database. UDWR Water Names and Water Id's have been assigned to the features. Oringial NHD features copied from the NHDHighRes feature class around 2014. Please note that some of the line work could of been captured prior to 2014 and be from an earlier version of the NHDHighRes data set.Permanent_Identifier and ReachCode were copied directly from the NHDHighRes data set. Certain features (mainly Community Fisheries) were not present in the data set at the time of creation and they had to hand digitized and therefore lack a Permanent_Identifier and ReachCode. For the these features the DWR water id (DWR_WaterID) was used and was added into the Permanent_Identifier field. If a DWR waterbody consists of a multipart feature (aka Deer Valley Lakes) the DWR water id plus a numerical value was added to the tail end of the water id (e.g. IV56801,IV56802, IV56802).Updated on 10/01/2019 to remove duplicates, merged together lakes/reservoisr that were split by two states, and assigned Permanent_Identifiers for those features that lacked them (hand digitized; features not present in NHD).

The overall goal of the Estuary Marine Protected Area (EMPA) Monitoring Program is to establish a monitoring framework, including data collection, analysis, synthesis, and reporting to determine the health of estuaries in California and the efficacy of MPA designation in estuaries. As part of the initial phases of the program, we developed standard protocols to assess key estuarine features across different estuaries, coupled with standard data templates and guidance on analysis, synthesis, and reporting, focused on four guiding principles flexibility, comparability, interpretability, and practicality. We developed 15 SOPs and piloted the framework at 15 estuaries in 2021. For more details on the EMPA program and framework, see https://empa.sccwrp.org This dataset includes the fish abundance data from SOP 9. Fish abundance was collected by beach seining 3 to 5 times at each sampling station within an estuary. Each fish was identified to species and total abundance was reported by species. For more details, see SOP 9 on https://empa.sccwrp.org.In 2023, the EMPA data types were modified to include more comprehensive data collection. Due to these changes and updates, we modified the historic 2021 data to match the current and ongoing EMPA data collection. Updates to the 2021 EMPA data included: addition of columns to match current EMPA data schemas, rigorous QA/QC, and modification of station codes. Rigorous QA/QC was conducted in order to remove duplicate entries, correct data discrepancies (e.g., unaligned data-time stamps), and update scientific nomenclature. In 2023, north coast stations were adjusted, and therefore no longer aligned with 2021 stations. We re-coded the 2021 stations using the following nomenclature - {oldstationno}{newstationno]. For example, Big River station 2 in 2021 now matches Big River station 1 in 2023. The new nomenclature used in the 2021 data is 21 (old station 2 + new station 1).

Last update: October 16, 2025 OverviewThis point data was generated and filtered from OpenStreetMap and is intended to represent places of interest in the state of Utah. These may include businesses, restaurants, places of worship, airports, parks, schools, event centers, apartment complexes, hotels, car dealerships…almost anything that you can find in OpenStreetMap (OSM). There are over 23,000 features in the original dataset (March 2022) and users can directly contribute to it through openstreetmap.org. This data is updated approximately once every month and will likely continue to grow over time with user activity. Data SourcesThe original bulk set of OSM data for the state of Utah is downloaded from Geofabrik: https://download.geofabrik.de/north-america/us/utah-latest-free.shp.zipAdditional attributes for the Utah features are gathered via the Overpass API using the following query: https://overpass-turbo.eu/s/1geRData Creation ProcessThe Open Source Places layer is created by a Python script that pulls statewide OSM data from a nightly archive provided by Geofabrik (https://www.geofabrik.de/data/download.html). The archive data contains nearly 20 shapefiles, some that are relevant to this dataset and some that aren't. The Open Source Places layer is built by filtering the polygon and point data in those shapefiles down to a single point feature class with specific categories and attributes that UGRC determines would be of widest interest. The polygon features (buildings, areas, complexes, etc.) are converted to points using an internal centroid. Spatial filtering is done as the data from multiple shapefiles is combined into a single layer to minimize the occurrence of duplicate features. (For example, a restaurant can be represented in OSM as both a point of interest and as a building polygon. The spatial filtering helps reduce the chances that both of these features are present in the final dataset.) Additional de-duplication is performed by using the 'block_id' field as a spatial index, to ensure that no two features of the same name exist within a census block. Then, additional fields are created and assigned from UGRC's SGID data (county, city, zip, nearby address, etc.) via point-in-polygon and near analyses. A numeric check is done on the 'name' field to remove features where the name is less than 3 characters long or more than 50% numeric characters. This eliminates several features derived from the buildings layer where the 'name' is simply an apartment complex building number (ex: 3A) or house number (ex: 1612). Finally, additional attributes (osm_addr, opening_hours, phone, website, cuisine, etc.) are pulled from the Overpass API (https://wiki.openstreetmap.org/wiki/Overpass_API) and joined to the filtered data using the 'osm_id' field as the join key. Field Descriptionsaddr_dist - the distance (m) to the nearest UGRC address point within 25 mosm_id - the feature ID in the OSM databasecategory - the feature's data class based on the 4-digit code and tags in the OSM databasename - the name of the feature in the OSM databasecounty - the county the feature is located in (assigned from UGRC's county boundaries)city - the city the feature is located in (assigned from UGRC's municipal boundaries)zip - the zip code of the feature (assigned from UGRC's approximation of zip code boundaries)block_id - the census block the feature is located in (assigned from UGRC's census block boundaries)ugrc_addr - the nearest address (within 25 m) from the UGRC address point databasedisclaimer - a note from UGRC about the ugrc_near_addr fieldlon - the approximate longitude of the feature, calculated in WGS84 EPSG:4326lat - the approximate latitude of the feature, calculated in WGS84 EPSG:4326amenity - the amenity available at the feature (if applicable), often similar to the categorycuisine - the type of food available (if applicable), multiple types are separated by semicolons (;)tourism - the type of tourist location, if applicable (zoo, viewpoint, hotel, attraction, etc.)shop - the type of shop, if applicablewebsite - the feature's website in the OSM database, if availablephone - the feature's phone number(s) in the OSM database, if availableopen_hours - the feature's operating hours in the OSM database, if availableosm_addr - the feature's address in the OSM database, if availableMore information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/society/open-source-places/

The Fireline QAQC GIS product is a tool designed to improve the quality of fireline data from the National Interagency Fire Center's National Incident Feature Service (NIFS). Its primary function is to clean, filter, and correctly attribute firelines to specific fire incidents for use in environmental modeling.The Fireline QAQC GIS product, developed by Alexander Arkowitz (Colorado State University/USFS Contractor) and Matt Thompson (US Forest Service Rocky Mountain Research Station), is a tool designed to produce quality-assured fireline data for environmental modeling. It uses the "Event Line" and "Historical Fire Perimeters" data from the National Interagency Fire Center's National Incident Feature Service to accurately attribute firelines to specific fire incidents, such as those within the 2022 WFIGS Perimeters dataset.Key ProcessesThe tool's workflow involves several key steps:Data Retrieval: It downloads "Event Line" and "Historical Fire Perimeters" data for a user-specified year.Filtering: The data is filtered to retain only completed firelines (e.g., dozer lines, hand lines) and remove features marked for deletion.Attribute Cleanup: It standardizes data by trimming extra spaces from text fields and populating missing IRWIN IDs (a unique fire identifier) where possible.Spatial Analysis: A buffer is created around a fire's perimeter to identify nearby firelines that may be associated with it. The tool performs intersections to match firelines to fires based on IRWIN IDs, incident names, and location.Change Tracking: When the tool updates a fireline's incident name or IRWIN ID, it stores the original values in "OldName" and "OldIRWIN" fields for review.Duplicate Removal: Finally, it identifies and dissolves identical fireline features to ensure data integrity.