Latest Contributions by JakeSkinner

1.  Did you re-synch all the database authenticated logins after restoring the database onto the new machine: http://resources.arcgis.com/content/kbase?fa=articleShow&d=29672 2.  Did you restore to a different version of SQL Server (ie 2005 to 2008)?  If so, check to make sure the compatibility level updated: http://resources.arcgis.com/content/kbase?fa=articleShow&d=32979 ... View more

The 'mxd' variable will place a lock on the MXD.  Without deleting this variable, the lock will remain.  For example, you run a python script that makes some change to an MXD and you don't delete the 'mxd' variable.  Then you open this MXD in ArcMap, make another change and then try saving.  You will receive an error that it is in use. ... View more

What RDBMS are you using (i.e. Oracle, SQL Server, PostgreSQL....)? ... View more

I have added to the code to capture the extent ID (it can fill in filename as 'mxd' and not sure how to capture scale) but it is giving errors in identifying the x'th entry in to the list -it prints just the x'th character. Also it's not clear where to put a print statment to give feedback that the program is working on the 2,3,4th etc mxd file. You will need to append the extent ID to a list.  Ex: for el in arcpy.mapping.ListLayoutElements(mxd2, "DATAFRAME_ELEMENT"):         ExtentIDStore = str(el.name)         list2.append(ExtentIDStore) Then you can use print statement for the list: print list2[0] I also notice that it loops first through the mxd's creating extent 1, then loops through creating extent 2 etc. I was initially thinking that it opened the first mxd, cycled through and created all the extent polygons and then opened the next mxd and created the extents. You can code it to do it this way, but the end result will be the same. Also it's not clear where to put a print statement to give feedback that the program is working on the 2,3,4th etc mxd file. You can execute a print statement at the beginning of the first 'for' loop: for mxd in mxdList:     mxd2 = mapping.MapDocument(mxd)     print mxd However, the same MXD name will be printed multiple times since the code loops through each MXD multiple times. ... View more

It appears that the feature datasets were not empty.  Deleting table entries within SQL Server Management Studio is a last resort.  When it comes to feature classes, there are a slew of other table entries/tables that need to be deleted as well. Attempting to delete other table entries can seriously corrupt your database.  I would recommend restoring your database backup and contacting tech support.  They will be able to determine why the feature datasets are still existing even though the database has been deleted. Also, I would recommend using a single geodatabase model in the future.  I find they are much easier to maintain. ... View more

You can do this using the UpdateCursor.  Ex: table = "XY" rows = arcpy.UpdateCursor(table) for row in rows:     if row.field1 > row.field2:         row.Num = row.field1     elif row.field1 < row.field2:         row.Num = row.field2     rows.updateRow(row) del row, rows ... View more

You can delete the empty feature datasets within SQL Server Management Studio.  Before doing so be sure to make a database backup of your SDE geodatabase.  After the backup is created you can run the following query: use SDE delete from sde.GDB_ITEMS where Name = 'TroutCreek.DBO.Model' ... View more

Try creating a new feature class called test.  Does it appear as: TroutCreek.DBO.Test ... View more

This is most likely because you are not connected to the database as the feature dataset owner.  Look at the feature dataset name.  It will be in the following format <database name>.<owner>.<feature class name>.  Ex: Planning.Vector.Parcels In the above example, Vector is the owner.  Next, I would check to make sure I'm connected to the database as Vector by right-clicking on the database > Connection Properties.  If 'Vector' is not listed under 'username' I would change this and specify 'vector' for the username and it's corresponding password. ... View more

Log onto the geodatabase as the feature dataset owner. Then right-click on the feature dataset > Delete. ... View more

In SQL Server Management Studio, open the 'sde.GDB_ITEMS' table.  Under the 'Name' column see if you see the Feature Datasets listed there.  It will be in the format "<database name>.<owner name>.<Feature Dataset name>".  If they exist here, they will exist when viewing the database in ArcCatalog. ... View more

You can publish a File Geodatabase for Query and Extract Data capabilities.  For example, if you wanted users to be able to download a local copy of feature classes within your File Geodatabase you can perform the following steps: 1.  Add the feature classes from the FGD to a map document 2.  Save the MXD 3.  Publish the MXD to ArcGIS Server enabling the 'Geodata Access' capability The client can then add the published map service to ArcMap.  When the user enables the 'Distributed Geodatabase' toolbar the 'Extract Data' tool will be enabled.  They can use this to make a local copy of the feature classes within the map service. Here is more information on Geodata Services. ... View more

Could you explain how these feature datasets were tied to other geodatabases?  Did they participate in a replication?  What is the error you receive when you try to delete the feature datasets? ... View more

Is your master feature class stored in an ArcSDE geodatabase?  If it is I would recommend replication.  You can replicate subsets of the feature class to other SDE, Personal, or File Geodatabases.  Then after making changes to the master feature class you can synchronize changes to the child geodatabases. ... View more

Jake, 1. while y < 7: === this loop creates a shp file with the extents of each dataframe? I guess I can use the same loop to also add in the scale and name of the dataframe into the shp file? 2. for fc in lstFCs: ==== take all the "polygon_extent_*.shp" files and merge them into extents.shp? 3. for item in list: ==== delete the "polygon_extent_*.shp"? The script is intended to create feature classes within the Extents.gdb, which you will need to create before running the script.  This is why you were receiving errors referencing shapefiles.  I believe since the file geodatabase did not exist, the script attempted to create a shapefile.  The 'env.workspace' is set to the Extents.gdb, so all output should be written here. 1.  The while loop with iterate through each mxd starting with the first dataframe , where x = 0.  X will then increase by 1 and iterate through each mxd with the next dataframe[1].  If the dataframe does not exist, for example the mxd does not contain dataframe[4], the script will execute the 'except' and pass the index error.  Yes, you could use the same loop to add the scale and dataframe name to the feature class, but this will take some more coding. 2.  This will take all 'polygon_extent' feature classes and merge them into one feature class. 3.  After the 'polygon_extent' feature classes are merged into one, it will delete the individual 'polygon_extent' feature classes. Hope this helps! ... View more