Latest Contributions by JakeSkinner

Personal Geodatabase are still supported at ArcGIS Desktop 10.1.  However, they are not supported with ArcGIS Server 10.1.  Take a look at the following PDF. ArcGIS Server 10.1 will no longer support the Microsoft Access based Personal Geodatabase. With the migration of ArcGIS Server to be 64-bit and because of the lack of scalability of Personal Geodatabases, we have removed support for Personal Geodatabases from ArcGIS server 10.1. Personal Geodatabases will continue to be supported on ArcGIS Desktop. Also, at 10.1 you can rename fields within Personal/File Geodatabases using ArcCatalog.  I believe moving the fields is still restricted to the MXD. ... View more

Hi Matt, What version of ArcSDE and what RDBMS are you running? Also, what type of replicas do you have (i.e. Two-way, One-way, etc)?  How many versions do you have, or are you just editing the SDE.Default version? ... View more

It may be best to delete the entries from the 'sde.sde_process_information' table.  What database are using (Oracle, SQL Server, PostgreSQL,...)? Here's an example query on how to do this using SQL Server: delete from sde.SDE_process_information where start_time < (select getdate() - 1) ... View more

Hi Brent, You can use the 'sdemon -o kill' command and specify the PID for the connection that is greater than 24 hours.  The 'sdemon -o info -I users' command will list each user connected, the PID, and the start time of the connection. Or, are you looking for a more automated approach to do this? ... View more

Try changing your expression variable to: expression = "round(!WSPD_SFC!/5.0, 0) * 5.0" Since the expression is quoted as a string, it will not read 'input' as a variable.  It will read this as a string literal. ... View more

Are you storing Raster and Vector data within the File Geodatabase?  What version of ArcGIS are you using? ... View more

1) Do you have to specify the specific table within the GDB, or can you run it on all of the feature classes within the geodatabase? The table I'm writing all of the feature class names to is specified here: table = r"C:\TEMP\Python\FieldNames.dbf" If the table exists within the geodatabase (not as a DBF), I can simply specify the name of that table.  Ex: table = "FieldNames" 2) I can't find where you specify the attribute field name within the code. YOu say mean to update an existing field called "Names" but I can't see where this is in the code. That was a type-o on my part.  The field name in the above example is called 'Fields', not 'Names'.  I'm calling this field using 'row.Fields = item'. for item in list:     rows = arcpy.InsertCursor(table)     row = rows.newRow()     row.Fields = item     rows.insertRow(row)     print "Successfully inserted" ... View more

Looks like you are using the Union_arc tool, which is for coverages.  Try the Union_analysis tool, which is for feature classes/shapefiles. ... View more

Try specifying '.shp' for your input layers.  Ex: inCover="kreisumring.shp" unionCover="gemeinden.shp" ... View more

Hi Jin, This is actually for ArcGIS 10.  You will need to replace 'arcpy' with 'gp' to have this work with 9.3.  Also, you will need to make a few changes to the 'SearchCursor'.  Here is a link that discusses how to do this for 9.3. ... View more

Hi Dan, Here is an example on how to do this.  The below code will list all the feature classes in a geodatabase (including feature classes within feature datasets), insert a record into a dbf table, and update an existing field within the table called 'Names' with the feature class name. import arcpy from arcpy import env env.workspace = r"C:\TEMP\Python\Test.gdb" table = r"C:\TEMP\Python\FieldNames.dbf" list = [] lstFCs = arcpy.ListFeatureClasses("*", "") for fc in lstFCs:     list.append(fc) del fc, lstFCs     lstDatasets = arcpy.ListDatasets("*") for dataset in lstDatasets:     lstFCs = arcpy.ListFeatureClasses("*", "", dataset)     for fc in lstFCs:         list.append(fc) for item in list:     rows = arcpy.InsertCursor(table)     row = rows.newRow()     row.Fields = item     rows.insertRow(row)     print "Successfully inserted" del row, rows ... View more

Hi Jin, I was able to do this using the cx_Oracle module.  Here is an example: import arcpy, cx_Oracle from arcpy import env env.workspace = r"C:\TEMP\Python\Test.gdb" env.overwriteOutput = 1 fc = "Hospitals" list = [] # append all CODE values from feature class to list rows = arcpy.SearchCursor(fc) for row in rows:     list.append(row.getValue("FAC_TYPE")) # create a connection to Oracle instance    connstr='vector/vector@orcl' conn = cx_Oracle.connect(connstr) curs = conn.cursor() oracleList = [] # query Oracle table using items from list and append to new list for item in list:     curs.execute('select FAC_TYPE FROM Hospital_Info where FAC_TYPE = ' + str(item))     for row in curs:         oracleList.append(row[0]) # Find items that have duplicates and delete from feature class for item in set(oracleList):     if oracleList.count(item) > 1:         arcpy.MakeFeatureLayer_management(fc, "Hospital_Lyr", "FAC_TYPE = " + str(item))         arcpy.DeleteRows_management("Hospital_Lyr")         print "Successfully deleted rows"     conn.close() ... View more

Hi Dan, A database connection is made for each ArcGIS Server instance (ArcSOC.exe) that is created for the service(s).  The min and max number of instances can be set by right-clicking on the service > Service Properties > Pooling tab.  By default, the minimum number of instances is set to 1 and the maximum is set to 2.  Therefore, when you start the service 1 connection is made to the SDE geodatabase. By default, an instance is created as Pooled.  This means when a request (ie pan/zoom in web app) is made to the service, an instance is taken from the pool, and then returned when the request is over. Once another request is made, say from another web app, that same instance can be used for that service request.  So, multiple requests will need to be made at the same time in order for another instance to be created, thus creating another connection to the SDE geodatabase.  This will not exceed the maximum number of instances, so by default a service can never exceed two connections to the geodatabase unless this paramter is increased.  If the max number of instances is exceeded, the client will have to wait until an instance is returned to the pool before their request is returned. Say the max instances of a service is set to two and both are being used, creating two connections to the SDE geodatabase.  Then one of the users is finished accessing the service. The second SDE connection will remain until the idle time expires (set within the Services Properties > Pooling tab).  Once the idle time expires, the instance will be removed from the server and the connection deleted from the SDE geodatabase. ... View more