Frank,
While I wasn't able to find the OBJL=22001 and OBJL=22010 objects formally
defined anywhere, I was able to back out their meaning using SeeMyEnc and
some debugging in GDAL. Basically I found that 22001 is an "Annotation"
point and 22010 is a "Traffic Line".
I added the following 2 lines a
Jukka Rahkonen wrote:
Hi,
Ogr2ogr seems to create field named ogc_fid with PostGIS driver but ogr_fid with
Oracle OCI driver. Is this intentional? Probably not a big trouble for
anybody.
Jukka,
I believe by the time I was implementing the Oracle driver I realized naming
the fid "ogc_fid wa
Hi,
Ogr2ogr seems to create field named ogc_fid with PostGIS driver but ogr_fid with
Oracle OCI driver. Is this intentional? Probably not a big trouble for
anybody.
-Jukka Rahkonen-
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osg
A further test revealed that the PROJ.4 DLL was missing on my system.
After downloading the current version included in OSGeo4W, and putting
it in the gdalwin32-1.6\bin directory, I now get the correct results.
Thanks a lot, Howard!
Klaus
Original-Nachricht
Betreff: Re: [gda
OSGeo4W should have a suitable proj.dll
Please reply to the list so others may benefit from the exchange.
Howard
On Oct 6, 2009, at 2:23 PM, Klaus Noekel wrote:
Hi Howard,
thanks for checking this so quickly. It still fails on my PC, and
the env variable definitely point to the correct loc
On Oct 6, 2009, at 2:10 PM, Klaus Noekel wrote:
Hi,
I have just installed GDAL 1.6.1.win32-py2.6 on a Win XP system and
set
up the GDAL directory properly (bin directory in PATH, env variable
points to data).
Scripts for coordinate transformation like that below do not crash,
but
just se
Hi,
I have just installed GDAL 1.6.1.win32-py2.6 on a Win XP system and set
up the GDAL directory properly (bin directory in PATH, env variable
points to data).
Scripts for coordinate transformation like that below do not crash, but
just seem not to do anything, i.e. the data remain unchanged in
Hi Micheal,
rgb2pct is a batch file, so when used inside another batch it must be
"called" in order for control to return to the initiator:
call rgb2pct v:\historic_topos\rects\w\arnold-pond-w.tif
v:\historic_topos\8bits\w\arnold-pond-w.tif
call rgb2pct v:\historic_topos\rects\w\attean-w.
I'm by no way a vector expert, but for this kind of stuff I'd go the
postgis way, at least for intermediate storage.
I've thought of this but have shied away from it because of the overhead
of installing postgis etc. just to get started. Time to get over my
shyness perhaps :)
cheers,
matt
Hi,
At least in my understanding the gdaldem manual's description for the
Roughness is misleading. It states
"Roughness is the the largest inter-cell difference of a central pixel
and its surrounding cell, as defined in Wilson et al (2007, Marine
Geodesy 30:3-35)."
From that I understood t
10 matches
Mail list logo