Latest Contributions by PaulChristensen3

While using the traditional Polygon/Line parcel system, once I transitioned to the next tax year, I would copy my working .gdb and rename it. For instance "Landrecords2020.gdb" to "Landrecords2021.gdb". The new .gdb would become my working .gdb and the previous year was 'archived'. This method gave me a historical feature class that I could then add to my map, and by adding all of my previous years layers, view how an area has changed throughout the years. I know the AGP Parcel Fabric uses retired parcels to represent historic parcels. However, what is the best workflow to keep a running history throughout the years? Should I continue my method of 'archiving' my past .gdb or maybe just export a snapshot of my working .gdb?  I want to be able to see how an area has changed throughout the years and I just don't know if the fabric's method of retiring parcels will show this as effectively as my current method especially for non-record driven edits such as QA/QC where a retired parcel is not created. Do yall just use one .gdb throughout the years and use the retired parcels for this? ... View more

Several of my Hosted Feature Layers have been increasing in size. Has anyone else had similar experiences? How do you manage this? I am the sole publisher of this data that is hosted in AGOL, and no other members of my organization edit or modify these files. For example: A file's normal size is 15mb. I have modified this file, however, the total feature count, field count, attributes etc, remain similar, no major changes besides a slight increase or decrease in total records. My method of modifying the data is to add it to a map in ArcGIS Pro, delete all features, then append features. The file size remains the same for hours to days, then increases dramatically to 70mb or even more. I had one go from 30mb to 280mb AND back down to 30mb with no intervention or input, right in front of mine and Esri's eyes as we screen shared!  I realize that enabling sync or editing can affect the file sizes, however the initial jump in size is erratic and not always directly related to toggling settings. As in, it does not always jump immediately when I toggle editing or sync, it might jump a few hours later or the next day.  Yesterday, a file I have not modified in at least several days, doubled in size with no discernible triggers. I toggled editing on and off and the file size went back down to the expected size. Now, this morning, it is back up to double what it should be with no changes overnight.  I opened a ticket and conversed with Esri for weeks back in February/March, and they were not able to give concrete answers as to what exactly affects size and how to predict changes. This was their response.  While I could find some documentation on size increases on sync-enabled layers, I haven't been able to find any related to editing. However, after speaking with colleagues, it is expected for the size of a layer to increase after enabling sync and editing, as we have both seen. It's difficult to speak to the amount a layer will increase in size, since this is dependent on the schema of the data, how many replicas may be created, the geometry of the features, etc. However, we saw similar magnitude increases (10x) in our datasets. Just something to be aware of when enabling those features. I think this is unacceptable. In order to be able to budget for credit consumption, file settings and their affect on size needs to be transparent and predictable, not erratic and spontaneous. I have relatively small datasets, what about organizations that have large data stores? Their credit budgets must be incredibly hard to pin down when their file sizes are all over the place. ... View more

I am using Jupyter Notebooks to automate some AGOL tasks. I have also tested this code in ArcGIS Pro and in Spyder with no luck. All using the same cloned environment. Cloned using ArcGIS Pro. This specific section of my workflow involves creating offline areas to be used in Explorer for ArcGIS. The layers and maps do not have Editing enabled, but they do have Sync enabled. There are two layers that are Layer Views, each with a definition query applied.  Manually, using the AGOL: Manage Areas interface, I am able to easily draw and create an offline area that is downloadable in Explorer. However, I cannot seem to get this to work reliably with the Python API. My notebook: from arcgis . gis import GIS from arcgis . mapping import WebMap from arcgis import env env . verbose = True ‍‍‍‍ #sign into gis gis = GIS ( "My_GIS" , "My_Username" ) print ( "Successfully logged in as: " + gis . properties . user . username ) wm_item = gis . content . get ( 'My_AGOL_Item' ) wm_item wm = WebMap ( wm_item ) extentdict = { 'xmin' : - x , 'ymin' : y , 'xmax' : - x , 'ymax' : y , 'spatialReference' : { 'wkid' : 3857 } } offline_item_properties = { 'title' : 'Re21_App1_North' , 'tags' : [ 'Reassessment' , 'Appraiser' ] } A1_North = wm . offline_areas . create ( area = extentdict , item_properties = offline_item_properties , folder = 'Appraiser Maps' , min_scale = 160000 , max_scale = 1500 ) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ This is almost exactly following the API Reference except that I use an extent instead of a bookmark. This exact code worked last week. But now it is throwing an error. The error is referencing Line 1755  'layer0_obj' in the _types.py script. Note: The offline area is created without any packages and is stuck on "Packaging" indefinitely. Error: Submitted . Executing . . . Start Time : Friday , May 29 , 2020 3 : 42 : 58 PM Running script CreateMapArea . . . Completed script CreateMapArea . . . Succeeded at Friday , May 29 , 2020 3 : 42 : 59 PM ( Elapsed Time : 1.22 seconds ) CreateMapArea GP Job : x_____xTwPeRg5tQfrLowkK0gxr - Q . . x_____xj0aedb71fa5af431ab38f6ae4be4bfd2a finished successfully . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - UnboundLocalError Traceback ( most recent call last ) < ipython - input -6 - f1b0325e3428 > in < module > 5 item_properties = offline_item_properties , 6 min_scale = 160000 , - - - - > 7 max_scale = 1250 ) ~ \AppData\Local\ESRI\conda\envs\arcgispro - py3 - clone\lib\site - packages\arcgis\mapping\_types . py in create ( self , area , item_properties , folder , min_scale , max_scale , layers_to_ignore , refresh_schedule , refresh_rates , enable_updates , ignore_layers , tile_services , future ) 1334 enable_updates = enable_updates , 1335 ignore_layers = ignore_layers , - > 1336 tile_services = tile_services ) 1337 1338 #---------------------------------------------------------------------- ~ \AppData\Local\ESRI\conda\envs\arcgispro - py3 - clone\lib\site - packages\arcgis\mapping\_types . py in _create ( self , area , item_properties , folder , min_scale , max_scale , layers_to_ignore , refresh_schedule , refresh_rates , enable_updates , ignore_layers , tile_services , future ) 1753 # LOD that is closest to min scale. Do similar for max_scale. 1754 - > 1755 sorted_lods = sorted ( layer0_obj . properties . tileInfo . lods , key = lambda x : x [ 'scale' ] ) 1756 keys = [ l [ 'scale' ] for l in sorted_lods ] 1757 UnboundLocalError : local variable 'layer0_obj' referenced before assignment‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ If I remove the min_scale and max_scale, the tool runs. But the map area does not have a valid scale and the area is not downloadable in Explorer. JSON: (with min/max_scale removed and notebook successfully ran) "mapAreas" : { "mapAreaTileScale" : { "minScale" : null , "maxScale" : null } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍  If I go into the AGOL: Manage Areas interface and 'edit' the Level of Detail to where I want it, everything seems to work and the map is downloadable in Explorer. JSON: (manually editing the Level of Detail in AGOL: Manage Areas interface) "mapAreas" : { "mapAreaTileScale" : { "minScale" : 160000 , "maxScale" : 1250 } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ I understand the basic error. The variable is not assigned. The issue is that the error is referencing a script that is not generally modified. If it were my code, it wouldn't be so bad to figure out and rewrite. I believe I am following the API Reference near verbatim, so I am thinking that the issue is potentially with my install, map configs, or somewhere else other than directly in my code. Is it an issue with my coding or maybe with my notebooks install? Should I try and run a clean Clone and conda? Issue with my map configurations? What are my options here? Where to begin? ... View more