search

iho-ohi / S-101-Test-Datasets

A repository of S-101 test datasets which make available for development phases and they will be migrated to the Registry later.
22 stars 6 forks source link

maxDisplayScale in 10100AA_OVRVU.000 #80

Open kusala9 opened 7 months ago

kusala9 commented 7 months ago

CSCL of AA2OVRVU.000 is 350k but the converted cell appears to be 180k. Can we check and alter the attributes if necessary. S-64 specifically refers to 350k

plebihan29n commented 6 months ago

S57 Compilation Scale of AA2OVRVU.000 is 350k . In the converted S-101 data coverage, the maximum-minimum display scale attributes have been set respectively 180k-700k . For the moment this is a volunteer conversion of CSCL and this conversion has been adopted for all datasets

This takes into account the current principle of overscale indication :

cf 4.6 Display scale range ... "When the MSVS is larger than the value indicated by maximum display scale, the overscale indication, in the form of an overscale factor and pattern covering the area that is overscale, must be shown. When at own ship’s position a dataset with a larger maximum display scale than the MSVS is available, an indication is required and must be shown on the same screen as the chart display." ...

In this particular case the over scale indication will appear at 175k in S-57-S-52 and will appear at 180k in S-101.

Before to change, Perhaps we have to wait the definitive and common decision around "maximum display scale " role ?

But nevertheless there is a correction/improvement that can be done at once : In this particular case of "navigation hazards test datasets" , we have two datasets at different scales I can make "minimum display scale attributes settings" in order to avoid gap between the two datasets. current settings : 10100AA_NAVHZ (45k-90k) => 10100AA_OVRVU (180k-700k) proposal settings : 10100AA_NAVHZ (45k-180k) => 10100AA_OVRVU (180k-700k)

kusala9 commented 6 months ago

I just noticed (when testing in the NIWC viewer that DBASE has min/max display scale 22-12k which is not very usable on the viewer as it disappears below min scale. A good guide to setting the minimumDisplayScale may be to use the scaleMinimum values in the cell. DBASE uses 180k and 200k so maybe set the minimumdisplayScale to 200k? Similarly for Standard and Other both of which have scaleMinimum vlaues of 1,500,000. They have no overlapping cells so I think this would be ok. It would be good to set the DBASE cell to something more usable in the interim though - I agree we may have to think again after the S-101PT after the discussion on optimumDisplayScale.... One of the issues is that S-64 (and S-164) will use specific scale settings and the display for the screenshots is partly dependent on those settings so if we change them we have to change the manual (and possibly the test).