1 / 23

Overview

Overview. OMG C4I GEOSIT Discussions Who is Gallium and What is InterMAPhics InterMAPhics Evolution External definition of the components External definition of the application InterMAPhics 2D/3D Visual Layering Definition by component Map Support User Interaction

JasminFlorian
Télécharger la présentation

Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Overview • OMG C4I GEOSIT Discussions • Who is Gallium and What is InterMAPhics • InterMAPhics Evolution • External definition of the components • External definition of the application • InterMAPhics 2D/3D • Visual Layering • Definition by component • Map Support • User Interaction • External Data Interface • Reduction in Life Cycle Costs

  2. Gallium Introduction • Gallium Software Inc. founded in 1992 • Pioneered mapping and tracking systems starting in the early 1980’s • Single product offering - InterMAPhics • InterMAPhics used to develop the Human-Machine Interface (HMI) • InterMAPhics deployed on wide variety of defense and civilian applications

  3. InterMAPhics History InterMAPhics 2D/3D Version 7 Version 5 Version 4 Version 3 Version 1 Version 2 Customers Current InterMAPhics 100 10 0 Legacy InterMAPhics 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 00 01 02 03 04 05 06 07 08

  4. Version Comparison • Version 3: • First commercial offering of InterMAPhics • External definition of tracks, overlays and tables • Proprietary definition compiler generating C code • Version 4: • Added external definition of user interaction (dialogue) • Proprietary definition compiler generated binary files • Version 5: • Object Oriented API layer • External application definition through rule engine

  5. InterMAPhics 5 External Definition Languages Display Program InterMAPhics Kernel Native Graphics Library Resource Definition IM Libraries Map Data Contact Definition Display Application Code Table Definition Application Definition Graphic Overlay Definition Dialogue Definition

  6. InterMAPhics 5 External Definition Languages Resource Definition • Application level definition and system resources • Determined the appearance of a track • Controlled the layout of tables – typically data blocks • Defined overlays using graphical primitives • Created the state and object interaction logic Contact Definition Table Definition Graphic Overlay Definition Dialogue Definition

  7. InterMAPhics 2D/3D (Version 6) • InterMAPhics 2D/3D • Designed to minimize lifecycle costs • Removed all external definition languages • Complete Object-Oriented API • Greater capability and flexibility • Integration of 2D and 3D capabilities

  8. Visual Layering 50NM ABC1234 123.0 ABC4321 250.0 • Independent visual layers • Containment of entities • Display Rendering • Visual Control • Thread Independence Viewport PresentationLayer MapLayer

  9. Definition of User Components • Definition by containment • Collection of graphical primitives • Relative positioning • No preconceived appearance • Separation of data and visualization • Separation of visualization and behavior PresentationLayer Presentation Primitive PrimitiveGroup

  10. Application Components • Defined structure for common objects • Tracks • Plots • Compass Rose • Range Rings • Supporting application framework • Controllers • Tables • Common design patterns • Used for rapid-development

  11. Map Support • Leveraging mature standards • NGA • ESRI • Independent from component layers • Static visualization • Performance optimized • Layer any number of maps

  12. Map Server Overview ESRI Maps Imagery Maps NGA Maps Client Workstation Client Workstation Client Workstation Disk Cache Map Server Map Service Map Service Disk Cache Memory Cache Memory Cache

  13. User Input • Separation of visualization and behavior • Support for Model-View-Controller pattern • Platform independent events • Implementation of standard controllers • Zoom and pan • Rubber-band zoom • Hook and select • Range and bearing tool

  14. Separation of data and visualization - Model • Separation of model and view • Bridge between GEOSIT product and application • Supports any data source • Tailor visuals to match data source

  15. Separation of data and visualization - View InterMAPhics Application (MFC, QT, Swing)

  16. Reduction in Lifecycle Costs • Significant reduction in training • Development integration of 3rd party tools • Software Design Tools (Rational Rose) • Integrated Development Environments (Visual Studio, Eclipse) • GUI Toolkits ( MFC, QT, Swing) • Object Oriented Development (C++ or Java) • API designed for performance and flexibility

  17. Supporting Slides

  18. Case 1: Standardize the services used to compose a GEOSIT picture • This approach allows system implementers considerable control to “build the picture” in whichever ways they need to while removing some unnecessary redundancies found in current systems and added flexibility in vendor selection. However the means for setting up these features will continue to vary widely from one vendor to the next. If done properly, it provides a means for sharing the data between different “brands” of GEOSIT application such as maps, tracks, overlays, etc within a heterogeneous GEOSIT environment. This approach reduces the scope of each individual service to a more manageable sized elements. • Case 2: Standardize the interface to control and tailor the GEOSIT application • This approach allows system implementers to interact with the GEOSIT at a general application level, thus insulating themselves from vendor-specific implementation issues. At a minimum it provides a standard way to (technically) interact with and manipulate the features within the GEOSIT application. This reduces the complexity and learning curve of programming in a heterogeneous GEOSIT environment.

  19. InterMAPhics 5 Development Cycle Offline Configuration RuntimeManipulation IM Libraries Display Program Compile & link Display Application InterMAPhics Kernel .tsm .tdl .csm .cdl .ssm Native Graphics Library .sdl DDL compile Graphic Symbol Files .tds load Graphic DDL .cds .sds Graphic Datasets .gdl GraphicService Layer .ddl Dialogue DDL DDL compile .dds Dialogue Dataset include Module 2: Overview of InterMAPhics

  20. Typical Track Composition GeoPresentation TrackPresentation2D ScreenString ScreenGroup ScreenMarker ScreenString ScreenString ModelListener WorldPolyline 12 290 450 Module 5: Creating a Track

More Related