[gdal-dev] TOC sub-dataset retrieving when frame with same coverage share the same boundary rectangle.

[Even Rouault]

Selon Nicolas G <nicolas.g-dev at outlook.fr>:

hi

yes you have well described the behaviour of the driver. The
subdatasets match the boundary rectangles
And it is very odd to have two frames with same col row
coordinates for the same boundary rectangle.
in your case you have to directly open the nitf tile instead
of the a.toc

> Hi,
>
>
>
> I’m using GDAL to get the CADRG database sub-dataset list.
>
>
> As an example (TOC file content):
>
> - Only one boundary rectangle defined in “boundary rectangle section”,
>
> - In “frame file index section”, I have two frames covering the same
> area (same resolution, …, but different functional content),
>
> - These two frames are stored in different path but all referring to the
> same boundary rectangle.
>
>
> Then in that case, the message "Frame entry(%d,%d) for frame file index
> %d was already found." is raised by GDAL when loading the TOC file, and
> finally
> only one sub-dataset is given back to me(the first one of the TOC file) ->
> method ‘RPFTOCReadFromBuffer()‘ of Rpftocfile.cpp.
>
>
> It seems that GDAL uses boundary rectangles and frame files to build the
> sub-dataset list and if, for a same boundary rectangle, two or more frames
> with
> the same coverage belong to different path
> then only one GDAL sub-dataset is created.
>
>
> Does someone can help me and explain me how to access the data of these
> two frames files (same coverage, same boundary rectangle but different path)
> through GDAL API?
>
>
> Or is there any development on this subject?
>
>
>
> Thanks,
>
>
>
> Nicolas
>
>
>
>
>
>