Latest Contributions by TessOldemeyer

Gotcha. Yes, Table_2 currently has 40 empty fields. I would like to only populate FieldA. Is there a way to assign 'None' to all subsequent fields without having a long list of 'Nones'? It looks like I might be able to use (*) to read in all fields from Table_1 if this is needed for line 7 (vs. having to list out all fields). Also, the tbList values are what I was expecting. I just wanted to make sure the list format wasn't part of the 'size of row error'. Thanks for all of your help! ... View more

I think this is exactly what I am looking for.  However, I am getting a "sequence size must match size of the row" error on line 10. I did not include a "myCalc" field though, as I have already added all of the necessary fields to the new table (i.e. Table_2). (Maybe I am wrong in excluding it?)  tbList = [] # empty list for row in arcpy.da.SearchCursor('Table_1', ["FieldA"]):     if row[0] not in tbList:         tbList.append(row[0]) # copy distinct rows to list inCursor = arcpy.da.InsertCursor('Table_2', ["FieldA"]) # list of all fields in new table for row in tbList:      inCursor.insertRow((row,None)) # field values to insert del inCursor‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If I print tbList, this is what I currently get: ... View more

Yes, they are unique values. ... View more

That blog post is AWESOME. I have been using it for many of my field updates lately, and it has been a game changer for speeding up scripts. I was actually hoping to integrate something similar for this particular issue but became stumped when I didn't have a key for both tables. I am also not quite sure if a dictionary is helpful, if the search cursor is only reading values from one field. If you have suggestions as to how I might make this method work for updating one existing field on a new table that does not already have a key (the new field that is being populated here will act as the key for subsequent field calculations), I will gladly take them. I'm a python novice and am looking for recommendations anywhere I can get them. Thank you so much! ... View more

This might be the straightforward way  I was hoping to keep the existing 'Table_2' structure (without having to add and reorder fields), but deleting the new field after a quick join and calculation might be the best way to go.  Thanks! ... View more

That was the ticket! Thank you so much! ... View more

Turns out, I did find some color conflict. It appears in both CityEngine and the web scene.  web scene:  CityEngine: ... View more

Thank you so much. You have been super helpful. By removing the transparency and adding an extrusion to the fill color shapes on the first floor models, I was able to resolve most of the flickering. I am using a 10 meter DEM as a terrain surface in CityEngine,  though I have not been exporting the terrain to our Portal. In web scenes, it appears to load to the 3D basemap correctly. I think the main issue with the flickering for my models is directly related to the uneven terrain. I am not sure of ways to navigate this. For the building in the screen shot below, I have extruded the floors by 1.3 m and am still receiving some z-conflict flickering due to the gentle hills of the terrain (e.g. the left side of the building shown). The colors are solid with no flickering in CityEngine, regardless of elevation offset or extrude height. The issue only seems to appear in the web scene. I did change some of the colors around and it looks like the rendering remains consistent in the web scene. The colors are accurate and the z-conflict still appears to be in the same location. I will keep an eye out for any issues with color that may look buggy, though I haven't noticed any as of yet. I'll keep you posted if I run into anything. Thanks again! ... View more

Here are screenshots of the same floor plan with an offset of 0.01 meters with the street maps and imagery base maps: There still appears to be some sort of face conflict (apparently with the ground surface) for the ground level floors in the web scene, even after a 0.1 m vertical offset. Also, as it would be nice to have these floors snapped to the ground, any options on how I might work around this conflict? Thank you! Tess ... View more

The colors do appear to be consistent in the web scene and in CityEngine. Here are two images of the same floor plan. The top image is in the web scene and the bottom is in CityEngine. I am not quite sure what the light gray building would be or how to adjust their plane. I do see what you're taking about though. However, in addition, it does look like the halls and other corridors should be rendering as the same dark gray as seen in CityEngine prior to export. It also looks as if the hallways and corridors are also attempting to render in the right color in the web scene.   The Model Heirarchy Explorer is awesome!  I have also browsed over the additional links you attached, and they are definitely helpful. I will keep digging.  Thanks! Tess ... View more

Awesome! This works perfectly:  report("name", "MyNewNameToBeDisplayedInPopupWindow") Thank you! ... View more

Thanks again for your help Cheryl. I do get the problem regardless of zoom level, though the flickering appears to change with zoom level. The polygon floor colors do render correctly as solid color surfaces in CE prior to exporting as scene layer packages. Adding the NIL after the attribute reporting did not appear to solve the issue.  Unfortunately, I will not be able to pass along the polygon feature data these models are generated from, but attached is the rule file that is being used. The rule file was originally written in CE 2015.  Thanks again! Tess ... View more