Latest Contributions by CraigGillgrass

Chris, Take a look at the following article: http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/Creating_geodatabases/0001000004t8000000/ It shows how to create geodatabases stored in SQL Server Express. ... View more

32 is a lot of feature classes to have a in a geometric network, it's probably the most number of classes that I've ever seen.  Here's why I'm raising this as an potential issue; as I mentioned, each time you create a new feature, the geodatabase opens a cursor on each class in the network.  If we can handle 5 cursors in 1 second (as an example); you would be looking at over 6 seconds to determine whether there are any features at that location.  This is a cost you are paying every time you create a new feature.  So, I would strongly suggest that you try and re-assess the number of feature classes in your network.  If you are adamant that you cannot either decrease the number of feature classes in the network or drop the network in order to load the features; then consider using a Map Cache.  If you're loading data into discrete areas of you network, with a reasonable number of existing features (reasonable being a couple thousand) you could try to build a Map Cache over the area you're loading the features into.  This could speed up a performance a bit, but you will need to prototype this. ... View more

While there is no limitation to the number of feature classes you can have in a geometric network, every feature class you have in the network comes with a cost. Each time a feature is created, the geometric network has to search through each class and determine if there are any coincident features.  So, the more feature classes you have in the network, the more time it takes to search for any coincident features.  The object loader is essentially a batch loader that automates the loading of features; but it still has to create them one at a time. I'd suggest that you look at ways of decreasing the number of feature classes in your network by combining several feature classes into 1 and using subtypes.  You can also look at eliminating any feature classes that aren't being used at this time, if you've added empty feature classes to the network thinking you'll use them at some point in the future, remove them and only add them when needed. you best option is probably to delete the geometric network, get all your data loaded and then recreate it.  It will no doubt be much faster. You never responded with how many features you are loading into the network. Can you respond with that? ... View more

Without more specifics on the relationship classes you want to create, I can't really comment on the data model structure.  Your examples, while helpful, don't really demonstrate how you'd like to use the relationship classes. ... View more

The object loader in ArcMap is the recommended method of loading data into a geometric network after it has been created.  Can you clarify how many features you loading and how many feature classes are in the geometric network? ... View more

This is by design, as a feature class/table cannot participate in multiple composite relationship classes.  Since composite relationship classes control the lifetime of features/rows, having multiples of these causes issues when editing. ... View more

Dave, Can you contact Tech Support and log an incident for this issue? http://support.esri.com/phoneSupport#us We'll probably need to get a dump of your database in house for testing.  I have not seen this issue before. thanks, ... View more

Do you have Archiving enabled on any of the classes that have edits which are being reconciled with Default? ... View more

It is not possible for geodatabase behavior, such as Topology rules to span across geodatabases, whether the geodatabase is ArcSDE, Personal or File. Two datasets cannot share a geometric network.  Advanced datasets, such as geometric networks, topologies, terrains, live within a feature dataset and only those feature classes in the feature dataset may be used in the advanced dataset. ... View more

There are a few customizations available to do this on the ArcScripts site; one of them is this script: http://arcscripts.esri.com/details.asp?dbid=15694 We are planning on adding the ability to track the last editor user and date along with creation editor and date at 10.1. ... View more

The edges do not become connected, because they are simple edges.  Connectivity for simple edges is only supported at edge endpoints. You'll need to determine whether this is a data issue that must be corrected (the edge should be physically split) or whether you should be using complex edges to establish connectivity. You should understand the differences between simple and complex edges before making this decision. ... View more

The behavior of how simple edges are snapped at mid-span when snapping is enabled during GN building has changed at 10.0. In 9.3 the behavior was are simple edges NOT snapped within the cluster tolerance at mid-span vertexes and vertexes are NOT inserted where needed to snap to, and no connectivity established for either condition. As part of the reworking of the GN creation code to provide a more scalable solution, we had to change how this aspect of the snapping model behaves.  So, in 10.0 simple edges are snapped within the cluster tolerance at mid-span vertexes or a vertex is inserted and snapped to, but no connectivity is established for either condition. ... View more

I'm not able to reproduce this behavior using 10.0 or our current builds. A couple of questions that will help narrow this down: Have you confirmed that the ModelName is set in the 9.3.1 SP2 geodatabase? Are you using ArcGIS 10.0 without any patches or hot fixes? Can you supply the code you are using to retrieve the ModelName, I may be doing something differently in my repro case. Finally, what type of ArcSDE database are you using; Oracle, SQL Server, etc?  What is the size of the database?  We may need to get the database in house to reproduce the issue. thanks, ... View more

ObjectIDs are managed and controlled by the Geodatabase, they are also unique within a given feature class/table within a Geodatabase.  You cannot control the values assigned as ObjectIDs within a feature class/table.  While the Insert cursors do not maintain ObjectIDs between feature classes/tables, since you are inserting new records into the target, Copy/Paste does maintain ObjectIDs.  Why do you need to keep the ObjectIDs consistent between your source and target Geodatabases? ... View more

Jackie, The error you ran into is a known issue that we've addressed for 10.0 Final.  The metadata of the feature class that the upgrade failed on pd_data_prod.INFRASTRUCTURE.ZIPCODE_GENERALIZED, contains a Document Type Definition (DTD).  For final, we'll be removing these from the metadata.  In the meantime, if you need to upgrade this geodatabase, you can get around this issue by deleting the metadata associated with the feature class.  If you're not able to do this, you'll have to wait for 10.0 Final before proceeding. ... View more