Release notes for Urban June 2024—ArcGIS Urban

The following updates have been made to ArcGIS Urban.

General

The following new features and general improvements are available in Urban:

Use editing constraints for length and angles when creating new polygon geometries, such as buildings, parcels, and study areas.
Plans and projects that are out of date can now be copied by non-owners.
When you create a new urban model, you can now set the custom elevation layer for all urban models.
The import dialog box includes the following improvements:
- In the sublayer step, layers are now filtered and visualized by geometry type.
- In the validation step, the header is shown in red when all values of a field are invalid, indicating that the wrong field has been matched.

The Parcel information side panel now displays additional information about existing and future land use when clicking a parcel in the overview.

The following new features and improvements are available:

In both the data manager and plan configuration, you can reorder the list of space use types and choose the order in which they are displayed in the legend and in other places in the plan editor.
In the data manager only, the function to copy an urban model has been improved:
- The ownership of plans and projects is preserved when you copy the urban model with an administrator role.
- The city name is preserved when you copy an urban model.

The following new features and improvements were added to the plan editing experience:

The Edit spaces tool has been improved:
- You can now add a ground space use type to the parcel.
- If the ground is overlapped by building spaces or surfaces, those parts are not counting towards the legend and dashboard.
- A warning is now shown for cases where overlaps cannot be resolved, specifically when surfaces or building spaces overlap.
- When you export a scenario to a web scene, the ground is included as well.
In plan scenarios, you can now add a custom elevation layer to visualize scenario specific changes in the terrain.
In the Parcel suitability tool, external layer criteria now support sublayers.

The following functionality is removed from the app with this release:

The support for plans in the urban database has been deprecated and is removed with this release.
The Develop field was removed from parcels in the plan scenario web scene.

The following enhancements and bug fixes are introduced with this release:

The project status icons now show the description in a pop-up.
The feedback category icons now show the description in a pop-up.
The markdown instructions to style descriptions now include a link to the documentation.
Bug fix—The zoning legend now filters out entries with no area.
Bug fix—In the import validation, field values are shown as they are in the original data for more complex data types such as booleans and objects.
Bug fix—The undo buttons are now disabled when the grid tool is open in the plan editor.
Bug fix—The Edge orientation tool is now being closed when you use the undo actions.
Bug fix—Surfaces and parcels are now always shown on top of context layers.
Bug fix—Global urban models in WGS84 and Chinese Geodetic Coordinate System 2000 are better handled regarding World elevation and 3D basemap layers. See Understanding local and global urban models to learn more.
Bug fix—The pointer on the project editor dashboard items now shows the default pointer instead of a dragging pointer.
Bug fix—Creating a web scene from a land use plan that included potential values did not work in some cases. This is now fixed.

The following are known limitations of this release:

The Select basemap dialog box only displays basemaps if you configured a basemap gallery in your organization. See the Configure map topic in the ArcGIS Online documentation to learn more about configuring the basemap gallery.
The data manager and plan configuration currently support a maximum of 1,000 features per table. Adding more than 1,000 features can lead to validation errors when uploading related data—for example, uploading future buildings to an urban model with more than 1,000 projects.
The number of vertices of the study area geometry can impact the performance when loading the plan and when editing parcels. Consider simplifying the study area geometry before importing it. See Simplify Polygon to learn how you can do this with ArcGIS Pro.
The number of parcels per scenario can impact the performance when coloring the parcels according to the calculated suitability score. Consider creating a scenario web scene that includes the suitability scores and configure it as scenario context to reduce the loading time for visualizing suitability scores in the plan editor. See Work with scenario web scenes to learn how to export suitability scores and Configure scenario context to learn how to add a scenario context.