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
> I've turned that as an error:
Thanks, much appreciated -that will probably save at least 10 people from
sitting at a coffee shop at 3am, recompiling anxiously for the 100th time,
pulling out what is left of their hair, subsisting on stale pizza and
wondering why they chose a career in programmin
As I have been unable to solve my strange proj4 related issues as per
http://osgeo-org.1560.x6.nabble.com/Failed-to-initialize-PROJ-4-with-quot-quot-td5338323.html
I wonder if this is at all related to my issues and why changing proj4
versions makes no difference
Is --without-fgdb the correct
> To save others from this hellish debugging process, it might be worth
> either checking for the FGDB libraries and throwing an error if GDAL is
> configured without --wtih-static-proj4=location or setting that option by
> default.
./configure should already output a warning about that situation
Hi Even,
I have resolved with your hints.
Thx for help.
Andrea.
2017-11-13 12:23 GMT+01:00 Even Rouault :
> On lundi 13 novembre 2017 09:00:38 CET Andrea Peri wrote:
>
> > Hi,
>
> > I have a trouble with my qgis-server.
>
> >
>
> > I have a debian stretch version 64bit where the libpng is at
I ran into an issue a few days ago where an ogr_fdw foreign data wrapper in
postgis was throwing
[XX000] ERROR: AddToPROJ4SRSCache: could not parse proj4 string '+proj=lcc
+lat_1=31.88 +lat_2=30.116667 +lat_0=29.67
+lon_0=-100.3 +x_0=69.9998983998 +y
+1
Daniel
On 2017-11-15 10:07 AM, Even Rouault wrote:
Hi,
I move to adopt RFC 70: Guessing output format from output file name
extension
https://trac.osgeo.org/gdal/wiki/rfc70_output_format_guess
Starting with my +1,
Best regards,
Even
--
Spatialys - Geospatial professional services
+1
Best regards,
Tamas
2017-11-15 16:07 GMT+01:00 Even Rouault :
> Hi,
>
>
>
> I move to adopt RFC 70: Guessing output format from output file name
> extension
>
>
>
> https://trac.osgeo.org/gdal/wiki/rfc70_output_format_guess
>
>
>
> Starting with my +1,
>
>
>
> Best regards,
>
>
>
> Even
>
> I wouldn't expect that effect to be as strong as you observed, but indeed
> there are technical
> grounds for your findings. When a tile is partial, ie for the right most or
> bottom most tiles
> when tile size is not a multiple of the tile dimension, the TIFF format still
> impose that the
Hi,
Just to inform you that I've fixed recently in trunk a long standing issue with
command line
utilities on Windows with non-ascii characters.
Previously we used the standard main() entry point, which got the arguments in
the
current codepage (which was already a limitation in case you want
Jacob Adams wrote
> I'd like to check my understanding of the impact of the tile size on
> JPEG-compressed geotiffs.
>
> I've been getting dark bands 4 or 5 pixels wide on the bottom and right
> edges of the image when manually creating large image tiles from a
> collection of smaller tiles. I'm
Even Rouault-2 wrote
> Hi,
>
> I move to adopt RFC 70: Guessing output format from output file name
> extension
>
> https://trac.osgeo.org/gdal/wiki/rfc70_output_format_guess
>
> Starting with my +1,
+1
-Jukka Rahkonen-
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f374209
On mardi 14 novembre 2017 13:16:40 CET Jacob Adams wrote:
> I'd like to check my understanding of the impact of the tile size on
> JPEG-compressed geotiffs.
>
> I've been getting dark bands 4 or 5 pixels wide on the bottom and right
> edges of the image when manually creating large image tiles fro
Hi,
I move to adopt RFC 70: Guessing output format from output file name
extension
https://trac.osgeo.org/gdal/wiki/rfc70_output_format_guess
Starting with my +1,
Best regards,
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
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
On mardi 14 novembre 2017 14:20:58 CET Kurt Schwehr wrote:
> Hi Even,
>
> I have some follow up questions on Cloud Optimized GeoTIFFs:
The main constraint of C.O.G is that all the IFD definitions are at the
beginning of the file, to
avoid seeking at various points in it. Other parameters are pr
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
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
18 matches
Mail list logo
