1. CIGI Drafting Group Agenda
Review open Action Items
Review PCR 12 implementation (thus far)
Review Extension Packet implementation
Cartesian placement proposal
Discuss “Ignored by the IG” issue
New task assignments

2. Open Actions
ACTION 7.1: MG - Confirm 64-bit entity type message fields are correctly placed. New packet data provided. Included in Fall SIW draft.
ACTION 7.2: CS - Prepare presentation for Fall SIW describing proposed changes to add Cartesian Coordinate support. Included later in this presentation.
ACTION 7.3: CS - Send an reminder for the final version of the June 25 & 27 meeting minutes to be uploaded. Reminder sent Aug. 13.
ACTION 8.1: CS – Add DIS reference document to Appendix D and reference it in the ICD. Point out existence of 16-bit DIS entity types. Included in Fall SIW draft.
ACTION 8.2: RH – Assemble straw man list of “shall be ignored” cases and categorize them.

3. Review PCR 12 Implementation
Overview on pages 7, 8, 39 – 41
First packets changed on pages 43 & 241

4. Review Extension Packet Changes
Reference on page 8
Expanded content on pages 291 – 294
New appendices on pages 298, 299

5. Cartesian Position Proposals
Goal - provide the ability to use 3D Cartesian coordinates for placement instead of Lat/Lon/Alt to properly support small, Flat-Earth use cases
Current work-around does not support ground-clamping of entities
Two possible methods to enable Cartesian Positioning:
Add new Boolean parameter to Earth Reference Model Definition packet for Cartesian mode
Revise Earth Reference Model Definition packet to use Spatial Reference Frames defined in the SEDRIS SRM

6. Cartesian Reference Parameter
Add new Boolean parameter to Earth Reference Model Definition packet
Pros:
Easy to document and understand
Implementation should be easy for IG vendors
Minor version friendly
Cons:
Not a generic solution, i.e. inclusion of additional reference models requires a new ICD version

7. SRM Spatial Reference Frames
Revise Earth Reference Model Definition packet to use Spatial Reference Frames defined by the SEDRIS SRM
Pros:
Builds on an existing SISO standard
Is a generic solution; any registered Spatial Reference Frame (SRF) from the SEDRIS SRM can potentially be used without changing the CIGI ICD
Expands IG support to high Earth orbit and other planetary bodies
Could be a new product discriminator for IG vendors
Cons:
Requires a major version change
More complicated to document
May not be easy to understand by new users; will need to provide a Cartesian positioning sample in the draft reference document.
Full implementation may not be of interest to IG vendors
All0wing partial implementation, i.e. support for a documented subset that minimally includes WGS-84 and Cartesian placement, could complicate compliance testing

8. Generic Position Parameters
Irrespective of how Cartesian positioning is enabled, all parameters associated with top level object placement, e.g. Entity Position, Environmental Region Control, HAT/HOT, etc, need to be changed to a generic vector for position data
Lat, Lon, & Alt parameters would become a generic vector {a, b, c}, where the usage of each vector element is dependent upon the specific spatial reference model in use

9. Discuss “Ignored by the IG” Issue
‘Packets referencing non-existent objects shall be ignored unless the packet can be used to instantiate the object.’
Ignoring errors can lead to unexpected results
What is a CIGI error? Something that is not expected by the IG. Examples:
Invalid packet size
Referencing non-existent entity
Undefined entity type
Should error and debug info be separated?

10. IG Message Packet Content
Currently considered the same as debug information
Should the ICD provide a recommended IG Message format for each "shall be ignored“ in the ICD?
Provide more debugging data to the end user
Potentially provide a high degree of conformity between the IG vendors that chose to implement the capability
Only in Debug mode? If “yes”, then implement several broadly defined IG Condition flags in the SoF packet as well to annunciate problems outside of Debug mode?
Add a verbosity level (e.g. info, warning, error)?

11. New Actions
ACTION 9.1: CS Search for all instances of “user-defined” related to the old User Defined packets and update as appropriate for the new Extension Packet paradigm.
ACTION 9.2: CS Add an entity type roll-up enable to IG Control packet. Completed during workshop.
ACTION 9.3: CS Draft a PCR for the SRM Spatial Reference Frame positioning enhancement.
ACTION 9.4: WP Draft a PCR listing standard Message IDs for the IG Message packet.
ACTION 9.5: RH Draft a PCR to define standard error messages to be returned by IG Message packet and a standard Message ID for “machine readable” messages that can be parsed by a CIGI Host.

12. New DG Assignments