Latest Contributions by ChristianWells

Check out more of what the Map Viewer Beta can do here, connect with others, and provide feedback on the experience: ArcGIS Online Map Viewer Beta ... View more

Robert Kearney‌ after digging in a bit more and discussing with the Product team, the most up-to-date version of Explorer for ArcGIS (Windows) is 20.1.0. I am working with our internal teams to update the Support website to reflect this. Please let me know if you have any additional questions. ... View more

Hi Robert Kearney‌, Thank you for posting your question - I want to help resolve this issue for you. Can you share what build number your Windows 10 machine is? You can find this by typing "System Information" into your Windows start menu. When you open the program you should see the build number like this: ... View more

Here are some resources on learning about the Slope tool: Esri Academy (Maintenance Required): Terrain Analysis Using ArcGIS Pro Learn ArcGIS (Scenario based): Estimate Solar Power Potential Regarding the bug - these are logged by contacting Technical Support. I will send you a direct message to get your information so we can get a case created for you. ... View more

Glad to hear we made some progress! On the insufficient permissions it might be the tables from the LOCATION or PLANNINGCADASTRE schema. Can you verify that you can do a SELECT one each table without the ST call? Can you verify you can do an INSERT on DEMOLITION_NOTIFICATIONS_GIS without the ST call? ... View more

I tried to simplify this down to just the ST functions, but this might help get us in the right direction. Here is how I did an INSERT INTO SELECT with an ST_BUFFER: insert into gis_table (shape) select sde.st_buffer(l.shape, 0.05) from location l;‍‍ If I add in attribute records it changes slightly: insert into gis_table (objectid, gis_table_id,shape) select 1,2,sde.st_buffer(l.shape, 0.005) from location l;‍ In the original script, there are some duplication of the ST calls with the ST_GEOMETRY + ST_ASTEXT function. There are 2 reasons I would avoid the additional call for WKT. ST_BUFFER returns an ST_GEOMETRY object and can be reused in your insert statement without rework The WKT is returned as a Character Large Object (CLOB), which can be unwieldy and quite large to store in memory - this becomes more important as you scale your SQL requests. ... View more

Dina - I'm glad this script is still helpful for someone a couple of years later. In my script I didn't originally consider seeing the Layout view, however, this should be a simple item to address. What we'll need to do is set the mxd.activeView to "PAGE_LAYOUT" so the MXD shifts to the layout tab instead. Can you try this code instead? import arcpy mxd = arcpy.mapping.MapDocument("CURRENT") mxd.activeView = 'PAGE_LAYOUT' for bkmk in arcpy.mapping.ListBookmarks(mxd): ext = bkmk.extent df = arcpy.mapping.ListDataFrames(mxd)[0] df.extent = ext arcpy.mapping.ExportToPDF(mxd, r"C:\Temp\{0}".format(bkmk.name)) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Edit: Here is the documentation I am referencing for the MapDocument Properties in ArcPy Mapping module. MapDocument—Help | ArcGIS Desktop  ... View more

Great question, Jose. I don't have a specific tool to recommend, but I'd like to help narrow it down. What are you hoping to monitor? Is it to find who is locking the database? Or just to be notified when is becomes locked? ... View more

Here is my testing: Create db1 as an Enterprise Geodatabase (same instance) Create db2 as a standalone database (same instance) Create a spatial table in db2 with 100 records using Create Random Points Fields (OID, Shape) Create an empty feature class in db1 with the same schema Fields (OID, Shape) Run the following code: -- Get the number of rows in the looping table DECLARE @RowCount INT SET @RowCount = (SELECT COUNT(*) FROM [db1].[dbo].[ORIGINFC]) -- Declare an iterator DECLARE @iterator INT -- Initialize the iterator SELECT @iterator = MIN(OID) FROM db1.dbo.ORIGINFC -- Loop through the rows of a table WHILE @iterator is NOT NULL BEGIN DECLARE @id as integer -- Get OBJECTID value EXEC sde.next_rowid 'sde', 'destinationfc', @id OUTPUT; -- Insert the data while casting the points geometry INSERT INTO SDE.destinationfc (oid, shape) SELECT @id,Shape FROM db1.dbo.ORIGINFC where OID = @iterator; -- Update the iterator value SELECT @iterator= MIN(OID) FROM db1.dbo.ORIGINFC WHERE @iterator < OID END‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Query the destination table count which should equal 100 I ran this with a 10.7.1 EGDB and SQL Server 2014 (12.0.6108.1) but I don't see duplicate records in the destination feature class.  Could you repeat my steps with a generic feature class and share the results you receive? I know this is a really simplified example but maybe it will point us towards the cause.  ... View more

Thanks for sharing your findings. Let me take a look at 10.7 and get back to you. What version of SQL Server are you using? ... View more

Yes, you can see the updates from each field worker but querying the version name will depend on their sync status and method. We have some great documentation here: Offline maps and traditional versioned data—Documentation | ArcGIS Enterprise  ... View more

This looks to be a bug from one of the beta builds BUG-000121076: Explorer for ArcGIS (Android) beta incorrectly reque..  ... View more

Great to hear Alice, thank you for the follow-up. I had a few thoughts for this solution long-term I wanted to share with you. If you aren't editing versioned Feature Classes with SQL this won't play as crucial a role, but I recommend doing this clean-up effort at some point in your DBMS maintenance. Although the views you created solve the issue, they don't contain the same definition as the versioned view would have. This is low-risk if you are only editing with ArcMap or ArcGIS Pro, but it would ensure quality repositories in the geodatabase Steps Delete the multi-versioned views using the SDE Command Line tools (sdetable -o delete_mv_view) This will remove the metadata reference and the substitute views you created above Create the versioned views using the Enable SQL Access tool This will update the naming convention to have "_evw" but it will ensure the view has the correct definition ... View more