I'll be talking about the new multiport
functionality that's been added to NMT 3.5.
In summary,
what we've done is we've allowed users to model features in the
application and be able to define how the connectivity works within it.
So if we click on this manhole here,
you'll see that there is a new feature called a switch.
It feeds in from this building and it can either leave
down this small pathway to the south
or towards the rest of the network up north.
Now,
also what you can see is in the feature details,
we also have a new field,
which is a connection mapping field.
So the foundations of what this
feature does or this switch does,
if we trace down from feature one,
from pin one,
we see that it goes up north of the
network and south down the network as well.
And if we trace downstream from the second pin,
we can see that it only travels
down the south of the network.
So let's say we want to edit this
and edit how the connectivity within this feature works.
We essentially want to change this connection mapping attribute.
Click the edit button and to the
right of the connection mapping field,
you'll select this button here.
So
let's say we no longer want the second pin to travel south.
We want it to travel north instead.
So we can remove that and add in the second pin instead.
So essentially what this connection mapping says is
whatever comes in from this port leaves from these ports.
So what it supports is
single port to range,
range to single port or range to range.
However, the ranges have to be of the same size.
So one to two and three to four instead
of one to two and three to five.
So let's see how this changes the behavior.
We changed this.
So we've said that instead of
whatever comes in from port two leaves on port one,
we've said whatever comes in port two leaves from port two.
So if we save that
and we trace downstream from port two,
we now see that instead of going down south,
it now comes up north of the network.
