On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
ok, so the exception occurs in the embedded copy of tinyxml inside the ECW
SDK ?
You likely need to apply those community patches to your libecwjp2 3.3
sources:
https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch
First of all, the dwg format is only available in gdal if you buy ODA SDK
which is very expensive. To omit this you can switch to DXF format which is
built-in by default in gdal.
https://www.opendesign.com/pricing
https://gdal.org/drivers/vector/dxf.html
Regards,
Michal
W dniu wt., 25.06.2024 o
https://gdal.org/drivers/vector/dwg.html says:
> DWG files are considered to have no georeferencing information through OGR
>From https://gdal.org/programs/ogr2ogr.html, you will need to specify the
spatial reference system / projection with "-s_srs"
-Kurt
On Tue, Jun 25, 2024 at 12:55 PM Ashly
Hello GDAL Devs,
I am new to using GDAL, and I just don't know enough about it yet. I am
working with thousands of CAD files (DWG) to extract a project boundary
line then export it out as a KML. I would love to automate this process.
Does GDAL have the capability to work with DWG files? Has anyon
ok, so the exception occurs in the embedded copy of tinyxml inside the
ECW SDK ?
You likely need to apply those community patches to your libecwjp2 3.3
sources:
https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch
Le 25/06/2024 à 18:42, Andrew C Aitchison a écrit :
On
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Le 25/06/2024 à 16:52, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault wrote:
Le 25/06/2024 à 16:25, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Can you run "gdb autotest/cpp/testclo
Le 25/06/2024 à 16:52, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault wrote:
Le 25/06/2024 à 16:25, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and
when it crashed "bt" so
On Tue, 25 Jun 2024, Even Rouault wrote:
Le 25/06/2024 à 16:25, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and when it
crashed "bt" so we have a backtrace of where it crashes (all of that
Le 25/06/2024 à 16:25, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and
when it crashed "bt" so we have a backtrace of where it crashes (all
of that after running "source ../scripts/setdevenv
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and when it
crashed "bt" so we have a backtrace of where it crashes (all of that after
running "source ../scripts/setdevenv.sh")
It doesn't crash:
(gdb) run
Starting program:
Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and when
it crashed "bt" so we have a backtrace of where it crashes (all of that
after running "source ../scripts/setdevenv.sh")
Le 25/06/2024 à 15:14, Andrew C Aitchison via gdal-dev a écrit :
This is not a new failure, so thre
This is not a new failure, so thre is no need for this to hold up 3.9.1.
System: Ubuntu 24-04/Noble on Intel x86-64.
# ctest --output-on-failure
8< 8< 8< 8< 8< 8< 8<
28/51 Test #28: test-closed-on-destroy-DM ***Failed0.19 sec
[==] R
12 matches
Mail list logo
