Should note that this is the desktop redistributable not the server
redistributable. I don't think (and this was the case in the past for me)
that you can use this in a server though INAL.
Norman
On Thu, Jan 16, 2025 at 11:33 AM Kurt Schwehr via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Fr
>From https://gdal.org/en/stable/drivers/raster/ecw.html
"Support is optional and requires linking in the libraries available from
the ECW/JP2 SDK Download page."
You must build from source and have Hexagon's binary SDK.
On Thu, Jan 16, 2025 at 8:06 AM Richard Greenwood via gdal-dev <
gdal-dev@l
Thank you Laurentiu,
“*They exist for safety reasons (so you don't modify a dataset by mistake),
not as an optimization.” *
This is what I’m looking for. 😊
All the best,
Michal Kowalczuk
W dniu czw., 16 sty 2025 o 10:11 Laurențiu Nicola via gdal-dev <
gdal-dev@lists.osgeo.org> napisał(a):
> Hi
Hi,
I strongly suspect a number of drivers are hardly used, in particular
their write/edition side
My list of candidate victims for removal (of the write side) is at
https://docs.google.com/spreadsheets/d/12yk0p8rRK4rAYO_VwXboatWkiILAjE2Cepu32lsHhM8/edit?gid=0#gid=0
. Please add your potenti
Dear Andrew,
are you a CAD user?
DXF does not support MultiPolylines (MultiLineString) natively. Lines and
MultiLines are both saved as LWPOLYLINE objects. It means that Multilines
are exploded.
Below you can find the DXF definition of 3 separate LWPOLYLINES that
originally in GIS creates a MultiP
It looks like you have to request the read-only redistributable:
https://supportsi.hexagon.com/s/article/ERDAS-ECW-JP2-SDK-Read-Only-Redistributable-Request
And I am guessing that you will need to build GDAL from source.
Rich
On Wed, Jan 15, 2025 at 11:44 PM selim sezer via gdal-dev <
gdal-dev@l
On Thu, 16 Jan 2025, Michał Kowalczuk via gdal-dev wrote:
Thank you, Jukka.
I saw this post. The main question is why the DXF driver implementation can
explode MultiPolylines and MultiPolygons (which is more complex) and
MultiPoint *not*?
As I read the DXF 2014 spec
http://images.autodesk.com/
Hi Michał,
Without knowing a lot about the underlying implementation, I would expect those
flags to make no difference in performance. They exist for safety reasons (so
you don't modify a dataset by mistake), not as an optimization.
As for the docs, that seems expected. The documentation can't
Hi,
* The main question is why...
Those who have written the DXF driver (Frank Warmerdam, Alan Thomas, Even
Rouault...) may know why but I guess that that their client did not have
multipoints in their data, or they were not willing to pay for something that
they do not need. Multipoints ar
Thank you, Jukka.
I saw this post. The main question is why the DXF driver implementation can
explode MultiPolylines and MultiPolygons (which is more complex) and
MultiPoint *not*?
Michał Kowalczuk
czw., 16 sty 2025 o 08:24 Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> napisał(a):
> Hi,
10 matches
Mail list logo
