Talk:Object positioning in the network
Jump to navigation
Jump to search
Assumptions and Questions
- ElementPart is a class needed for splitting and fusioning NetElements for creating a new Network level. It has no specific role for positioning. Here, AssociatedNetElement is used, as described in the model
- Each AssociatedNetElement in my understanding refers to one and only one PositionedNetElement, which is the unique reference for the AssociatedNetElement's parameters (intrinsic coordinates begin and end and keepsOrientation).
- Question: Maybe the association netElement of Linear/AreaLocation is redundant, since AssociatedNetElement can be understood as the association class between Linear/AreaLocation and PositionedNetElement. See class diagramm OrderedAssociatedNetElement from the model on the wiki page.
- The applicationDirection of a SpotLocation refers to the orientation of the netElement of the SpotLocation. In the model it is defined with repect to the "LinearLocation" - might be an error.
- The parameter keepsOrientation of AssociateNetElement is "1=true" if the orientation of the AssociateNetElement is the same as the (unique) PositionedNetElement. It is "0=false" if the orientation is reverse. In the Model it is described as relevant / not relevant (Fig. 42).
Insights
- Each PositioningNetElement has an orientation which means it has a beginning and an end, denoted by intrinsicCoordinates 0 and 1. Those are defined by the PositionedRelations referring to this PositioningNetElement.
- The PositionedRelations are crucial for building LinearLocations, including routes, since they define the navigability and orientation of the NetElements along the sequence