Latest Contributions by DanCampbell

‎07-14-2020

Hi Brian, I think that in all the testing I was doing I might have run into the situation you note. At one point I noticed that there were duplicates of some of fields in my plan which might have been caused by data being copied twice. However, I believe my further testing was with a fresh plan and I still had the issue. Thanks for the heads-up, and I'm going to check again just to be certain. Dan

‎07-07-2020

Hi Till, It just so happens I do have another question. I've successfuly generated edge attributes in CityEngine and created a new parcel layer that I have loaded into Urban, matching the Edges field to the EdgeInfos field. My problem is that when I create a new Zoning Plan all the selected parcel edge attributes in Scenario 1 are still set to the default of "side", and not the the new attributes generated in CityEngine. Opening that new Zoning Plan in ArcGIS Online shows the selected parcel EdgeInfos attributes to be: [{"orientation":"front","adjacencies":[]},{"orientation":"side","adjacencies":[]},{"orientation":"rear","adjacencies":[]},{"orientation":"side","adjacencies":[]}]. So, the data in the table looks right with the respective front and back edges being listed, but it is not being reflected in Urban. Am I missing a step to get the mapping to work correctly? Thanks again, Dan

‎07-03-2020

Thank you Till, I was was starting to suspect that the specific round-trip functionality wasn't there, and I'm glad to hear you are working on implementing it. The work-around you suggest will do the job for me, and I almost got there on my own. What confused me was that when I brought the plan into CityEngine the parcel view in the Inspector didn't expose any edge information. I ran the Compute Edge Attributes routine, but I didn't think it was doing anything because there was no view of any changes in the edge orientation. If it gests the job done cumbersome is OK with me. In using the plan method to update eges, must it be done all at once with one big plan, or is it still possible to run a series of smaller plans and assemble the new parcel base in ArcGIS Pro? Thanks again, Dan

‎07-01-2020

Some of my problem has been resolved. I found that if I reduced the vertex count of some of the larger polygons I was finally able to export the parcel shapefile and open it in ArcGIS Pro and ArcGIS Online. So, small victories! Where I remain stumped is getting the parcel edge attributes into Urban. In loading the Parcel layer I see that I am required to match fields. No problem doing so with Population, Jobs and Households. For Edges, however, there doesn't seem to be a single field that I can select that contains the edge data. What is available in the shapfile exported form CityEngine is information spread across numerous fields starting with rnttns which contains, front, rear, and side attributes. When I open up a scenio for which I edited the parcel edges directly in Urban I noticed that there is a field called EdgeInfos that seems to contain the consolidated edge data that Urban needs. I couldn't find any options in CityEngine export function that would enable me to create this field. Thanks for any assistance on this, Dan

‎06-29-2020

I've been able to successfully bring my parcels that I will be using in ArcGIS Urban (approximately 94,700) into CityEngine and calculate pretty good edge attributes. Where I am running into trouble is getting the parcels back into Urban. I first tried directly loading the parcel shapefile directly into CityEngine and calculating the edge attributes. When I tried to export the updated version, it took well over an hour to create the new shapefile, and even when it appeared to have completed no file was actually created. I tried a few more times, and after hours of processing it finally created a file, but I was presented with an error message when I tried to open it in ArcGIS Pro, or to add it to ArcGIS Online. I thought the issue might be a compbination of the number of parcels and the numerous vertices along curved edges so I tried exporting only a smaller selection of parcels. That worked...sometimes. The first set of data opened in ArcGIS Pro and I could see that edge orientation data was present and that there were multiple columns with the mttns_* and strctg_* headings. The second small extract worked as well, but it only included the "Shape" column and no attribute info at all. Trial and error suggested that reducing either the complexity of the parcel polygons seemed to help. I expect I will probably be able to combine all these smaller extracts in ArcGIS Pro but I wonder if the resulting file will still create difficulties when I try to bring it into Urban. Merging two very small extracts took about 45 minutes, so I'm not sure this is a viable approach. I've also tried creating a scenario in Urban that includes all the City Parcels and opening it in CityEngine. Once again, there is no issue creating the edge attributes. The problem is that the Syncronize All Scenarios starts OK, but eventually times out. So, I'm guessing I must be doing something wrong, or I am running up against the maximum number of parcels that can be handled efficiently. Any advice on how to best proceed would be greatly appreciated. Dan Campbell

‎05-15-2020

When I publish a scenario the existing buildings are not included. I viewed the "Exporting Your Scenarios" video and noticed that the existing 3d buildings are included in the published example, and are shown as another layer that can be turned on or off. What do I need to do to include existing buildings in my published scenario? Is the correct workflow adding the existing buildings through the design visualization option in a project? Thanks, Dan

‎04-06-2020

Hi. I am trying to understand how to work with the Suitability Score for parcels. Am I correct that to use this functionality I need to map the Suitability field to any field in my parcel file with a numeric value when I first load the file into Urban? For example, if I have a field called "building_age" in my parcel file that has values from 1 to 10, I would map that field to the Suitability field in Urban. Then, using Urban I would use the slider to identify the parcels most likely to be developed based on the corresponding building age. If my understanding is correct, does this also mean that only a single suitability category can be used unless the full parcel file is re-imported and a different attribute mapped to the Suitability field? Thanks, Dan

Online Status	Offline
Date Last Visited	‎02-12-2021 01:49 PM

My Ideas

Latest Contributions by DanCampbell

Re: Parcel Edge Attributes Using CityEngine

Re: Parcel Edge Attributes Using CityEngine

Re: Parcel Edge Attributes Using CityEngine

Re: Parcel Edge Attributes Using CityEngine

Parcel Edge Attributes Using CityEngine

Publishing a scenario with existing buildings

Configuring the Suitability Attribute