Latest Contributions by RandyKreuziger

‎12-24-2019

Why in the world did they do that? Thanks for the alert on this. No telling how many users have unknowingly corrupted their edits.

‎11-22-2019

Several of our SQL 2012 geodatabases are still at 10.4.1. ArcGIS Pro crashes when attempting to view locks when the NULL column value is encountered! Pro crashing is beyond disappointing for a new product! ESRI wants customers to migrate to Pro but in my experience it crashes just as much as ArcMap.

‎11-13-2019

When you say geodatabase do you mean enterprise like SQL Server or file geodatabase? If SQL Server, you could have a single table with year, site and density with a view that makes it look like you have it above.

‎10-17-2019

Timm, I have the same issue. How did you do it or did you learn?

‎09-11-2019

We have a staging database where feature classes are staged using the same name as the one in the master database. Our existing tools have inputs for the target fc and the source fc then doing a truncate-append. If the user has update rights to both locations this could be disastrous if they get mixed up! Once both are set I always double check to see that I didn't get the target and source backwards.

‎09-11-2019

Shapefiles are a type of Feature Class. We have a few users who mistakenly call all GIS feature classes (shapefiles, SDE, personal gdb, file gdb) shapefiles. I've learned to ask them what them mean by shapefile so I get them what they really need. Same goes for layer, some users call everything including shapefiles layers.

‎09-11-2019

As I understand it, Python 2.7 is not going to stop working and does not have to be uninstalled. However, there will be no bugfixes going forward.

‎09-06-2019

Joshua, that fixed the issue. I'll report this behavior to ESRI since it seems like a bug.

‎09-06-2019

Hi Josh, You are correct, I didn't mention Pro vs ArcMap because we run these scripts in a CMD window. Also, we upgraded all of our ArcGIS Pros to 2.4.1 so I haven't been able to test it with an early version of Pro. I changed the script to run with python 2.7 to verify that it, at least, worked correctly in ArcMap python. The only change needed was changing line 14 from memory to in_memory. Having said that, CopyRows shouldn't be changing field definitions in the first place.

‎09-06-2019

One of my users has a script that works in 2.7 and was working with 3.x but now breaks after the ArcGIS Pro 2.4.1 update. When copying an SDE table into memory using the arcpy.CopyRows_management all text field sizes are increasing from what there are to 5000. For example, text fields of size 1 and 100 become 5000. Our tables are a SQL 2012 / SDE 10.4.1 geodatabase. To see if I could replicate this issue I even created an empty table from scratch containing only two fields, the first is DataSource defined text length 100 and the other is Flag defined as text length 1. Is anyone else seeing this? The user says it was working in version 3 before we pushed out Pro 2.4.1. c:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>python.exe h:\treg\test_inmemory2.py SDE table is : H:\Treg\(Prod) MyDatabase @Reader.sde\ MyDatabase .DBO.WS_Test OBJECTID is a type OID with a length of 4 DataSource is a type String with a length of 100 Flag is a type String with a length of 1 Copying table H:\Treg\(Prod) MyDatabase@Reader.sde\ MyDatabase .DBO.WS_Test into memory... temp table is : memory\tmpTable OBJECTID is a type OID with a length of 4 DataSource is a type String with a length of 5000 Flag is a type String with a length of 5000 try : ##Import modules import os , sys import os . path as path import traceback import arcpy from arcpy import env arcpy . env . overwriteOutput = True sdeTable = r "H:\Treg\(Prod) MyDatabase@Reader.sde\MyDatabase.DBO.WS_Test" tmpTable = r "memory\tmpTable" print ( 'SDE table is : {}\n' . format ( sdeTable ) ) ##check field lengths in SDE text fields fields = arcpy . ListFields ( sdeTable ) for field in fields : print ( '{0} is a type {1} with a length of {2}' . format ( field . name , field . type , field . length ) ) print ( '\nCopying table {} into memory...' . format ( sdeTable ) ) arcpy . CopyRows_management ( sdeTable , tmpTable ) print ( '\ntemp table is : {}\n' . format ( tmpTable ) ) ##check field length on in memory text fields fields = arcpy . ListFields ( tmpTable ) for field in fields : print ( '{0} is a type {1} with a length of {2}' . format ( field . name , field . type , field . length ) ) except : print ( '\n*** ERROR IN SCRIPT!' ) print ( '\n***PYTHON ERROR INFO: \n' + str ( traceback . format_exc ( ) ) ) ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by RandyKreuziger

Re: ArcGIS Pro Tips and Tricks - I share mine, you share yours

Re: Error trying to view locks

Re: How or when should you use a related table over having the data in the geodatabase?

Re: Publish raster dataset as image service with attributes?

Re: Pro: GP Inputs should display full path to sources (as does Arc)

Re: What is the difference between a feature class, layer, shapefile?

Re: Is it possible to remove Python from ArcMap?

Re: Problem with CopyRows_management to in memory with Python 3

Re: Problem with CopyRows_management to in memory with Python 3

Problem with CopyRows_management to in memory with Python 3