help-DB

-D(d)B/
- -d execution of the commandline is least verbose
- -D execution of the commandline is most verbose

.../tarawa-subset/...
- database =name of PCIDSK database: 4SM shall add the suffix ".pix"

.../24_1_0_0/... database structure : number of channels
- U8 =number of 8U channels
  - let N=number of spectral bands: make U8=4*N+15
- S16 =number of 16S channels:
  - make S16=1 for Depth in centimeters
  - if seatruth is a DTM in centimeters, make S16=3
- U16 =number of 16U channels, to store 16U raw data
  - for 16 bits images like Landsat 8, Ikonos, QuickBird, Hyperspectral, make U16=N
- R32 =number of 32R channels
  - make R32=0 as 4SM does not use real 32 bits channels
- NOTE: channels must be organized in that order in PCI database.pix
- NOTE: PCI database.pix may be either of BAND or FILE interleaving (CIM syntax)

.../3_1/..................................bands
- bands...................number of raw_data_bands
  - a Landsat TM image has 4 bands: Blue, Green, Red, and NIR
- FirstChRaw..........first channel raw data
  - for U8 data, this is channel_1
  - for U16 data, this is channel_U8+U16+1

.../R650_L600/..................image size
- nbRow................number of rows/columns in image
- nbLin..................number of lines in image

.../714.5_162.54/..............UTM coordinates of UL corner of UL pixel:
- UTM origin of the database: this is the UL corner of the UL pixel
- West and North in kilometers (unlike in OpenEV!!!)

Not georeferenced

suppose no georeferencing details are available
you would still have to give something, like
- -DB/PCI/heronETM/31_1_0_0/4_1/R1647_L1235/0.0_75.150
- -Mis/USF/GBR/Landsat/ETM/USF/UTM_16_008/.030_.030/22_NOV_1990
- for an image with pixel size 30 m and 2505 lines

Pixel size is provided in the -MIS... argument
You may use -DB (instead of -dB) to display database specifics on screen
Minimum channel structure for a N_bands image is
- U8=N+15+N+N+N...
  - Then optional S16=1 (or 3 if a DTM is available)
  - Then, if any, U16 channels for N U16 raw data like Landsat 8, Ikonos or CASI imagery?

About the tarawa-subset.pix database structure

-DB/tarawa-subset/27_1S_0s_0s/3_1/R650_L600/718.069_169.231

27 vs 24?
- look at the channel descriptor tarawa-subset.mcd textfile
- there is no fixed maximum number of channels
- if you need more for any reason, just increase their number in -D/... argument
  - some of them shall be left unused, it does not hurt though
  - like channel 10 for storing bottom typing: does not make sense for a SPOT 1 image which does not have a blue band
  - like channels 20 and 21
- or you can use them to contain a copy of some other channel or result
  - a handy aspect of the FILE interleaving
So we have 27 U8 channels, but S16 is different, why is 1S?
- channel_28:
  - is where you store estimated depth in centimeters:
  - requires one S16 channel_28
- channel_29: if you have a DTM, this is where you store it
  - requires one more S16 channel_29
- channel_30: is where you store the difference
  - requires one more S16 channel_30
- for this you change for:
  - -DB/tarawa-subset/27_3S_0s_0s/3_1/R650_L600/718.069_169.231
For a Landsat 8 OLIP image like at SanLorenzoChannel:
- -DB/mbOLI_20160601/40_3S_7S_0s/7_44/R4644_L3260/568.050_6140.220
- 40.....U8
- 3.......S10 for ZRecorded=ZDTM, ZComputed=Z4SM, and ZR-ZC
- 7.......U16 for copy of raw data
- 0.......R32
- 7 bands: UB, B, G, Pan, R, NIR, SWIR are used
- FirstChRaw is channel_40+3+1 =channel_44