Data Updates Required for S-164

[kusala9]

data updates required.

• S-102/ S-104
• NavWarn elements
• data which spans cells, light sectors and S-1233
• complex pick reports (if and when)
• Data which is in one feature catalogue but not the other.
• better multiple version demonstrations
• multiple data coverage which tests loading strategy

[kusala9]

• "significantly complex LUA portrayal"
• Updates to Settigns to get it inline with new PC
• Chart 1 (of course)

[kusala9]

• new features created by S-65. Should all be in data somewhere?

[kusala9]

• all the different possiblities of 8211 curve updating

[kusala9]

• data which matches all the real number formats and is also used in complex portrayal.

[kusala9]

• large 8211 records (GH issue in S-164)
• DAta at the edges, to check data loading strategies.

[kusala9]

• updating S-128 when updating datasets so you're not putting the whole catalogue in every exchnage set.
• every different type of support file.
• every different way of doing cancellations
• every different way of updating support files (in fact need specific support file test)
• optimumDisplayScale tests, overlapping display scales?
• check 102/104 is rejected if vertical datums are not compiled right.
• Provision for other Chart 1s?
• S-124 in force bulletin
• S-124 with area of influence.
• S-124 with each different means of cancellation
• S-124 with different catagroeis for testing filters.
• interoperabilityIdentifier + Test.
• fileLocator
• different image types.
• updates to NavHaz following issue and spreadsheet.

[kusala9]

Gridded Data Tests (from my notes)

• Vewing 102/104/111 in a single location. Multiple cells of each with different resolutions
• rejection of cinomcpatible data + selection from overlapping?
• Something to do with ENC scales?
• multiple vertical datums (according to what methodology they choose)
• USSC two different values
• WLA with interrogation of adjusted ENC values
• Checking the message is in place
• Time checks, in range, out of range
• Plan over the gridded region.
• Also need a 102/104 cell overlaying navhaz, to test contour and alarm/indication functions. This should be next to navhaz with the route over it and the adjustment causes alerts.

[kusala9]

• updates to navhaz already identified.

[kusala9]

Scenarios for Support file management.

• Install two datasets with a common support file
• Change the name of the support file in one dataset and deliver the other support file
• Install another dataset which shares the first support file
• Update the content of the support file (without a dataset update)
• Delete the first dataset
• Cancel and Replace the third dataset (without its support file)
• Terminate the support file

[kusala9]

need to do a tree of all resource pursposes and revision status and make sure we have all combinations.

[kusala9]

• add interoperabilityIdentifier to datasets to make sure there is interoperability between features. This should be between S-124 and S-129 and use a generic MRN structure.