The following updates have been made to ArcGIS Urban.
General
The following new features and general improvements are available in Urban:
- When creating an urban model, you can select a coordinate system in which the urban model will be created. The user experience is also improved when you create an urban model:
- Choose a basemap to define the coordinate system of your urban model.
- You can create the urban model in any supported coordinate system. See Supported coordinate systems to learn more.
- When you choose a projected coordinate system, a local urban model is created. Compared to a global urban model, a few limitations exist. See Understanding local and global urban models to learn more.
- The Select basemap dialog box shows all basemaps from the basemap gallery of your organization, including the ArcGIS Online basemaps when added to the basemap gallery.
- The extent of the urban model is used to filter out basemaps on the Select basemap dialog box.
- When creating an urban model, parcels and zones are reprojected in the coordinate system of the urban model.
- In the portal item picker, it shows all the items of My organization upon opening the dialog box-instead of My content as before.
Overview
The following new features and general improvements are available in the overview:
- A more descriptive error message appears when loading a layer fails:
- The layer might not be in the same coordinate system as the urban model. See Understanding local and global urban models to learn more.
- The elevation layer might have the wrong tiling scheme to be displayed together with the basemap in a local urban model.
Data manager and plan configuration
The following new features and improvements are available in the data manager:
The following improvements are available in both the data manager and the plan configuration:
- The coordinate system of the urban model is shown in the settings page.
- The experience to import tiers for zoning types and overlay boundaries is improved when importing from spreadsheets or feature layers. On the dialog box, you can import the setbacks of the first tier from individual fields instead from a JSON string.
- The metrics graph shows colored nodes and warning messages in ToolTips when there are no parameters or constant values configured.
Plan editing
The following new features and improvements were added to the plan editing experience:
- When building spaces are not counting toward GFA/FAR, you can identify them more easily, as they are visualized transparently in the space editing mode.
- Improved undo and redo actions while drawing spaces, also when using keyboard shortcuts.
- You can save plans as duplicates to urban models with a different coordinate system. In this case, the geometries are reprojected to the new coordinate system.
- In the suitability tool and the plan scenario web scene, parcels with no value are shown transparently to avoid visual interference.
- In local urban models, the plan scenario web scene is created as a local scene.
- The GeodeticShapeArea field in the plan scenario web scene is replaced with an Area field storing the correct area value (planar area for projected coordinate systems, geodetic shape area for geographic coordinate systems). See Supported coordinate systems to learn more about various coordinate systems.
Project editing
The following new features and improvements were added to the project editing experience:
- Metric values are exported in the project scenario web scene so you can use them in your calculations or to display them in the web scene pop-up.
- Improved undo and redo actions while drawing in the project editor, also when using keyboard shortcuts.
- You can save projects as duplicates to urban models with a different coordinate system. In this case, the geometries are reprojected to the new coordinate system.
- In local urban models, the project scenario web scene is created as a local scene.
- The GeodeticShapeArea field in the project scenario web scene is replaced with an Area field storing the correct area value (planar area for projected coordinate systems, geodetic shape area for geographic coordinate systems). See Supported coordinate systems to learn more about various coordinate systems.
Deprecated and removed functionality
The following functionality is deprecated and will be removed with a future release:
- The support for plans stored in the urban database will be removed in the future. There is a new information banner when opening a plan stored in the urban database. Save the plan as a duplicate to move it out of the urban database. See Copy an existing plan to learn more.
The following functionality is removed from the app with this release:
- The Select basemap dialog box in the data manager only shows items from the basemap gallery of your organization. The ability to choose any web map as the basemap has been deprecated. Previously selected web maps can still be used as basemaps. See the Configure map topic of the ArcGIS Online documentation to learn more about configuring the basemap gallery.
- The ability to import multiple tiers in the data manager and plan settings is deprecated and replaced with an improved user experience to import the setbacks for the first tier. You can still configure multiple tiers on the zoning type dialog box and when editing overlay boundaries in the plan editor. You can also import multiple tiers using the ArcGIS Urban API.
Enhancements and bug fixes
The following enhancements and bug fixes are introduced with this release:
- A number of accessibility improvements are available everywhere in Urban, including the following:
- Search results are announced by screen readers when the results list is filtered or searched.
- Error messages such as invalid inputs are discoverable and available for assistive technology devices.
- You can navigate in button toolbars with the keyboard.
- Accordions and list elements can be navigated with the keyboard.
- Labels are properly attached to the elements they are referencing, allowing you to click labels of, for example, input elements to select them for input.
- You can zoom in the scene for all browsers.
- The Custom ID field is also displayed and can be configured on the building type dialog box in the plan editor.
- Buttons are shown with squared instead of rounded corners.
- In some places, button borders have been removed to decrease visual clutter.
- The width of edges for rendering buildings, spaces, and so on, has been harmonized across the application.
- Bug fix—The scrolling behavior of the scenario switcher when using the mouse has been reverted.
- Bug fix—For plan scenario web scenes, only the envelopes of the selected visualization styles are exported.
- Bug fix—When switching between scenarios in the plan editor, the envelopes of the previous scenario could still be visible for an instance. This is fixed.
- Bug fix—When updating parcel attributes in large plans, the refresh of the features would sometimes fail and still show the old value. This is fixed.
- Bug fix—The discussion pins stayed visible in the overview when returning from the project editor. This is fixed.
- Bug fix—A problem when importing features from an enterprise-hosted feature layer is fixed.
- Bug fix—On the web scene creation dialog box in Hebrew, a string was not translated correctly.
- Bug fix—Undo and redo was sometimes not working correctly when using keyboard shortcuts. This is fixed.
- Bug fix—Cache control was turned on when editing for nonowners was disabled. This could lead to issues when editing and loading in data. This is fixed.
- Bug fix—After removing the close buttons, in read-only mode, dialog boxes could not be closed anymore, as the cancel button was disabled. This is fixed.
Known limitations
The following are known limitations of this release:
- Coordinate systems with imperial units are not supported yet when creating an urban model or when copying an existing urban model to another coordinate system. Support will be added in the future.
- When choosing a file geodatabase to import features, the coordinate system cannot always be retrieved from the item. The Coordinate system mismatch dialog box might not appear when choosing a file geodatabase with a different coordinate system than the urban model.