%TEMP% is the Windows environment variable pointing to the temp directory. For
Unix/linux:
,--%<---
# set variable
export GDAL_PAM_PROXY_DIR=/tmp
# confirm
echo $GDAL_PAM_PROXY_DIR
/tmp
`--->%--
Luke
From: Nikos Alexandris [mailto:n...@nikosalexandris.net]
Sent: Wednesday, 31 July 2
Luke:
%TEMP% is the Windows environment variable pointing to the temp directory.
For Unix/linux:
,--%<---
# set variable
export GDAL_PAM_PROXY_DIR=/tmp
# confirm
echo $GDAL_PAM_PROXY_DIR
/tmp
`--->%--
So much to my bash knowledge... :D
It works fine, thank you very much!
Nikos
[rest d
On Wed, Jul 31, 2013 at 2:35 PM, Even Rouault
wrote:
>
>
> ok, that one is actually known. It is also a defect of the FileGDB SDK. See
> http://trac.osgeo.org/gdal/ticket/4578 and
> http://trac.osgeo.org/gdal/ticket/4224
>
>
Thanks, Even. I should have looked through the Trac tickets myself bef
Selon Carl Godkin :
> On Wed, Jul 31, 2013 at 9:24 AM, xavier lhomme
> wrote:
>
> > Raster Dataset and Mosaic Dataset are not supported :
> > See :
> >
>
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-170.pdf
> >
> >
>
> Thanks for the tip, Xavier. The .gdb files I'
On Wed, Jul 31, 2013 at 9:24 AM, xavier lhomme
wrote:
> Raster Dataset and Mosaic Dataset are not supported :
> See :
> http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-170.pdf
>
>
Thanks for the tip, Xavier. The .gdb files I've got have more than just
rasters and mo
Selon Xian Chen :
Hi Xian,
If you want to debug that, you can have a look at the revelant code in
ogr/ogrsf_frmts/dxf/ogrdxf_hatch.cpp around line 250 and below, and in
ogr/ogrsf_frmts/dwg/ogrdwg_hatch.cpp around line 190 and below.
Best regards,
Even
> Hi all,
>
> I encountered an error when
Raster Dataset and Mosaic Dataset are not supported :
See :
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-170.pdf
Best Regards
2013/7/31 Carl Godkin
>
> Thanks, Even. You give me hope that I wasn't barking up the completely
> wrong tree. I will attempt to debug
+1 Howard
On Mon, Jul 29, 2013 at 10:49 AM, Frank Warmerdam wrote:
> +1 Frank
> On Jul 29, 2013 4:14 AM, "Even Rouault"
> wrote:
>
>> Hi,
>>
>> Motion: I move to adopt RFC 41 : Support for multiple geometry fields in
>> OGR
>>
>> http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fiel
lpinner wrote:
> A workaround to your 2nd question is to set the GDAL_PAM_PROXY_DIR
> environment variable, either permanently or on the commandline before you
> call gdalinfo.
>
> set GDAL_PAM_PROXY_DIR=%TEMP%
> gdalinfo -stats some.ntf
Thank you Luke.
1st, that would be
,--%<---
# set variab
On Wednesday 31 of July 2013 11:55:27 Nikos Alexandris wrote:
> Yet another NITF related "problem". An ntf file contains (no SUBDATASETS)
>
> gdalinfo -nogcp -nomd -mm M1BS.ntf
>
> ,--%<---
> Band 1 Block=1024x1024 Type=UInt16, ColorInterp=Blue
> Computed Min/Max=183.000,2047.000
> Overview
Yet another NITF related "problem". An ntf file contains (no SUBDATASETS)
gdalinfo -nogcp -nomd -mm M1BS.ntf
,--%<---
Band 1 Block=1024x1024 Type=UInt16, ColorInterp=Blue
Computed Min/Max=183.000,2047.000
Overviews: 3438x3448, 1719x1724, 859x862, 429x431, 214x215
Overviews: arbitrary
Band
Hi all,
I encountered an error when reading the attached dwg file using OGR. The
last part is supposed to be a clockwise big circle arc, but is translated
into a counterclockwise circle arc.
I then converted the file into dxf and still have the error. Can anyone
please help me out?
Best regards
12 matches
Mail list logo