Latest Contributions by RickMomsen

‎06-29-2023

@SSWoodward I just upgraded to 3.1.0 for this functionality and it is not working. arcpy.CreateFeatureclass_management(gdb, "sometest3", template=fc_template) fc_template has a handful of domains and none transferred over to sometest3 is this a 3.1.1 functionality?

‎12-17-2015

The data access module (.da) was introduced at 10.1. When I first converted my scripts to use the da cursors and saw the performance improvement I did cartwheels down the hallway. I recommend everyone using 10.1 + do it. (the da upgrade - not the cartwheels)

‎12-11-2013

This worked perfect for me too, but it took a lot of searching to find this thread. adding key words for future victims... Failed to compress the database Cannot insert the value NULL into column 'compress_id', table SDE_COMPRESS_LOG column does not allow nulls. INSERT fails

‎07-25-2013

I didn't have a problem reconciling between Public versions, but I got the same error when reconciling up to a Protected version. I got around this by inserting the owner information before the version name (ie, 'owner.version' rather than 'version'), and when logged in as SDE the script ran fine. Russel is correct that the wrong error message is given - luckily this is one of the first threads I came upon.

‎07-09-2013

I'm having a problem where the Feature Compare tool is not working as expected. I am trying to compare the shapes of two polygons between the two feature classes - both have only two polygons. I am using the geoprocessing tool and not a script. The result states that the "Geometries are the same", but as you can see from the attachment this is clearly not the case (nearly 70 meters off). Most of the vertices are coincident, but not in this particular area. I have my input parameters below. Does anyone see where I'm going wrong? Thanks in advance for your help. -Rick system: Arc 10.0 - ArcInfo Both FCs are in a FGDB, but not the same feature dataset Both FCs have identical spatial reference Input parameters: * sort field: compare (I added this field to both, and double checked to make sure "1" and "2" represented the appropriate polygons) * Compare type: GEOMETRY_ONLY * Ignore options: ignore Z, M, PointID, ExtensionProps, SubTypes, RelationshipClasses, and RepresentationClasses (in other words...everything) * XY Tolerance: 0.001 Meters * M Tolerance: 0 * Z Tolerance: 0 * Attribute Tolerance: <blank> * Omit Fields: <all of them except for the "compare" field> * Continue Comparison: true [ATTACH=CONFIG]25827[/ATTACH]

‎06-09-2011

CC, The 'simplest' method is to export your updated PGDB FC metadata to XML (or desired format) and then import each file into the respective FC in SDE. Anything 'easier' will have to be programmed. If your organization updates metadata often, you may want to consider updating metadata in SDE since that will copy over to your export. Note that replications will not help your situation: "Metadata for the feature classes and tables you choose to replicate is copied during the replica creation process. However, changes to the metadata are not applied during replica synchronization."

‎06-09-2011

Craig, One possible cause of this is if one of your users created the version as 'private'. In this case, the only other user that can see this version is SDE; who can also delete it. You can also check the SDE.VERSIONS table to see all versions and their properties.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by RickMomsen

Re: Create feature class template with Domains

Re: Efficient way to delete all table rows

Re: Failed to compress database, why?

Re: ReconcileVersion Conflicts Detected

FeatureCompare problem

Re: transfer metadata to SDE

Re: Cannot delete version