Re: [gdal-dev] Logics of CPLGetXMLValue and CPLFetchBool

2017-11-15 Thread Ari Jolma
Ari Jolma kirjoitti 15.11.2017 klo 15:51: Even Rouault kirjoitti 15.11.2017 klo 13:40: On mercredi 15 novembre 2017 10:58:23 CET Ari Jolma wrote: > > Thus the return value of CPLGetXMLBoolean can't use CPLGetXMLValue if it > follows the logic of CPLFetchBool. That is true is existence an

Re: [gdal-dev] Logics of CPLGetXMLValue and CPLFetchBool

2017-11-15 Thread Ari Jolma
Even Rouault kirjoitti 15.11.2017 klo 13:40: On mercredi 15 novembre 2017 10:58:23 CET Ari Jolma wrote: > > Thus the return value of CPLGetXMLBoolean can't use CPLGetXMLValue if it > follows the logic of CPLFetchBool. That is true is existence and no denial. > Why not CPLGetXMLBoolean(n

Re: [gdal-dev] Logics of CPLGetXMLValue and CPLFetchBool

2017-11-15 Thread Even Rouault
On mercredi 15 novembre 2017 10:58:23 CET Ari Jolma wrote: > I thought it would be perhaps good to have CPLGetXMLBoolean since we > have CPLFetchBool and many of the option values needed by the new WCS > driver are boolean flags and the option values end up in the service > XML. It would twist the

[gdal-dev] Logics of CPLGetXMLValue and CPLFetchBool

2017-11-15 Thread Ari Jolma
I thought it would be perhaps good to have CPLGetXMLBoolean since we have CPLFetchBool and many of the option values needed by the new WCS driver are boolean flags and the option values end up in the service XML. It would twist the brain a bit less if one could simply use CPLGetXMLBoolean. Th