D1_LEHD_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
D1_LEHD_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
D2_EFA_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
D2_EFA_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
E1_ODF_flowline_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
E1_ODF_flowline_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
E2_wetlands_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
E2_wetlands_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
E3_heatisland_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
E3_heatisland_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
E4_soil_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
E4_soil_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L1_landuse_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L1_landuse_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L2_ccap_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L2_ccap_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L3_public_ownership_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L3_public_ownership_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L4_transit_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L4_transit_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L5_speedlimit_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L5_speedlimit_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
L6_pednetwork_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
L6_pednetwork_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
H1_photoviewer_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
H1_photoviewer_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
H2_redlining_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
H2_redlining_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
S1_poi_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
S1_poi_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
S2_county_ID_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
S2_county_ID_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
S3_ai_assistant_usefulness (type: esriFieldTypeString, alias: How useful would this be to your work?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true, Coded Values: [Extremely useful: Extremely useful], [Very useful: Very useful], [Moderately useful: Moderately useful], ... 3 more ...)
S3_ai_assistant_feedback (type: esriFieldTypeString, alias: Optional: Other feedback on this?, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)
other_projects (type: esriFieldTypeString, alias: Are there any other GIS data projects or process improvements that you'd like the RLIS team to consider prioritizing? If so, please describe here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
testimonials (type: esriFieldTypeString, alias: The RLIS team always loves to hear about how RLIS supports your work. If you have any examples you'd like to share with us, please describe them here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
other_feedback (type: esriFieldTypeString, alias: Is there anything else you'd like to share?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
D1_LEHD_description (type: esriFieldTypeString, alias: Project description: Add LEHD data from the U.S. Census Bureau to RLIS. This data provides demographic information about workers linked to both employment locations and homes, including information about worker age, earnings, job sector, race and ethnicity, educational attainment, and sex. Project benefits: Because work area statistics are based on work locations, the data is a better representation of people's locations during the daytime than American Community Survey statistics which summarize responses based on home addresses. Daytime population information is essential for emergency planning, and also supports transportation and economic analysis. Residence-based LEHD data is similar to existing American Community Survey data in RLIS, but provides the ability to focus analyses on the working population. While there is some uncertainty about the continued availability of federal data, we will continue regular updates to the RLIS copy of this data for as long as the data is being maintained, and we believe there will be value to preserving the most recent copy of the data within RLIS should it become unavailable in the future., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
D2_EFA_description (type: esriFieldTypeString, alias: Project description: In the current Equity Focus Area data, an EFA is a census tract is identified both based on an above average percentage of the population meeting certain criteria, and the density of that segment of the population being twice the regional average, in order to prioritize areas where programs and improvements are likelier to serve a large number of people. This project would create an alternative version of the data for internal use that does not consider population density when identifying EFAs.Project benefits: A density-indifferent version of the EFAs would provide more visibility of rural areas with higher percentages of historically underserved communities., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
E1_ODF_flowline_description (type: esriFieldTypeString, alias: Project description: Replace RLIS stream data with Oregon Department of Forestry's lidar-derived stream routes, clipped to the Metro region. The data has been enriched with information collected during field surveys and includes size and channel type attributes. Project benefits: This change will provide a newer, more accurate, and more frequently maintained stream dataset for the region for cartography and general reference. The state's stream data includes additional attributes such as stream size, seasonality, and presence of fish. Like the older RLIS layer, the new data would not be suitable for localized analysis as it has not been ground-truthed. The dataset is updated by the State roughly every quarter, but includes some known issues (such as incorrect flow direction assigned to some segments, or geometry errors for streams that run through flatter landscapes) that are being corrected as capacity allows. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
E2_wetlands_description (type: esriFieldTypeString, alias: Project description: Replace RLIS wetlands data with the Oregon Wetlands Database, which includes three layers: the Local Wetlands Inventory, the National Wetlands Inventory, and the More Oregon Wetlands dataset. Each provides a different level of detail and includes different features. The Local Wetland Inventory has been approved by the Department of State Lands and is limited to wetlands that are at least one half acre in size; the National Wetland Inventory includes many more features, especially smaller wetland areas; and the More Oregon Wetlands data includes wetlands not captured by either inventory, such as some industrial water bodies. Project benefits: This change will provide a more up-to-date source of wetland data with a greater level of detail than the existing RLIS wetland data. This data will support environmental analysis and better understanding of habitat locations and connectivity, while also leading to better consistency between analysis completed at the state and local levels., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
E3_heatisland_description (type: esriFieldTypeString, alias: Project description: Add urban heat island data to RLIS and update it annually. The data would show temperatures classified into warm to cool values, highlighting areas in the region where warmer temperatures are experienced. Urban heat is identified from national surface temperature data collected by satellite.Project benefits: This data could be compared against urban canopy or other trees data to highlight the relationship between the built and natural environment. For example, transportation agencies are interested in the locations of heat islands when planning road improvement projects that may impact street trees. It can be compared with demographic data to understand differences in how heat waves impact local communities., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
E4_soil_description (type: esriFieldTypeString, alias: Project description: Republish a subset of soil survey data from the Soil Survey Geographic Database (SSURGO). Soil data has been collected from field surveys and soil sample analyses over the last century. SSURGO includes many attributes, but this project would focus on soil hydrologic classes (rate of water infiltration) and soil types. Depending on interest, other attributes may also be included in the data. Project benefits: Similar data was once provided in RLIS but was deprecated due to a lack of maintained data. This project will restore access to soil data within RLIS, which will support environmental, land use, and risk analysis, for example identifying high value habitat or farming land, or determining flooding and erosion risk. While there is some uncertainty about the continued availability of federal data, we will continue regular updates to the RLIS copy of this data for as long as the data is being maintained, and we believe there will be value to preserving the most recent copy of the data within RLIS should it become unavailable in the future., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L1_landuse_description (type: esriFieldTypeString, alias: Project description: Add more detailed land use information to the RLIS taxlot data where buildings are present. This will increase the specificity of land use types, for example providing "Retail" or "Office" categories where the current data is categorized as "Commercial", and providing housing types from the RLIS Housing data. Project benefits: This information will allow for more specific land use analysis and will support Metro's Urban Growth Report and land use modeling. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L2_ccap_description (type: esriFieldTypeString, alias: Project description: Add 1-meter land cover data from NOAA's Coastal Change Analysis Program (C-CAP), clipped to the Metro region. NOAA has produced three land cover data layers, impervious surface, canopy, and water. NOAA anticipates updating this data every 4-6 years. Project benefits: This data can be used to analyze change in land cover over time. Canopy data is especially of interest to urban heat analysis, and changes in impervious surface data can inform development analysis. Clipping and republishing the data within RLIS will provide easier access and improved performance of the data. While there is some uncertainty about the continued availability of federal data, we will continue regular updates to the RLIS copy of this data for as long as the data is being maintained, and we believe there will be value to preserving the most recent copy of the data within RLIS should it become unavailable in the future., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L3_public_ownership_description (type: esriFieldTypeString, alias: Project description: Include an attribute in the RLIS taxlot data to indicate if taxlots are publicly or privately owned. Clackamas, Multnomah, and Washington Counties track this information to different extents, so there will be limitations to this field. For example, publicly owned land that is leased for taxable purposes may be miscategorized as privately owned land. Project benefits: Some services, such as Metro's cleanup of illegal dumping, operate differently on publicly vs privately owned land. This project will provide easier access to that information without relying on users to be able to identify public agencies by name in the taxlot ownership data. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L4_transit_description (type: esriFieldTypeString, alias: Project description: This project would incorporate routes and stops from smaller transit providers (such as SMART, Ride Connection, county shuttle services, and intercity routes) into RLIS, to expand on the existing TriMet bus route and stop data. Project benefits: Adding this data to RLIS will support transit analysis and visualization. This data is already being collected to support Metro's Regional Transportation Plan and incorporating the data into RLIS would make the data more easily accessible to others. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L5_speedlimit_description (type: esriFieldTypeString, alias: Project description: Incorporate posted speed limits into the internal RLIS Streets data. Where speed limits change in the middle of a street segment, the speed limit that applies to the majority of the segment will be applied.Project benefits: Speed limit data attached to the RLIS street network would support street safety analysis and travel modeling, which are important to Metro's Safe Streets for All and Transportation System Management and Operations (TSMO) work. This project was selected as a priority project during the last project cycle, but limitations in the data sources resulted in a significant amount of manual editing and made quarterly updates infeasible. We are resurveying to determine interest in an annually-updated, internal version of this data., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
L6_pednetwork_description (type: esriFieldTypeString, alias: Project description: Develop and maintain a regional, routable pedestrian network for internal use by combining RLIS Trails and Streets data. This data would be updated annually.Project benefits: This Esri network dataset would allow GIS analysts with access to Esri software to generate walksheds around points of interest (e.g., schools). This project was selected as a priority project during the last project cycle, but it was not completed. We are resurveying to confirm that this data is still needed. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
H1_photoviewer_description (type: esriFieldTypeString, alias: Project description: This project would create a new application that displays Metro's regional aerial imagery collection, which includes aerial imagery collected nearly every summer since 1996, as well as some winter leaf-off imagery. Project benefits: This application would be a one-stop location for viewing historical aerial imagery for the Portland metropolitan region that wouldn't require people to build their own maps., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
H2_redlining_description (type: esriFieldTypeString, alias: Project description: Republish historical redlining data from Mapping Inequality, a project from University of Richmond's Digital Scholarship Lab that has digitized historical maps showing neighborhoods that the federal government believed were risky areas for banks and lenders to offer mortgages. These determinations were usually made based on the racial demographics of the neighborhoods. For the Portland area, data comes from a 1934 map and includes original descriptions of income, occupation and race of population, as well as neighborhood infrastructure.Project benefit: This data can provide context for racial and geographic disparities in home ownership and property values, as well as show historical neighborhood demographics. Adding the data to RLIS will make it easier to find and overlay with other data for our region., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
S1_poi_description (type: esriFieldTypeString, alias: Project description: Incorporate new data sources into our Points of Interest locator. The Points of Interest locator allows people to navigate our web maps by searching for place names (such as schools, parks, churches, and other landmarks), but it relies on place information from a data source that is no longer maintained and is missing newer places. Project benefits: This project will provide more up-to-date name and location information for points of interest (for example, recently renamed schools) and include a larger collection of places, allowing easier navigation within our map applications., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
S2_county_ID_description (type: esriFieldTypeString, alias: Project description: This project would add a "County" column to all point data layers within RLIS to indicate the county that the point falls within. This project would also add a unique ID column to all point data in RLIS, with the ID values persisting between updates to the data. Project benefits: The County column would allow users to quickly filter the data to a smaller area of interest to improve performance of the data, and the persistent unique IDs would allow users to more easily select points or join their own data to points without having to rewrite queries. , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
S3_ai_assistant_description (type: esriFieldTypeString, alias: Project description: Test Esri's AI Search Assistant for the RLIS Discovery site. The AI Search Assistant can use RLIS open data layers to provide text, tabular, or map-based answers to questions about the region, and can help people find content in the site more easily.Project benefits: Through this project, we'll identify some limitations of the AI Search Assistant and provide feedback to Esri to improve the product. Testing the Search Assistant is essential in determining whether the benefits of the tool are great enough (and potential issues are sufficiently managed) to justify future public rollout of the Search Assistant for the RLIS Discovery website (dependent on the release of Metro's AI policy and on approval from Metro's Information Technology department)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
Templates:
Name: New Feature
Description:
Drawing Tool: esriFeatureEditToolPoint
Prototype: