Geometric Network Snapping -- Separate Tolerance for Separate Region

[EdwardBlair]

Here's a question.

I've got a Geodatabase on which I want to build a geometric network.  But I don't want to apply the same snapping tolerance to the full database.  There are dense regions and there are sparse regions and I'd like to apply a relatively small tolerance in the dense and a relatively large tolerance in the sparse.

One thought I had is to find a way to apply geometric network snapping, by region, outside the process of actually creating the network.  In this way I'd apply a small snap tolerance to the dense and a larger tolerance to the sparse.  Then create the network with the smaller tolerance (or no tolerance at all) knowing that sparse area features have already been snapped.

If I did this I'd need to find the interface that performs geometric network snapping and see if that can be separated from the network creation process.

Anyone done this?  Any comments would be much appreciated.

Thanks,
Ed

[CraigGillgrass]

Ed,

Geometric network snapping cannot be applied by region.  If you are using ArcGIS 10.0 or later; it does use the same code as the Topology Validate process.  One way to solve this issue is to have you data stored in separate geodatabases or feature datasets based on regions and then create a Topology on each applying the cluster tolerance for that specific region.

Craig

[EdwardBlair]

Craig -

I appreciate the feedback.  Thanks.

Not sure I fully follow your suggestion, though.  If I move one region of the network to a different database instance or into a different dataset within the same instance (with new class names of course) then I could just use the normal process for creating a network.

Are you suggesting possibly taking the sparse region, moving it to a separate instance.  Building a network with a course-grained snapping tolerance.  Then drop the network and move it back into the full database and create a new network with a fine-grained tolerance?


Ed

[CraigGillgrass]

Are you suggesting possibly taking the sparse region, moving it to a separate instance.  Building a network with a course-grained snapping tolerance.  Then drop the network and move it back into the full database and create a new network with a fine-grained tolerance?

Yes. That's how other sites have handled this type of situation.