Legacy Issue Number: 17054
Source: SimVentions ( Matthew Wilson)
There is no way to get even a general understanding about where an Entity exists at a general interface level.
Define a new method in the entity interface:
This is logically consistent across any entity type. An entity could still consist of multiple points (e.g., isPointEntity() would return false), and still return a center point. This keeps the conceptual integrity of the entity interface, but expands its utility.
One such concrete example of the utility: Creating a user interface component for scaling a Viewport to a set of points. The most common use case is for those points to be entity positions. The QueryManager can be used to retrieve a list of entities, but from that point on you have to dive into implementation specific details to convert the Entities to a position to choose from.
Part of this resolution is the editorial fix to clean up the “extra” tables in 220.127.116.11.3.
Update the model to reflect the new method in the Entity interface to add getReferencePoint() with a return type of GeodeticPosition.
Add a new section to the specification and update the graphic in paragraph 18.104.22.168 on figure 7.11to reflect the new method.
Returns the GeodeticPosition to be used as the main point of reference for this entity.
Is Abstract false
Reported: TCI 1.0b2 — Thu, 26 Jan 2012 05:00 GMT
Updated: Wed, 1 Feb 2023 21:57 GMT