We have been collecting all the questions that we got asked a lot about ArcGIS Urban. We hope that with this collection of frequently asked questions you will find all the answers that you are looking for. And if not, please ask us anything else you are curious about here! We are looking forward to hearing from you.
Frequently Asked Questions
- View a digital representation of your city in which all urban developments are visualized in one place for collaboration among stakeholder groups.
- Create and compare scenarios for Zoning and Land Use Plans (mid- to long term) as well as Projects (short- to midterm).
- Visualize zoning rules in 3D—Convert legal text into a visual representation that can be used for detailed scenario planning down to the parcel level.
- Generate plausible buildings and analyze the impact of Plans with automatically generated capacity indicators data and by comparing different design scenarios.
- Gather feedback from the public on Plans and Projects
Urban is built on top of ArcGIS Online. It uses Hosted Layers to display and manage data that is published in an ArcGIS Online Organization. It utilizes the ArcGIS Online’s concept of groups and user to control access to these Hosted Layers.
No, Urban is currently only available for ArcGIS Online.
The Urban Databases can be opened in ArcGIS Pro when connecting to the ArcGIS Online Organization where they have been created. The hosted Feature Layers can be displayed and edited through ArcGIS Pro, however there is no dedicated Integration available.
There is a dedicated integration available between CityEngine and Urban. CityEngine can automatically connect to an Urban Model and load Plans and Projects from Urban. Changes and edits made in CityEngine can by synchronized back to Urban and new scenarios can be created.
Urban and CityEngine have a lot of things in common (e.g. they use the same procedural engine under the hood to create models) but they also differ. In CityEngine, you can write you custom CGA rules, where Urban provides a built-in rule that cannot be modified. What you can change in Urban are the parameters that drive the rule, such as the maximum height or the allowed floor area ratio. Urban is a web-based application whereas CityEngine is a Desktop tool that is installed locally. In general, Urban is a focused platform – not just a tool or web app – that supports urban planning workflows and facilitate communication between stakeholders. CityEngine supports the creation of detailed urban designs and produces sophisticated models of built-out scenarios. Read more about Urban and CityEngine.
GeoPlanner supports creating 2D scenarios at regional scale across many industries. Urban is designed to support urban planning workflows such as re-zoning by displaying and calculating capacity indicators based on procedurally built 3D scenarios. In general, GeoPlanner supports more generic workflows whereas Urban has a strong focus on urban planning because it uses the procedural engine of CityEngine to produce plausible buildings and zoning envelopes.
There are two options to bring AutoCAD data into Urban:
1. CAD Integration through CityEngine: The Urban CityEngine integration allows to import data of different 3D formats (dxf, dae, fbx, glTF, kml/kmz, obj) into CityEngine and from there the models can be attached to an Urban scenario directly.
2. CAD Integration through ArcGIS Pro: Urban can display SceneLayers and BuildingSceneLayers that have been published through ArcGIS Pro. Those layers can be coming both from CAD or Revit BIM-Data. After publishing the layers from ArcGIS Pro, they can be linked as external sources in a scenario of a Project/Plan in Urban.
Yes, BIM models can be added to Urban, but they have to be converted to a BuildingSceneLayer before. To get the best results, it is recommended to publish a generalized version of the BIM model with a minimum number of nodes. Multiple BIM models can be attached to different scenarios, but for performance reasons they will not be loaded/displayed at the same time.
In Land Use or Zoning Plans you can create plausible 3D buildings and zoning envelopes based on the underlying zoning regulations. Urban supports many zoning parameters, such as maximum coverage, FAR, height or number of floors as well as allowed space uses, skyplanes, tiers and setbacks and more. These parameters affect, how the generated plausible buildings look like. You can additionally control the shape of those buildings by designing different building types.
In comparison to Plans, where buildings are automatically generated, the Plan editor allows you to design your own buildings. You can enrich the 3D scene by adding greenery, street furniture or vehicles from a large library.
It is possible to share your design scenarios with the public and get feedback to Plans and Projects by enabling public engagement. This allows you to collaborate with the public and further refine your scenario designs.
Urban can also be used as a platform where urban planners collaborate by sharing their Urban Model, Plans and Projects on ArcGIS Online, for example with a specific group of people or within a certain organization.
No, Urban is a web-based application and needs a stable internet connection.
Urban runs best with Chrome, however also Firefox, Safari and Edge are supported. Only Internet Explorer cannot be used with Urban because it does not support the technology behind the procedural modelling of the 3D buildings. Read more about system requirements.
An Urban license is tied to a Creator user type in your ArcGIS Online Organization. The cost of a license depends on your local distributor. Please get in touch with our team to get more information about licenses and prices.
A larger city does not necessarily consume more credits. The credit consumption depends on the number and size of Plans, Projects and Indicators that are stored in your Urban. The more features that are stored in the database, the more credits are consumed for storing them. Please review the credit consumption of ArcGIS Online for more information. Additional credits are consumed in Urban when using the address search and for elevation queries (when not using a custom elevation layer).
Yes, Urban is part of the Education Institution Agreement. With the Educational license, universities and schools can make licenses available for students for classes. Get in touch to receive more information about this.
Yes, greenfield development is supported in Urban. New parcels can be added and generated on-the-fly with the 3D drawing tools. You can draw new parcels in Urban, however they will not be based on a cadastre management system. Urban provides a grid tool to efficiently subdivide areas into rectangular parcels. You may also consider opening the Plan in CityEngine for automatically generating parcels based off the drawn street network.
With the parcel drawing tools in Urban, you can also outline rough lot lines. If you have a Feature Layer with proposed roads in it, you can use this to guide your scenario design. You also have the option to design a road network for the Plan area in CityEngine, and then bring it into Urban to guide scenario planning.
Yes, the underlying concepts of Urban can also be used to solve other problems, such as:
- Architecture, Engineering, and Construction (AEC): How can we keep track of all our proposed, planned, and completed projects?
- Real Estate: How can we manage and display all of the on-going projects in our organization?
- Education: How can we explain urban density and trends around settlement development to students in an interactive way?
And many more… let us know if you have an idea for an application in your field/industry.
Yes, external data can be added to Urban. We recommend using the built-in data manager tool in Urban to load data from Feature Layers or spread sheets (e.g. csv, excel). External layers such as already published base maps and existing buildings can also be attached there. In the Plan and Project configuration, external layers can be attached per scenario, and indicators support adding external WebScenes that can be styled using the smart mapping capabilities of the SceneViewer.
Yes, the built-in Living Atlas Indicators include the Trust for Public Land (TPL) indicator called ParkServe®. The ParkServe® platform provides information about park systems and the associated percentage of city, town and community residents within a 10-minute walk of a park. This indicator is currently only available for the US.
The ArcGIS Living Atlas of the World is a collection of authoritative, global geographic data curated and hosted by Esri. You can use Living Atlas content alone or in combination with your own content to create maps, scenes, and apps and perform analysis in Map Viewer or Insights for ArcGIS. In Urban, Living Atlas Indicators are provided for specific regions in the world (current only US is supported) that showcase important metrics for urban development, such as population change or housing vacancy.
Yes, the built-in Capacity Indicators can be configured to fit your city’s standards. For the US you can choose a default template with pre-configured values when creating your Urban Model. The default values are an average over the whole US and can be used as a benchmark if you do not have knowledge about metrics such as average living area per capita. These assumptions are attached to the space use types in Urban and can be configured in the data manager.
Yes, within Urban you can export Plan design scenarios to a Web Scene (3D) or a Web Map (2D) and Capacity Indicators to an excel sheet for further processing. Additionally, Urban lets you generate high-resolution screenshots within the application.
Urban creates so-called plausible buildings as well as zoning envelopes. The application calculates capacity indicators based on the gross floor area per space use of the plausible buildings. Capacity Indicators analyze population, number of households, jobs, parking spots, generated trips and many other metrics. The indicators are calculated based on assumptions such as average floor space consumption per capita or type of job. These assumptions can be configured by the user. The capacity indicators are displayed in Urban in a dashboard that can be filtered by the whole study area or a user-driven selection.
No, Urban’s data model is separate from the Local Government Information Model. It is focused on the representation of Plans and Projects and is specialized to support the procedural generation of zoning envelopes and plausible building forms. You can use parcel and zoning information from the Local Government Data Model to populate the Urban data model.
Yes. You can access the Plans and Projects in Urban from ArcGIS Pro via the appropriate Feature Layers. These can be used in various analytical processes. The results of such spatial analysis can be published back to Urban as Custom Indicators, our as Context Layers for specific Plans and Projects.
There are various analytical models (some proprietary and some are open source) that are used for planning purposes. Urban can provide inputs to these models, expanding the in-app dashboards. Many times, these models are also localized to the city in which they are used therefore Urban can provide input that may be more detailed.
If you have the model, you can use the results that urban generates, you can show the impact on various other indicators that you are interested in.
Yes, Urban is designed to work for small and large cities and to a certain extent also on a county and regional level.
There is no limit on how much content Urban can display in the Overview because the data (e.g. buildings) is streamed and loaded on different levels of details depending on your viewport and zoom level. When creating new Plans in Urban, we recommend to keeping the area to cover below 50’000 parcels (or buildings) per Plan for performance reasons and the best possible user experience. However, a city can contain any number of Plans and Plans larger than 50’000 parcels will still work, but speed will be decreased.
Additionally, the Scene Layer technology on ArcGIS Online allows you to scale up to any size as features are loaded (streamed) based on your viewport and zoom level. The level of detail of the 3D buildings are continuously adjusted based on those parameters. Our example city Boston (BPDA) covers an area of 89.63 square miles in Urban. Read more about best practices for large scenes.
No, you don’t need to have existing 3D content. Of course, we recommend building out a 3D basemap for a better experience and so that more accurate planning decisions can be made. A curated 3D basemap creation workflow can be found here.
It is possible to load in 3D trees (as a SceneLayer) which will also be masked by new developments as it is the case with existing buildings. A 3D tree layer can be produced if you have access to lidar, or if you have a tree points layer. Floodplain and park layers (and similar), if hosted in a WebScene, can be brought into Urban as an indicator or contextual layer. Zones that relate to parks or open space can be added and color schemes can be defined accordingly. Additionally, trees and vegetation layers (2D or 3D) can be added as design context for new Plans.
No, but it is recommended you go through a launch kit for the initial setup of Urban. You can set up Urban on your own using the data manager within Urban.
Do you have any further questions? Then please get in touch & ask questions here in our GeoNet space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.