Based on user feedback, the topo team has taken six of the most requested topology rules and added them to geodatabase topology for the 10 release. Here’s a quick look at what they are: A complete list of topology rules can be found HERE
If you enjoyed this article, please consider sharing it!
7 Responses to 6 New Topology Rules @ ArcGIS 10
Leave a Reply
You must be logged in to post a comment.
Looks, great.
For next time, here is an idea – it would be awesome if you could combine spatial topology with attribute logic, for example:
myPolygon must contain one point where point.location_type = ‘Hospital’
You might be surprised how often this kind of business rule comes up in gdb design sessions.
Awesome, hardly waited the rule of detecting a point at a point — I am assuming it will also detect topology between objects stored in 3D geometry. Do you have any consideration of implementation of topology rules between objects that change also in time?
-Dejan
@hawatson
Combining attribute based logic with topology rules is something we are now looking at for post-10.
@ssddgreg
Right now, we do not support detecting topology errors between objects in 3D, only 2D. We haven’t really considered implementing topology rules between objects considering time; but as time is more integrated into the Geodatabase, it is something we’ll examine.
I agree with hawatson but would extend it to relational topology. For instance a county layer may have an attribute naming the state that it resides in, and there is a state layer. The topology currently would only show all counties are in all states, what would be beneficial would be to have a relationship class between the county and state layers and then do the topology based on that relationship without having to declare 50-odd subtypes. Is this also being looked at post-10?
@Sibbald – We have talked about a rule called Tessellate which would model the scenario you outline above; a county must be contained within a state, the states feature class must cover the counties feature class and the counties feature class must cover the states feature class. (Note that it is possible to model this now, it requires several rules though)
Combined with attribute based rules (which we are looking at post-10) it may be possible to model this. We don’t get this requirement very often, there are other requests that are more frequent, can you elaborate on the use case for this issue?
@hawatson In theory, you could do attribute logic in topology rules now by using feature class subtypes in your topology rules.
I guess I am not the first and last who will commend on topologies and geometric network at ESRI. There was a demand expressed to have multiple feature classes participating in multiple topologies and/or geometric networks. Is this somewhere on a roadmap? It occurs in nature!