-- DEMO Version v0.5--***Updated to include Errors Identified in the Split line feature class tool***Introducing the Address Management Solution - an ArcGIS Pro Desktop Application Template designed to revolutionize your address data management process!With this ArcGIS Pro Project template, you can efficiently create and manage address points and road centerlines, ensuring data accuracy and completeness. Powered by custom attribute rules, data creation becomes a breeze, automatically populating mandatory fields for seamless data integration.Key Features:Address Points: Easily create new address points with attribute rules that automate the generation of related attributes for comprehensive data.Road Centerlines: Benefit from attribute rules that streamline data editing, simplifying the process of splitting and recalculating address ranges for accurate data maintenance.NG911 Ready: Align your data with the NENA GIS Data Model and National standards, ensuring compatibility and efficient integration with Next Generation 9-1-1 services.User-Friendly: The template comes with targeted training modules, guiding users through introductory, advanced, and master levels to master ArcGIS Pro's powerful address management capabilities.Statewide Dataset: Leverage our comprehensive state-wide datasets, custom domains, and dynamic labels, tailored to cater to Arizona's geographic requirements.Empower your team with the tools and knowledge needed to succeed in creating a more resilient, efficient, and reliable address management system. Download the Desktop Application Template and review the Training Materials to get started!

Abstract Landslides are damaging and deadly, and they occur in every U.S. state. However, our current ability to understand landslide hazards at the national scale is limited, in part because spatial data on landslide occurrence across the U.S. varies greatly in quality, accessibility, and extent. Landslide inventories are typically collected and maintained by different agencies and institutions, usually within specific jurisdictional boundaries, and often with varied objectives and information attributes or even in disparate formats. The purpose of this data release is to provide an openly accessible, centralized map of existing information about landslide occurrence across the entire U.S. This data release is an update of previous versions 1 (Jones and others, 2019) and 2 (Belair and others, 2022). Changes relative to version 2 are summarized in us_ls_v3_changes.txt. It provides an integrated database of the landslides from these inventories (refer to US_Landslide_v3_gpkg) with a selection of uniform attributes, including links to the original digital inventory files (whenever available) (“Inv_URL”). The data release includes digital inventories created by both USGS and non-USGS authors. The original inventory is denoted by an abbreviation in the “Inventory” attribute. The full citation for each abbreviation can be found in us_ls_v3_references.csv. The date of the landslide event is included as a minimum and maximum (“Date_Min” and “Date_Max”) to accommodate events that happen within a range of dates. The date value is inherently difficult to interpret or discern due to the nature of landsliding, where some landslides move for long periods of time or move intermittently, and some areas can exhibit multiple landslide events. To preserve the constituent inventories as much as possible, we include all entries even if they are not considered landslides, such as “gullies” or “avalanche chutes.” We include a landslide type attribute when that information is available (“LS_Type”). The landslide classification system used in the original inventories is not always known or stated in the metadata, but many mapping entities use the schema from Cruden and Varnes (1996) or the updated schema from Hungr and others (2014). Given the wide range of landslide information sources in this data compilation, we provide an attribute to assess the relative confidence in the characterization of the location and extent of each landslide (entry) (“Confidence”). The confidence level reflects the resolution and quality of input data, as well as the method used for identification and mapping. This confidence does not reflect a formal accuracy assessment of field attributes. Relative to the previous data releases (version 1 and 2), this update (v3) includes more inventories, updated confidence rules, a new landslide type attribute, a new unique identifier (“USGS_ID”), new machine-readable date fields, and an ancillary database containing all fields from the original inventories (refer to US_Landslide_v3_ancillary). Please contact gs-haz_landslides_inventory@usgs.gov for more information on how to contribute additional inventories to this community effort. When possible, please cite the constituent inventories as well as this data release. This data release includes: (1) a landslide point file and polygon file in multiple forms (US_Landslide_v3_gpkg, US_Landslide_v3_shp, US_Landslide_v3_csv), (2) an ancillary database with original fields (US_Landslide_v3_ancillary), (3) a spreadsheet that summarizes the confidence rules, their justification, and any extra analyses (us_ls_v3_analyses.csv), (4) a summary file of the changes made between version 2 and version 3 (us_ls_v3_changes.txt), (5) a file containing the references of the constituent inventories (us_ls_v3_references.csv), (6) and a readme (README.txt). Disclaimer: Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Data fields Field Names Definitions USGS_ID Unique USGS identifier for each landslide entry. Date_Min Minimum possible date of landslide occurrence. If date is known to the day, Date_Min will have a value while Date_Max is empty. Time zone is assumed to be local, except for Inventories ‘USGS Earthquake-Triggered Ground Failure’ and ‘USGS Seismogenic Mass Movements’ which are in UTC. Date_Max Maximum possible date of landslide occurrence. If date is known to the day, Date_Max will be empty while Date_Min has a value. Time zone is assumed to be local, except for Inventories ‘USGS Earthquake-Triggered Ground Failure’ and ‘USGS Seismogenic Mass Movements’ which are in UTC. Fatalities Number of fatalities caused by landslide event. Confidence Confidence in landslide (entry) extent, nature, and location. LS_Type Landslide (entry) type. Classification schema of original inventories is often not specified. Inventory Name of original source inventory. Inv_URL URL or link to original source inventory. Info_Source Information source or sub-layer from original source inventory. Notes Unformatted notes field, includes additional information. Lat_N Latitude of point or polygon centroid in WGS 1984 Lon_W Longitude of point or polygon centroid in WGS 1984 Confidence attributes Confidence Definitions 1 Possible landslide (feature) in the area 2 Probable landslide (feature) in the area 3 Likely landslide (feature) at or near this location 5 Moderate confidence in extent or nature of landslide (feature) at this location 8 High confidence in extent or nature of landslide (feature) References Belair, G.M., Jones, E.S., Slaughter, S.L., and Mirus, B.B., 2022, Landslide Inventories across the United States version 2: U.S. Geological Survey data release, https://doi.org/10.5066/P9FZUX6N. Cruden, D.M. and Varnes, D.J., 1996, Landslide Types and Processes, in Turner, K.A. and Schuster R. L., eds., Landslides Investigation and Mitigation: Transportation Research Board, U.S. National Research Council Special Report 247, U.S. National Academy of Sciences, Chapter 3, p. 36-75. ESRI, 2023, ArcGIS Pro (Version 3.1.3), Redlands, CA: Environmental Systems Research Institute, Retrieved from https://www.esri.com/en-us/arcgis/products/arcgis-pro/resources. Hungr, O., Leroueil, S., and Picarelli, L., 2014, The Varnes classification of landslide types, an update, Landslides, 11(2), p. 167-194, https://doi.org/10.1007/s10346-013-0436-y. Jones, E.S., Mirus, B.B, Schmitt, R.G., Baum, R.L., Burns, W.J., Crawford, M., Godt, J.W., Kirschbaum, D.B., Lancaster, J.T., Lindsey, K.O., McCoy, K.E., Slaughter, S., and Stanley, T.A., 2019, Landslide Inventories across the United States: U.S. Geological Survey data release, https://doi.org/10.5066/P9E2A37P. Python Software Foundation, 2023, Python Language Reference, version 3.9, Retrieved from http://www.python.org. QGIS.org, 2022, QGIS Geographic Information System (Version 3.28.4-Firenze), QGIS Association, Retrieved from http://www.qgis.org.

Buildings are the foundation of any 3D city; they create a realistic visual context for understanding the built environment. This rule can help you quickly create 3D buildings using your existing 2D building footprint polygons. Create buildings for your whole city or specific areas of interest. Use the buildings for context surrounding higher-detail buildings or proposed future developments. Already have existing 3D buildings? Check out the Textured Buildings from Mass by Building Type rule.What you getA Rule Package file named Building_FromFootprint_Textured_ByBuildingType.rpk Rule works with a polygon layerGet startedIn ArcGIS Pro Use this rule to create Procedural Symbols, which are 3D symbols drawn on 2D features Create 3D objects (Multipatch layer) for sharing on the webShare on the web via a Scene LayerIn CityEngineCityEngine File Navigator HelpParametersBuilding Type: Eave_Height: Height from the ground to the eave, units controlled by the Units parameterFloor_Height: Height of each floor, units controlled by the Units parameterRoof_Form: Style of the building roof (Gable, Hip, Flat, Green)Roof_Height: Height from the eave to the top of the roof, units controlled by the Units parameterType: Use activity within the building, this helps in assigning appropriate building texturesDisplay:Color_Override: Setting this to True will allow you to define a specific color using the Override_Color parameter, and will disable photo-texturing.Override_Color: Allows you to specify a building color using the color palette. Note: you must change the Color_Override parameter from False to True for this parameter to take effect.Transparency: Sets the amount of transparency of the feature Units:Units: Controls the measurement units in the rule: Meters | FeetImportant Note: You can hook up the rule parameters to attributes in your data by clicking on the database icon to the right of each rule parameter. The database icon will change to blue when the rule parameter is mapped to an attribute field. The rule will automatically connect when field names match rule parameter names. Use layer files to preserve rule configurations unique to your data.For those who want to know moreThis rule is part of a the 3D Rule Library available in the Living Atlas. Discover more 3D rules to help you perform your work.Learn more about ArcGIS Pro in the Getting to Know ArcGIS Pro lesson