You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the draft data model, the route of a link between its endpoints is represented as a LineString.
However, the supply side research surfaced examples of networks, in which there are junctions that are not specifically declared as nodes:
On closer inspection of the above example (interactive version), links are represented as LineStrings and the apparent junctions are actually the result of two links partially sharing the same route. For example, there is one link between MSU1 and RLU06 and one link between MSU1 and EST01:
So this network can be represented using the draft data model.
The text was updated successfully, but these errors were encountered:
In the draft data model, the route of a link between its endpoints is represented as a LineString.
However, the supply side research surfaced examples of networks, in which there are junctions that are not specifically declared as nodes:
On closer inspection of the above example (interactive version), links are represented as LineStrings and the apparent junctions are actually the result of two links partially sharing the same route. For example, there is one link between MSU1 and RLU06 and one link between MSU1 and EST01:
So this network can be represented using the draft data model.
The text was updated successfully, but these errors were encountered: