gmwg - 2. march 2005 brian parish aml specifications manager ukho brian parish aml specifications...

GMWG - 2. March 200GMWG - 2. March 20055

Brian ParishAML Specifications Manager

UKHO

Brian ParishAML Specifications Manager

UKHO


v2.0 Product Specificationsv2.0 Product Specifications

Strategic intentStrategic intent– Version 2.0 has not been constrained to be Version 2.0 has not been constrained to be

backwardly compatible with version 1.0.backwardly compatible with version 1.0.– Require the capability to support the Require the capability to support the

production of data conformant to both production of data conformant to both version 1.0 and version 2.0 of the PS version 1.0 and version 2.0 of the PS

– Require the capability to ingest AML data Require the capability to ingest AML data conformant to both version 1.0 and version conformant to both version 1.0 and version 2.0 of the PS 2.0 of the PS

– Initial Implementation strategy for version Initial Implementation strategy for version 2.0 defined at GMWG-1 technical day 2.0 defined at GMWG-1 technical day


v2.0 Implementation Strategyv2.0 Implementation Strategy

End of 2004End of 2004– Production Software upgrade by patch Production Software upgrade by patch – Ability to convert between v1 & v2Ability to convert between v1 & v2

End of March 2005End of March 2005– v2.0 test data production planned by UKHOv2.0 test data production planned by UKHO

April 2005April 2005– Receiving systems become v2.0 capable by stages Receiving systems become v2.0 capable by stages

over a much longer periodover a much longer period Mid 2005Mid 2005

– Data producers deliver both versions as requiredData producers deliver both versions as required– Dual fuel delivery required for some timeDual fuel delivery required for some time– Dual fuel updating requiredDual fuel updating required

Strategy review planned for GMWG-2 technical Strategy review planned for GMWG-2 technical dayday


DiscussionDiscussion


ESB/IWC: SedimentESB/IWC: Sediment

Sediment modelling in AML ESB is Sediment modelling in AML ESB is inadequate for some sonar systems inadequate for some sonar systems Requirement for high resolution gridded Requirement for high resolution gridded

sediment data (Geo-acoustic parameters) sediment data (Geo-acoustic parameters) fits within IWC (NetCDF)fits within IWC (NetCDF)

Surface sediments may be regarded as a Surface sediments may be regarded as a continuation of the water column for some sonar continuation of the water column for some sonar systemssystems

Requirement for lower resolution vector Requirement for lower resolution vector data in ESB remainsdata in ESB remains


Integrated Water ColumnIntegrated Water Column

Current situationCurrent situation– Proposed changes from GMWG-1 includedProposed changes from GMWG-1 included

Multiple profiles (France)Multiple profiles (France)– New requirement for high resolution, New requirement for high resolution,

gridded, sediment data includedgridded, sediment data included– Final version phase-1 published on AML Final version phase-1 published on AML

website for GMWG approval (Jan 2005)website for GMWG approval (Jan 2005)– GMWG approval by silence procedure GMWG approval by silence procedure

scheduled at end of Feb 2005scheduled at end of Feb 2005 Silence broken (MILOC) discussion continuesSilence broken (MILOC) discussion continues Scheduled review by MILOC in 2005Scheduled review by MILOC in 2005

– NetCDF annex in prep (July 2005)NetCDF annex in prep (July 2005)


Network Model BathymetryNetwork Model Bathymetry

Current situationCurrent situation– First draft Product Specification dated First draft Product Specification dated

Oct 2004 defines a gridded approachOct 2004 defines a gridded approach– Sample data available in ASCII and Sample data available in ASCII and

xyz formatsxyz formats– NetCDF annex is also possibleNetCDF annex is also possible– Further work requiredFurther work required– DBDBv is an alternative option being DBDBv is an alternative option being

investigatedinvestigated


VPF annex B (GMWG-1)VPF annex B (GMWG-1)

VPF annexes are required for v2.0 onlyVPF annexes are required for v2.0 only Action 0122 required development by Action 0122 required development by

UKHO & US NGA of operational annex UKHO & US NGA of operational annex Bs for MFF and one other (CLB) by Bs for MFF and one other (CLB) by GMWG-2GMWG-2

Technical experts from UKHO & NGA met Technical experts from UKHO & NGA met in Washington DC last week.in Washington DC last week.

Good progress was made (next slide)Good progress was made (next slide)

Final test dependent on v2.0 test dataFinal test dependent on v2.0 test data


VPF annex BVPF annex B

Requirement for VPF annexes should be Requirement for VPF annexes should be reviewedreviewed– The higher level requirement is to support The higher level requirement is to support

InteroperabilityInteroperability– Perhaps VPF annexes are no longer the most Perhaps VPF annexes are no longer the most

efficient solutionefficient solution Dependency on HIHWG means we could be Dependency on HIHWG means we could be

ready for database to database exchange of ready for database to database exchange of data before we have fully operational VPF data before we have fully operational VPF annexesannexes

UK & US tasked by GMWG-2 to consider UK & US tasked by GMWG-2 to consider alternative options alternative options


AML content

Amphibious Air Ops Anti-SubmarineStandardSymbolSets

REP

Discipline specific symbologyDiscipline specific symbology


AML content


REP


AML default symbology


AML content


REP


AML default symbology

Command Support

Mine Countermeasures

TDAs


REP


MFD Met TopoAFD Dynamic

Who is looking at this?

The REP may be a backdrop for Display of Tactical Information


Tactical symbologyTactical symbology


Gulf ESB SedimentGulf ESB Sediment


SymbologySymbology

Current activityCurrent activity– Develop AML Symbology Guidance (UKHO)Develop AML Symbology Guidance (UKHO)

Identify all relevant symbol sets/standardsIdentify all relevant symbol sets/standards Review and amend AML “Default Symbology”Review and amend AML “Default Symbology”

– Define symbology/portrayal requirements Define symbology/portrayal requirements in support of the REP and request support in support of the REP and request support from DGIWG to develop a solutionfrom DGIWG to develop a solution


Atmospheric & Meteorological Atmospheric & Meteorological ClimatologyClimatology

Current SituationCurrent Situation– Final version 1.0 of PS produced (3Final version 1.0 of PS produced (3rdrd Nov 2004). Nov 2004).– Copyright & release statements agreed.Copyright & release statements agreed.– Data unchanged from v0.9.Data unchanged from v0.9.– CDs containing Product Specification and data CDs containing Product Specification and data

produced by UK Met Office and distributed by produced by UK Met Office and distributed by UKHO January 2005UKHO January 2005

– Specification placed on AML website Jan 2005Specification placed on AML website Jan 2005– Viewing system requiredViewing system required


Implementation issuesImplementation issues NATO 3 letter country codesNATO 3 letter country codes

– AML specifies v6 of STANAG 1059AML specifies v6 of STANAG 1059– Current v8 of 1059 changed to ISO 3166 3 letter codesCurrent v8 of 1059 changed to ISO 3166 3 letter codes– Main impact on file naming conventionMain impact on file naming convention

Production SpecificationsProduction Specifications– Impact of re-allocating characters in filenamesImpact of re-allocating characters in filenames– Chart-like titlesChart-like titles

Long term via S-57 v4.0Long term via S-57 v4.0 Short term via dataset header comment fieldShort term via dataset header comment field Adopt a naming conventionAdopt a naming convention Viewing systems will need upgradingViewing systems will need upgrading Link viewing system upgrade to v2.0Link viewing system upgrade to v2.0 Place chart-like titles in v2.0 test dataPlace chart-like titles in v2.0 test data


Action 0228Action 0228 DGIWG are requested to develop a single DGIWG are requested to develop a single

homogenous reference symbology in support homogenous reference symbology in support of the NATO Recognised Environmental of the NATO Recognised Environmental Picture.Picture.– Symbology is required to support alternative Symbology is required to support alternative

representations dependent on scale, attribution, user representations dependent on scale, attribution, user profile & display mediaprofile & display media

Display media includes systems with a wide variety of Display media includes systems with a wide variety of display capabilities as well as hardcopydisplay capabilities as well as hardcopy

– Symbology is to be informed by but not constrained Symbology is to be informed by but not constrained by existing standards wherever possible by existing standards wherever possible

– Symbology to be developed following the Symbology to be developed following the conventions of the Open GIS Consortiumconventions of the Open GIS Consortium

gmwg - 2. march 2005 brian parish aml specifications manager ukho brian parish aml specifications...

Documents

gmwg approval

test data slide

vpf annex b gmwg

discussion slide

implementation slide

vpf annex b n requirement

v1 v2 n end

aml data conformant