Problem: Connectivity isn’t established properly when using an Any Vertex connectivity policy and elevation fields
【相关信息】
Article ID: 40574
Bug Id: N/A
Software:
ArcGIS - ArcEditor 9.3.1, 10
ArcGIS - ArcInfo 9.3.1, 10
ArcGIS - ArcView 9.3.1, 10
ArcGIS for Desktop Advanced 10.1
ArcGIS for Desktop Standard 10.1
ArcGIS for Desktop Basic 10.1
Platforms:
Windows XP, Server 2003, Vista, Server 2008, Windows 7
【问题描述】
Using Any Vertex connectivity in conjunction with field-based elevation can cause undesirable connectivity in the network.
【原因】
When using field-based elevation in a network, only the endpoints of edges actually carry the elevation values. So on an edge that has a From elevation of 1 and a To elevation of 3, only the corresponding endpoints carry the respective elevation values. All of the vertices between the endpoints carry NULL elevation values. This means that any intersection where an endpoint of one edge is coincident to a non-endpoint vertex of another edge, true connectivity can’t be established even if the policy is set to Any Vertex.
However, in this same configuration, if a non-endpoint vertex is coincident with another non-endpoint vertex, connectivity is established because both vertices share the same elevation (which is NULL) even though the endpoints may not have the same elevation values. This means that connectivity can occur in areas where it shouldn't, and it may not occur in areas where it is intended to.
Article ID: 40574
Bug Id: N/A
Software:
ArcGIS - ArcEditor 9.3.1, 10
ArcGIS - ArcInfo 9.3.1, 10
ArcGIS - ArcView 9.3.1, 10
ArcGIS for Desktop Advanced 10.1
ArcGIS for Desktop Standard 10.1
ArcGIS for Desktop Basic 10.1
Platforms:
Windows XP, Server 2003, Vista, Server 2008, Windows 7
【问题描述】
Using Any Vertex connectivity in conjunction with field-based elevation can cause undesirable connectivity in the network.
【原因】
When using field-based elevation in a network, only the endpoints of edges actually carry the elevation values. So on an edge that has a From elevation of 1 and a To elevation of 3, only the corresponding endpoints carry the respective elevation values. All of the vertices between the endpoints carry NULL elevation values. This means that any intersection where an endpoint of one edge is coincident to a non-endpoint vertex of another edge, true connectivity can’t be established even if the policy is set to Any Vertex.
However, in this same configuration, if a non-endpoint vertex is coincident with another non-endpoint vertex, connectivity is established because both vertices share the same elevation (which is NULL) even though the endpoints may not have the same elevation values. This means that connectivity can occur in areas where it shouldn't, and it may not occur in areas where it is intended to.
1 个回复
EsriSupport
赞同来自:
There are several ways to fix this. Keep in mind that retaining data integrity and simplicity is usually considered the best practice.
Make sure that fields sourcing the distance and time-to-traverse costs are recalculated after doing this, as attributes are copied to both features when a line is split.
【其它相关参考】
【创建及修改时间】
Created: 9/26/2012
Last Modified: 7/12/2013
【原文链接】
http://support.esri.com/en/kno ... 40574
要回复问题请先登录或注册