Changes between Version 1 and Version 2 of rfc36_open_by_drivername


Ignore:
Timestamp:
Oct 3, 2011, 11:56:33 AM (13 years ago)
Author:
ilucena
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rfc36_open_by_drivername

    v1 v2  
    4949== Issues ==
    5050
    51 But it is important to note that some drivers already accept a "driver-name:" entry and knows how to deal with it directly.
     51But it is important to note that some drivers already accept a "driver-name:" entry and knows how to deal with it directly. In that case if the driver name entered is exactly the name of a driver then it will take advantage of the proposed mechanism avoiding the probing mechanism. Therefor entries like "GTIFF_RAW:xxx", "GEOR:xxx", "JPEG_SUBFILE:xxx" will fail to be loaded direct by any driver, since they are not real drivers names. The control will be passed to the driver probing loop that will eventually open the file.
    5252
    53 In that case if the driver name entered is exactly the name of a driver then it will take advantage of the proposed mechanism avoiding the probing mechanism, ex.:
    54 
    55 {{{
    56 gdalinfo georaster:mike/bear@dbg,arch,img,id=123
    57 }}}
    58 
    59 So entries like "GTIFF_RAW:", "GEOR:", "JPEG_SUBFILE:" will fail to be loaded direct by any driver, since they are not real drivers names, and in that case the datasets will be opened by the existing driver probing mechanism.
    60