Latest Contributions by DominikAllemann

With the new UX, shipped with the February 2022 release, any user who has access to a project can see the details (such as street furniture, trees, surface areas, etc) when opening it.  The project detail card with the description etc that used to be displayed when clicking on a project pin in the overview is now also incorporated in the new project viewing experience (for public users) and in the improved project editing experience (for licensed users) respectively.  ... View more

Hi @lbedard , Thanks for answering my follow-up questions. Unfortunately, due to technical limitations, buildings are placed at a height of 0 when applying a building type to a parcel that is outside of the custom elevation layer's extent. We will investigate ways to improve the user experience in such cases in a future version of Urban and will keep you posted.  In the meantime, I'd recommend removing the custom elevation layer when applying a building type on a parcel that is outside of the custom elevation layer's extent.  Sorry for any caused inconvenience and thanks for your understanding.  ... View more

Hi @lbedard , Thanks for your question and for sharing your experience with the community.  Some follow-up questions to better understand the issue that you are experiencing: Do you currently have a custom elevation layer configured on your Urban Model? Did you have a custom elevation layer configured on your Urban Model when the building in scenario 1 was generated? When you create a new scenario 2 based on Scenario 1, go to Zoning mode and then click "Reapply all building types": will the building(s) be positioned like in "Scenario 1" or rather like in the "New Scenario"? Right now, Urban behaves as follows when working with custom elevation layers: Applying a building type within the extent of a custom elevation layer: the parcel's vertex with the minimal height determines the z-value at which the building is positioned. The z-value is taken from the custom elevation layer.  Applying a building type outside of the extent of a custom elevation layer: the building is placed at a height of 0.  Drawing a custom space within the extent of a custom elevation layer: the z-value at the position where you start drawing determines the height at which the building space is positioned. The z-value is taken from the custom elevation layer. Drawing a custom space outside of the extent of a custom elevation layer: the z-value at the position where you start drawing determines the height at which the building space is positioned. The z-value is taken from the default World Elevation service.  We will investigate if and how the user experience can be improved when working with building types outside the extent of a custom elevation layer.  Thanks. Dominik     ... View more

Hi,  Thanks a lot for letting us know :). ... View more

Hi @BertrandCzerwinski , Thanks for the additional details. Judging based on the screenshots you shared, what you are experiencing indeed seems unexpected. However, we can't reproduce what you are experiencing with our internal test data. Would it be possible to share the two web scenes with the ArcGIS Online user "urban_zrh_pe"? This would be helpful to sort out whether the issue is triggered by the web scene data or by anything else. Thanks.   ... View more

Hi @MaximeDemers , Thanks a lot for your questions. Re: Visibility of project buildings when switching between scenarios The buildings that are not toggled off when switching scenarios: did you draw these buildings using the "Buildings" drawing tool in the project editor? Or are your project scenario buildings loaded from a web scene that is configured as scenario design visualization? To ensure that the project scenario buildings don't clash with the existing buildings in your Urban Model: did you draw a demolition area per scenario in the project editor? Demolition areas are represented by an orange polygon in the 3D map view. Re: Project scenario buildings stay visible when quitting the project The scenario buildings that stay visible when quitting the project: are these loaded from a web scene that is configured as scenario design visualization or did you draw these in the project editor? Buildings drawn in the project editor are expected to be visible when quitting the project if they belong to the topmost scenario in the list of your project's scenarios.  Thanks.  ... View more

Hi @sonia_ml, Thanks for the additional insights. To me, it looks like there are actually two issues: 1) The layer that is being used to import the building footprints from. 2) Matching the building footprints to the projects.  I'm confident that we will get this sorted out soon.   Regarding issue 1 For future buildings I am importing a Multipatch  footprint scene. What exactly do you mean by a "Multipatch footprint scene"? Are you trying to import the footprints from the associated feature layer of a 3D Object Scene layer? Does your future buildings layer only contain the building footprints that you'd like to import to your Urban Model or does it also contain other features?   Regarding issue 2: The screen with the validation errors is displayed if there are footprints in the future buildings layer that cannot be matched to a project.   A potential reason is that the values in the "Project" field of the future buildings layer don't match the projects' "Join ID". Please ensure that the values stored in what you configure as the "Project" field when importing the future building footprints are matching the "Join ID" values of your projects.   In case of further questions, please let us know. Thanks. ... View more

Hi @sonia_ml  I'm sorry to hear that you are experiencing issues with adding future buildings to projects.  To further narrow down the issue, it would be beneficial to know a bit more about what exactly you are experiencing, e.g: Are you getting an error when trying to import future buildings from a polygon feature layer? If so, what kind of error do you get? Does the import dialog run through but the buildings don't show up in the overview? Can you provide reproduction steps for the issue you are experiencing? When importing future buildings to projects through the data manager, please ensure the following: The future building footprints are imported from a hosted feature layer. The future building footprints in the hosted feature layer have a z-value - so that the 2D footprint geometries are correctly placed on the terrain.  The features in the future building footprints layer should have at least the following two attributes: A foreign key that points to the JoinID of the project the footprint belongs to. An attribute storing the height of the building. This value is used to extrude the 2D footprint. Thanks. ... View more