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...")
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
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'' 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'').  
# 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?
# 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 ''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

Latest revision as of 22:25, 11 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 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).
  3. 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.
  4. 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.
  5. 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

  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
Retrieved from "https://wiki.railtopomodel.org/index.php?title=Talk:Object_positioning_in_the_network&oldid=694"