Hi,
On windows, using visual studio (2008 and 2012), I could compile both 32
bits and 64 bits, but only the 32 bits version actually worked.
I haven't tried to figure out why the 64 bits version didn't work, 32 bits
was good enough for me.
Hope this is an option for you as well,
Jan
On Fri, Jan
If the spatial resulution is fine for your problem, then as Tyler
suggested, you can use gdallocationinfo [1] to get the pixel value at
Long,Lat location.
If you think you need to downscale your data to your needs, you can first
built a vrt (virtual dataset) with gdal's gdalbuildvrt [2] and -tr
On 24. jan. 2013 20:43, Even Rouault wrote:
Did you try to do your suggestion at hand to actually check that your idea
leads to the expected result ? This is basically a matter of running :
1) gdaltransform -s_srs EPSG:4326 -t_srs +proj=stere +lat_0=90 +lon_0=0 on
the coordinates of the GCPs of
my idea is to convert a MULTIPOINT shapefile to a POINT shapefile, but
how
to set SHPT=POINT?
I would have a try with ogr2ogr -explodecollections
-explodecollections did the conversion from MULTIPOINT to POINT shapefile.
thanks!
-
best regards
Helmut
--
View this message in
Thanks for the suggestion Jan.
I tried to compile the 32-bit libgdal with the 32bit FileGDB_API but
still throws the same error...
Is it possible that the osc tool is looking inside it's build
environment at /tmp or /usr/tmp instead of my local user files at
/usr/lib64?
I might take this problem
I've tested compiling the 64bit gdal-1.9.2 from the tar.gz source file:
./configure --with-fgdb=/usr/lib64/FileGDB_API
And it completes successfully where I can see the FileGDB driver
read/write format in the output of ogrinfo --formats.
There must be something in this SPEC file that is causing
My buildlog from osc build openSUSE_12.2 x86_64 libgdal.spec --clean if
it helps.
http://paste.opensuse.org/view/raw/e119c82d
On Fri, Jan 25, 2013 at 1:54 PM, Donovan Cameron sault@gmail.comwrote:
I've tested compiling the 64bit gdal-1.9.2 from the tar.gz source file:
./configure
Hi Donovan,
This approach will not work.
OpenBuildService (OBS) is a system to automate builds and create
packages, and we are using it to
http://openbuildservice.org/
openSUSE Build Service is a deployment of OBS that we are using to
produce openSUSE distribution
When I check-out the libgdal package and I run the osc build command, isn't
this building locally and not trying to *upload *any binaries? I thought
this chroot was in my local machine and only making changes there?
I was trying to keep this all a local build by following the instructions
at:
Hi Donovan,
comments inline:
On 01/26/2013 01:34 AM, Donovan Cameron wrote:
When I check-out the libgdal package and I run the osc build command, isn't
this building locally and not trying to *upload *any binaries? I thought
this chroot was in my local machine and only making changes there?
10 matches
Mail list logo