The following updates have been made to ArcGIS Urban.
General
The following new features and general improvements are available in Urban:
- You can create a web scene with a selection of plans and projects of your urban model to share it with stakeholders or the public. You can use the web scene in other Esri products such as StoryMaps, Instant Apps, or Experience Builder. See Create city web scene to learn more.
- Use the refined Boston example city with two new design plans to explore Urban.
- A new structure of the data manager, plan, and project settings improves the user experience.
Plan editing
The following new features and improvements were added to the plan editing experience:
- You can undo and redo actions in the plan editor. This feature is available in all modes: zoning or land-use, development, dashboard, and discussion. You can, for example, undo changes made to buildings, parcels, dashboard charts, or comments.
- The visualization of the zoning map is improved:
- Overlays are now shown together with zoning on the map and in the legend.
- You can change the appearance of zoning, land use, and overlays by choosing from a variety of fill and outline styles.
- A new pop-up on zones and overlays improves the experience to explore and modify zoning regulations.
- You can change the order of zoning, land use, and overlays in the zoning legend.
- You can set descriptions on overlays to be shown in the new overlay pop-up.
- You can now set a label on each overlay boundary individually. This replaces the option to configure labels on overlay types.
- A new and improved tool to add zoning, land-use, and overlay boundaries is introduced. It replaces the former Edit geometry and Paint tools.
- A new option allows you to automatically merge adjacent or overlapping zoning and land-use boundaries of the same type when adding a boundary or changing the type of a boundary.
- The scenario to a web scene export is improved:
- You can modify the default title of the created web scene.
- Viewpoints are added as slides that can be used for presentations.
- Display names (field aliases) are added to all fields. The display name is used to describe the content in a more user-friendly way instead of showing the technical field name.
- A field description is added to the exported fields where available.
- Layer titles, field display names, and field descriptions are being translated.
- All exported values are converted to the units which are set in the ArcGIS Online user profile. The unit is added to the field display name.
- The suitability tool is further improved:
- During the calculation, the tool shows a progress bar and an option to cancel the calculation.
- The calculation performance when using external layers is improved.
Removed functionality
The following functionality was removed.
General
The following general functionality has been removed from Urban:
- The Hardeeville, Uppsala, and Melbourne example cities have been removed and replaced with the new and updated Boston example city.
Plan editing
The following functionality has been removed from the plan editor:
- The ability to configure the net area factor on individual building floors and surfaces has been removed. You can still configure the net area factor on the space-use type level. The metric calculation will exclusively use the net area factor as configured on the space-use type. See Work with space-use types to learn more about space-use types.
- Highlighting intersecting land-use boundaries when validating zoning against land use in zoning plans has been removed.
- Disabling fields in the overlay types settings and hiding them in the overlay boundary dialog box has been removed. See Work with overlays to learn more about editing overlay types and boundaries.
Note:
The setting of previously disabled fields is now set by default to replace underlying zoning. If your overlay boundaries have parameters defined for such fields, you must remove those values. See Modify an overlay boundary to learn more about editing parameters on overlay boundaries.
Enhancements and bug fixes
The following enhancements and bug fixes are introduced with this release:
- Improved performance of the plan editor. The following actions are faster:
- Loading a scenario.
- Applying or re-applying building types to multiple parcels at the same time.
- Loading zoning envelopes for multiple parcels.
- The OK button is now located to the right of the Cancel button in all dialog boxes to increase usability.
- Drawing zoning and land-use boundaries on top of existing ones will replace the boundaries underneath.
- The space-use type dialog box in the plan editor additionally shows the net floor area per dwelling unit for residential space-use types. The value is automatically calculated based on the gross floor area per dwelling unit and the net area factor.
- The net floor area of future developments is added to the exported scenario web scene.
- The option to embed an urban model, a plan, or a project is visible only if the item is shared with everyone (public).
- You can now select a feature and open up its pop-up even if it is hidden behind buildings or zoning envelopes, for example, selecting parcels in the suitability tool.
- Setback values can now be erased by deleting the value instead of having to type 0.
- Bug fix—Overlay types proposed in the plan were applied after existing overlay types, regardless of the order specified in the plan configuration. This is fixed in this release. Now, overlay types are always applied in the order shown in the plan configuration. See Reorder overlay types to learn more.
- Bug fix—In some cases, the metric chart showed incorrect values for individual metric sources. This is fixed in this release. The total metric value was not affected by this issue.
- Bug fix—The following issues have been fixed when exporting a scenario to web scene:
- The exported web scene contains the custom elevation layer (if one is defined).
- Surfaces are exported as part of the future developments and added as a new layer to the web scene.
- Adding the existing buildings layer to the web scene is now working with proper masking regardless of the type of layer (for example, if the existing imagery buildings are not an integrated mesh layer).
- You can now change the extrusion of future developments in the Scene Viewer.
- ArcGIS Pro now shows the correct extrusion of future buildings.
- It was not possible to export a scenario that included inaccessible external layers—for example, because they were not shared with the user. This is fixed. Urban ignores the inaccessible layers in the export and shows a warning.
- Metric or suitability criteria names made up entirely of non-Latin characters are now exported.
- Bug fix—Types that are in use—for example, by a boundary—cannot be deleted anymore in the data manager.
- Bug fix—Zoning envelopes now update correctly on local changes; for example, modifying overrides, adding zones, or editing overlays.
- Bug fix—An issue where wrong warning labels are showing after switching plan scenarios is fixed for this release.
- Bug fix—The suitability tool now supports external layers with a layer ID different than 0.
- Bug fix—The parcel explorer in the overview supports long parcel IDs.
- Bug fix—Error notifications are now always displayed in the foreground instead of being hidden behind dialog boxes.
- Bug fix—External layers (for example existing buildings) defined in a local coordinate system are ignored by Urban instead of crashing the app. Urban currently supports only external layers in a global coordinate systems (for example, Web Mercator).
Known limitations
The following are known limitations for this release:
- Zoning envelopes cannot be shown when editing spaces in the plan editor. The zoning envelope of the selected parcel is automatically hidden when entering the space editing tool.
- The exported plan scenario web maps may not display correctly in the Map Viewer Classic. Use the new Map Viewer instead.
- The number of dwelling units displayed in the development side panel is an estimation that is subject to projection imprecisions. When you apply a dwelling unit building type to a parcel, this number may differ slightly from what is displayed on the map.
- The OpenStreetMap 3D scene layers are not supported yet.