Latest Contributions by MikkelHylden

Is it possible to edit the rotation angle of a marker symbol using Pro Python?  I have been able to get to the basic symbol rotation, but the value I need to change is in the rotation drop down of the symbol details in Pro, and I can't find a way to get to that in Python.   Code snippet getting to the symbol on each layer's symbology object: if sym.renderer.type == 'SimpleRenderer' :    print (' angle: {0}'.format(sym.renderer.symbol.angle)) if sym.renderer.type == 'UniqueValueRenderer':    for grp in sym.renderer.groups:       for itm in grp.items:            print (' angle: {0}'.format(itm.symbol.angle)) Thanks in advance.   ... View more

We have offline geodatabase files created, and they appear differently in the windows and iOS versions of our app.  In windows, all layers appear normally, but in iOS (in some cases) not all point features draw.  In other cases, the point features draw fine.  These are two configurations of the same app, so the code is identical.  Both configurations contain large geodatabase files (~1GB to ~2.5GB), but the size of the file does not seem to matter.  The one we're having problems with is 2.4GB and one that loads correctly is 2.5GB.  One thing I have noticed however is that the one with problems has 74 feature classes and tables, while the others that work correctly have 37, 22, and 49 (split into three separate files, all of which display properly even if made visible at the same time).  In windows, the exact same geodatabase files display correctly.  I would also note that it is not ALL points that don't display in iOS - I have found a couple that do display, although I don't see any rhyme or reason in that they are in the middle of the drawing order, etc..  Is there a limit to the number of tables/features that will display correctly in the iOS version of the runtime that is different from what happens with the windows runtime?   ... View more

We have build a mobile app (I am working in the windows version currently) that uses SQLite geodatabase files for rendering at closer zoom scales, and VTPK files farther out.  These are generated via ArcGIS Pro using python scripts, and have been working well.  We recently updated the servers from Pro V1.4.1 to Pro 2.0, and are using the Runtime version 100.1.  After doing so, the geodatabase files no longer render all the point features in a runtime app.  The geodatabase has data in the tables, as viewed through SQLite, and features can be found using the search tool in our app (and the search zooms to the correct location), so it is not a case of the data being somehow truncated. The geodatabase files generated are rather large (2.4 to 3.3 GB), but I have not seen anything indicating that there is a size limit on SQLite files.  It does not seem to matter if I generate the mobile packages via script or directly from ArcGIS Pro.  I also created a smaller Pro project with only a few layers - that one displays all features as expected.  Other, smaller geodatabase files show some point features but not all.   Has anyone had a similar situation, and if so how can it be remedied?  ... View more