Skip to main content
Question

Can I use the NetworkTopologyCalculator to differentiate between different elevations (3D)?

  • September 12, 2016
  • 6 replies
  • 28 views
Y

Hi, I have a road network that I've been using the NetworkTopologyCalculator on to identify unconnected roads which I then discard to avoid drivers getting stick on an piece of road.

But, what I've just had pointed out to me is that my method isn't catching all unconnected roads. Some unconnected roads pass under/over the valid road network, touching nodes, which the

NetworkTopologyCalculator assumes are part of the valid road network. I have an elevation indicator for the start and end of each road segment, so I though by using the 3DInterpolator this would allow the

NetworkTopologyCalculator to identify that the roads were not touching at bridges/tunnels, but this does not seem to be the case.

Has anyone encountered such an issue, and if so are there any tools that might assist me here?

Thanks

Rich.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • 1442 replies
  • September 12, 2016

Hi,

The LineOnLineOverlayer can be used before the NetworkTopologyCalculator to intersect all lines and therefore making roads going under/over participate in the network analysis.

mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • September 12, 2016

I don't think the NetworkTopologyCalculator handles Z values very well - but neither does any other transformer that you might use in this case.

I would try dropping all lines to points (Chopper) and testing for matching points. Use the Matcher with 3D geometry matching.

FME Evangelist to the Rich and Famous!!
R
Forum|alt.badge.img
  • ras
  • 9 replies
  • May 17, 2019

I don't think the NetworkTopologyCalculator handles Z values very well - but neither does any other transformer that you might use in this case.

I would try dropping all lines to points (Chopper) and testing for matching points. Use the Matcher with 3D geometry matching.

Hello @mark2atsafe

I ran into same issues. I need to analyse a 3D pipe network and FME is treating it as a 2D problem. Things seem to overlap in 2D, but in 3D they do not. :(

Are there any plans to give the 3D part of FME some upgrades?

mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • May 21, 2019

Hello @mark2atsafe

I ran into same issues. I need to analyse a 3D pipe network and FME is treating it as a 2D problem. Things seem to overlap in 2D, but in 3D they do not. :(

Are there any plans to give the 3D part of FME some upgrades?

I honestly don't know what to suggest here. We are trying to improve all our 3D transformers, but I doubt that the TopologyBuilder is very high on this list. You may want to publish that as an idea on this site, and see if you can get other users to upvote it. I don't see an alternative method for creating a 3D topological network, except to isolate all of the line endpoints and do comparisons to see what matches. What I'll do is pass this on to our tech experts team, to see if anyone has experience of doing such a thing and if they are able to help further.

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • May 22, 2019

I honestly don't know what to suggest here. We are trying to improve all our 3D transformers, but I doubt that the TopologyBuilder is very high on this list. You may want to publish that as an idea on this site, and see if you can get other users to upvote it. I don't see an alternative method for creating a 3D topological network, except to isolate all of the line endpoints and do comparisons to see what matches. What I'll do is pass this on to our tech experts team, to see if anyone has experience of doing such a thing and if they are able to help further.

I checked with my colleague and there is currently nothing in FME designed to do this. But one colleague suggested there is a way we could implement this, given enough demand, so please do file this as an idea on this site if it is important and we will keep watch to gauge demand. Another colleague suggested the LineCombiner with "Consider Node Elevation" set to Yes might help, but I haven't been able to test that idea. Hopefully it will work if you try it out.

FME Evangelist to the Rich and Famous!!
jdh
Contributor
Forum|alt.badge.img+37
  • jdhContributor
  • Contributor
  • 2002 replies
  • May 22, 2019

Hello @mark2atsafe

I ran into same issues. I need to analyse a 3D pipe network and FME is treating it as a 2D problem. Things seem to overlap in 2D, but in 3D they do not. :(

Are there any plans to give the 3D part of FME some upgrades?

The networkTopologyCalculator only sees connections at nodes. Is there a way to join you input data (ex lineCombiner - consider node elevation yes)) so there are no nodes at the false intersections.

 

 

If that is not possible, you could rig something up in python using graph theory and connected components.

Community Stats

32,080
Posts
121,820
Replies
39,714
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.