> The libspatialite code where the failure occurs is only executed when
> spatialite is built with LOADABLE_EXTENSION undefined. Is there any
> possibility that the new gpkg code depends on this being defined?
> LOADABLE_EXTENSION does not appear anywhere in the GDAL source.
Are you trying to
Even,
That does seem to be the problem; I had already compiled the bindings using
SWIG 3.x and the make clean command wasn't clearing everything out completely.
I verified the new jar made after running the veryclean command now has the
appropriate SWIGDatasetUpcast method just like the
Hei Even,
Thanks for the incredibly quick fix. I shall test at once.
Cheers
Stefan
-Original Message-
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: 3. mai 2016 21:33
To: gdal-dev@lists.osgeo.org
Cc: Blumentrath, Stefan
Subject: Re: [gdal-dev]
Le mardi 03 mai 2016 21:06:14, Blumentrath, Stefan a écrit :
> Dear GDAL-devs,
>
> I just tried to open a Norwegian SOSI file with ogrinfo from GDAL 2.1dev
> but get: FAILURE:
> Unable to open datasource `./ADM_kommune_2018_Masoy.sos' with the following
> drivers.
>
> 'ogrinfo --formats' does
Dear GDAL-devs,
I just tried to open a Norwegian SOSI file with ogrinfo from GDAL 2.1dev but
get:
FAILURE:
Unable to open datasource `./ADM_kommune_2018_Masoy.sos' with the following
drivers.
'ogrinfo --formats' does not list the SOSI driver either. But I am sure I did
compile with
Le mardi 03 mai 2016 20:23:49, jramm a écrit :
> Hi
>
> When writing geotiffs, if I dont write blocks they will automatically be
> filled on close by the FillEmptyTiles.
> It appears that this will only fill with zeros - is it possible to make it
> fill with the no data value instead?
You can
Hi
When writing geotiffs, if I dont write blocks they will automatically be
filled on close by the FillEmptyTiles.
It appears that this will only fill with zeros - is it possible to make it
fill with the no data value instead?
This is potentially a huge time saver when processing a large, fairly
Le mardi 03 mai 2016 19:50:11, Alan Stewart a écrit :
> Even,
>
> The libspatialite code where the failure occurs is only executed when
> spatialite is built with LOADABLE_EXTENSION undefined. Is there any
> possibility that the new gpkg code depends on this being defined?
> LOADABLE_EXTENSION
On 2016-05-03 3:11 PM, Even Rouault wrote:
Le mardi 03 mai 2016 19:57:45, Jeff McKenna a écrit :
I'm also very ok with changing the default to set
H5_BUILT_AS_DYNAMIC_LIB only - I'll just edit the makefile before
building. Not an issue for me.
I'm not keen to modify things without a clear
Le mardi 03 mai 2016 19:57:45, Jeff McKenna a écrit :
> I'm also very ok with changing the default to set
> H5_BUILT_AS_DYNAMIC_LIB only - I'll just edit the makefile before
> building. Not an issue for me.
I'm not keen to modify things without a clear understanding of what is
required in which
I'm also very ok with changing the default to set
H5_BUILT_AS_DYNAMIC_LIB only - I'll just edit the makefile before
building. Not an issue for me.
Since no one is recording these notes from this long discussion in the
buildhints wiki, I'm +1 to change to this new setting in makefile.vc;
Even,
The libspatialite code where the failure occurs is only executed when
spatialite is built with LOADABLE_EXTENSION undefined. Is there any possibility
that the new gpkg code depends on this being defined? LOADABLE_EXTENSION does
not appear anywhere in the GDAL source.
Alan Stewart
Senior
On 2016-05-03 1:36 PM, Even Rouault wrote:
If you have the opportunity, it would be good if you could check if defining
both _HDF5USEDLL_ and H5_BUILT_AS_DYNAMIC_LIB doesn't affect negatively your
builds. Ideally, we'd like to have a default set of compilation flags that
works out of the box
Le mardi 03 mai 2016 18:23:47, Jeff McKenna a écrit :
> On 2016-05-03 4:54 AM, Even Rouault wrote:
> >> -EXTRAFLAGS = -I$(HDF5_DIR)\include -DWIN32 -D_HDF5USEDLL_
> >> +EXTRAFLAGS = -I$(HDF5_DIR)\include -DWIN32
> >> -DH5_BUILT_AS_DYNAMIC_LIB
> >
> > Jeff,
> >
> > does the above
On 2016-05-03 4:54 AM, Even Rouault wrote:
-EXTRAFLAGS = -I$(HDF5_DIR)\include -DWIN32 -D_HDF5USEDLL_
+EXTRAFLAGS = -I$(HDF5_DIR)\include -DWIN32
-DH5_BUILT_AS_DYNAMIC_LIB
Jeff,
does the above match your experience ? We could probably define both
_HDF5USEDLL_ and
an see thers)
I'm working on a new build for the MS4W community with the new 2015
compiler, which seems to work better managing these 4 libraries (huge
knock on wood!).
In terms of building HDF5, one of the important notes is during cmake
be sure to set "-DBUILD_SHARED_LIBS:BOOL:ON" I'm
Hello GSoC students!
I created the section about GSoC 2016
(https://trac.osgeo.org/gdal/wiki/SoCProjects) in GDAL wiki.
Please write your project texts as was done previous years and provide
them to your mentors to publish them at appropriate wiki pages.
Don't afraid some duplication the
GDALBuildOverviews() seems to works fine now, my bad. Thanks for the
responses.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Questions-about-MBTiles-write-support-GDAL-2-1-RC4-tp5263684p5264135.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
I saw the code on gdal-2.1.0\frmts\mbtiles\mbtilesdataset.cpp I want know
where a blob is written into mbtiles.
I don't see any INSERT SQL statement for inserting a tile blob
Gane
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
Le lundi 02 mai 2016 23:21:04, Ryan Grout a écrit :
> Thanks, again Christoph. You're a lifesaver.
>
> For the benefit of the gdal-dev list.
> Applying the below patch to GDAL fixed my build issues with HDF5 1.8.16
> ---
>
20 matches
Mail list logo