Issue 4814: latitude and longitude for Calculated Track Position                                                                                                                                                    (surveillance-ftf)
Source: THALES (Mr. Emmanuel Fuchs, elfuchs@club-internet.fr  omg@elfuchs.com)
Nature: Uncategorized Issue
Severity: 
Summary: Calculated Track Position - this should be in latitude
and longitude to support retrieving track information without having to
define a special set of adaptation of the system plane

Proposed solution : Use latitude and longitude for Calculated Track Position
Resolution: Use latitude and longitude for Calculated Track Position
Revised Text: Page 3.2 suppress I30/100 replace Cartesian by LatLong.

Page 3.4 suppress I3O/100 

Page 3.4 insert 


// LAT LONG COORDINATES


  typedef SFloat  Azimuths;


    typedef Azimuths       LatAzimuths;
    typedef Azimuths       LongAzimuths;

    enum Hemisphere {
        NORTH,
        SOUTH
    };

    enum LatLongDirection {
        EAST,
        WEST
    };


    struct Latitude {
        Hemisphere    lat_hemis;
        LatAzimuths   lat_azim;
    };


    struct Longitude {
        LatLongDirection       long_dir;
        LongAzimuths           long_azim;
    };

    // 2D Position in a LAT/LONG coordinates system
    struct LatLong2DPosition {
        Latitude               latit;
        Longitude              longit;
    };


in 3.2.1.11 I30 Track suppress the field I3O/100 and insert 

LatLong2DPosition latlong_position; // Issue 4814	

In 4, change IDL source

Actions taken:
January 24, 2002: received issue
February 14, 2003: closed issue
Discussion: 

End of Annotations:=====
Date: Thu, 24 Jan 2002 19:10:42 +0100
From: Emmanuel FUCHS <emmanuel.fuchs@thalesatm.com>
Organization: Thales ATM
X-Mailer: Mozilla 4.75 [fr] (WinNT; U)
X-Accept-Language: fr
MIME-Version: 1.0
To: juergen@omg.ORG
CC: FTF surveillance <surveillance-ftf@omg.ORG>
Subject: latitude and longitude for Calculated Track Position 
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: GV3e93J\!!`I%e9$Z"e9

Hi Juergen

A new issue for surveillance FTF

Calculated Track Position - this should be in latitude
and longitude to support retrieving track information without having
to
define a special set of adaptation of the system plane

Proposed solution : Use latitude and longitude for Calculated Track
Position

Thank you

Emmanuel FUCHS