Tactical Situation Display TACSIT Standards Discussion - PowerPoint PPT Presentation

1 / 12
About This Presentation
Title:

Tactical Situation Display TACSIT Standards Discussion

Description:

OMG Tech Meeting Burlingame, CA Feb 05. 1. Tactical Situation Display (TACSIT) ... OMG Tech Meeting Burlingame, CA Feb 05. 2. Objective. To open the discussion ... – PowerPoint PPT presentation

Number of Views:286
Avg rating:3.0/5.0
Slides: 13
Provided by: omg3
Category:

less

Transcript and Presenter's Notes

Title: Tactical Situation Display TACSIT Standards Discussion


1
Tactical Situation Display (TACSIT) Standards
Discussion
  • Kickoff discussion
  • Matt Wilson / Sonalysts Inc (NSWCDD)

2
Objective
  • To open the discussion on TACSIT standards
  • Identify potential topic areas
  • Get feedback on topics areas
  • Not limit scope (yet)

3
Desirable end-state
  • Common map data files
  • Map updates
  • Common map server
  • Consistent look
  • Consistent actions
  • Shared overlay / graphics data
  • Reduce vendor specialized internal track files
  • Remote cursors
  • Playback / Replay capabilities

4
Resulting Topic Areas
  • Map Data Formats
  • Track Interface / Data Standards
  • Look and Feel Tailoring
  • Standard API for getting / initiating track
    related HCI actions
  • Graphic Overlay Interchange
  • Playback

5
Map Data Format
  • Map information for tactical use
  • Elevation / Depth
  • Coastline / National Boundary / Territorial
  • Airways / Shipping routes
  • Navigation Data
  • Overlays / Shapes
  • Options
  • Common processed format?
  • Common source format?
  • Common pre-processor API?

6
Map Data Format (explained)
  • Storage / Delivery Issues
  • Size, update, in-process, batch
  • Common processed format
  • The rendering engines use a common format
    directly
  • No additional conversion step required
  • Facilitates a common Map Server in the system
  • Common pre-processor API
  • Each GIS app confirms to the same API for
    converting source data for internal use.
  • Requires common source format
  • Common source format
  • Standardized map input format
  • Not necessarily pre-optimized

Processed Data
Processed Data
7
Track Interface / Data Standard
  • Standard approach to plugging in a track data
    stream
  • Extensible standard for track data stream(s)
  • Track Data format with open extensions
  • Track file format with open extensions

TrackProducer(s)
Track Consumer API
TACSIT app
8
Look and Feel Tailoring
  • Track-to-symbol taxonomy
  • Track type taxonomy
  • Standard symbology sets (NATO, NTDS, 2525B)
  • Plug-in Symbol set
  • Annotations / modifiers to base symbols
  • Land and water colors
  • flat and elevation contours
  • Named graphic element colors
  • Overlays
  • Pairing lines
  • Sectors
  • Number, shape, size, color of hook symbols

9
Track manipulation HCI actions
  • Triggering / registering for track related
    actions
  • Triggering / registering for hook actions
  • Primary, secondary
  • Consistent results of input device interaction
  • Select, range in/out, pre-hook, etc.
  • Other track related actions
  • Type change, drop, etc.

10
Graphic Interchange
  • Transfer of shapes
  • Remote cursors
  • other consoles / operators
  • Remote / Large Screen Displays
  • How many / control (on same display)
  • Support for copy / capture screen
  • I believe some of this may be under Open GIS
    consortium?

11
Playback / Replay / Logging
  • Track Data
  • Operator Actions
  • Viewer state changes
  • Range scale / offset
  • Graphics visible
  • Historical screen capture

12
Discussion Topics
  • What topics do we want to tackle?
  • Single standard vs. subset standards
  • Data Interface
  • Map, Track
  • Visual Tailoring / Functional interface
  • Which standards belong in this body vs. others
  • What existing standards exist?
Write a Comment
User Comments (0)
About PowerShow.com