Talk:Object positioning in the network: Difference between revisions

From railTOPOMODEL® Wiki
Jump to navigation Jump to search
(Created page with "== Assumptions I made when writing this page== # ''ElementPart'' is a class needed for splitting and fusioning NetElements for creating a new Network level. It has no specific...")
 
mNo edit summary
Line 1: Line 1:
== Assumptions I made when writing this page==
== 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
# ''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 linear NetElement has an orientation which means it has a beginning and an end, denoted by intrinsicCoordinates 0 and 1. It has to be defined how this orientation is assigned to the NetElement within the model
# Each AssociatedNetElement refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation is somehow redundant, since it is covered by the netElements relation of AssociatedNetElement (see class diagram above). The model allows one ore more PositionedNetElement, but in case of more than one, where do the intrinsic coordinates or the parameter keepsOrientation refer to?  
# Each AssociatedNetElement refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation can be eliminated from the model, since it is covered by the netElements relation of AssociatedNetElement (see class diagram above). The model allows one ore more PositionedNetElement, but in case of more than one, where do the intrinsic coordinates or the parameter keepsOrientation refer to?
# 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 ''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 PositionedNetElement. It is "0=false" if the orientation is reverse. (Model says in Fig. 42 it is described as relevant / not relevant)
 
== 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
# Orientations are relevant in LinearLocations, not in AreaLocations.

Revision as of 08:21, 10 September 2016

Assumptions and Questions

  1. 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
  2. Each AssociatedNetElement refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation is somehow redundant, since it is covered by the netElements relation of AssociatedNetElement (see class diagram above). The model allows one ore more PositionedNetElement, but in case of more than one, where do the intrinsic coordinates or the parameter keepsOrientation refer to?
  3. 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.
  4. The parameter keepsOrientation of AssociateNetElement is "1=true" if the orientation of the AssociateNetElement is the same as the PositionedNetElement. It is "0=false" if the orientation is reverse. (Model says in Fig. 42 it is described as relevant / not relevant)

Insights

  1. 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.
  2. The PositionedRelations are crucial for building LinearLocations, including routes, since they define the navigability and orientation of the NetElements along the sequence
  3. Orientations are relevant in LinearLocations, not in AreaLocations.
Retrieved from "https://wiki.railtopomodel.org/index.php?title=Talk:Object_positioning_in_the_network&oldid=691"