Ok, thanks.
-- Oyvind
On Fri, May 27, 2011 at 9:10 PM, Kirk McKelvey wrote:
> Sorry Oyvind, somehow I missed your note about it being MG2.
>
>
>
> I looked into this yesterday and it is indeed a difference in the v8 DSDK.
> Image properties that are available through the API (such as the nodata
HI Frank,
thanks for your help, I did as per your reply but I still get the same error
message:
ERROR 4: Unable to open EPSG support file gcs.csv.
Try setting the GDAL_DATA environment variable to point to the
directory containing EPSG csv files.
Failed to process SRS definition: EPSG:4326
--
On 11-05-31 05:51 PM, kavinmehta wrote:
Thanks Frank. Would you know how to do it? i.e. what command to use to
convert a shape file from (EPSG 2229) to (EPSG 4326). I am having a hard
time doing it thru ogr2ogr however i can easily do this in FME Desktop tool
which uses ogr2ogr internally.
Kavi
Thanks Frank. Would you know how to do it? i.e. what command to use to
convert a shape file from (EPSG 2229) to (EPSG 4326). I am having a hard
time doing it thru ogr2ogr however i can easily do this in FME Desktop tool
which uses ogr2ogr internally.
Thanks,
kavin Mehta.
--
View this message in c
On 11-05-31 04:06 PM, kavinmehta wrote:
Thanks Jean-Claude.
I ran the following command:
ogr2ogr -f "ESRI Shapefile" -overwrite "C:/mapdata/ABC.shp"
"C:/mapdata/ABC.shp" -T_SRS EPSG:4326
and got similar error:
ERROR 4: Unable to open EPSG support file gcs.csv.
Try setting the GDAL_DATA envi
Yes, the magic of the configuration option... that makes much sense.
So by default we will emit simple layer names, but we can be
configured to emit qualified names.
On Tue, May 31, 2011 at 1:23 PM, Even Rouault
wrote:
> Le mardi 31 mai 2011 18:43:15, Paul Ramsey a écrit :
>> This is why I'm look
Le mardi 31 mai 2011 18:43:15, Paul Ramsey a écrit :
> This is why I'm looking for guidance from the OGR experts... what
> layer name styles work best for interoperation? If I emit schema.table
> layers on read, will apps be happy or sad?
Not having followed the whole discussion and not sure to re
Thanks Jean-Claude.
I ran the following command:
>ogr2ogr -f "ESRI Shapefile" -overwrite "C:/mapdata/ABC.shp"
"C:/mapdata/ABC.shp" -T_SRS EPSG:4326
and got similar error:
ERROR 4: Unable to open EPSG support file gcs.csv.
Try setting the GDAL_DATA environment variable to point to the
directory
On 05/31/11 21:23, kavinmehta wrote:
Hi,
I would like to convert a shape file from EPSG 2229 to EPSG 4326 but am not
too sure how to do this using gdaltransform and running it from the command
line?
gdaltransform -s_srs "c:\xyz\oldfile.shp" -t_srs "c:\xyz\newfile.shp"
but it did not work.
H
Hi,
I would like to convert a shape file from EPSG 2229 to EPSG 4326 but am not
too sure how to do this using gdaltransform and running it from the command
line?
I tried looking at the manual and ran as per instructions, however it ended
up with a blank file. here is the i/p file details:
PROJCS[
Well, I'm no expert!! As far as applications go, the few I use *had* problems
with schemas other than public, but I think this has been worked out for some
time now. So I think schemas are well supported - but it may be worthwhile
asking qgis and gvsig how they are faring with these today...
I
Paul,
PgSql is not the only driver that use the schema.table notation. I see that
OGR's MSSQLSpatial driver too uses it too. So there won't be anything new.
On the other hand, the '\' separator could lead to some confusion with
escaping in some situations.
On Tue, May 31, 2011 at 10:13 PM, Paul R
This is why I'm looking for guidance from the OGR experts... what
layer name styles work best for interoperation? If I emit schema.table
layers on read, will apps be happy or sad?
The driver is moving towards read/write. I will have no trouble
dealing with schema.table names as I can just map them
On 11-05-31 09:29 AM, Toni Pignataro wrote:
Hello,
I am trying to create an overview image with gdaladdo and tried out different
resampling parameter. My results looks fine on large scale, but zooming out
(small scale) the image looks really poor. What I want to to achieve or
reproduce is an eff
You can find for comparison here an image with my result:
http://wheregroup.com/de/system/files/arcmapp_vs_gdaladdo.png
Am 31.05.2011 15:29, schrieb Toni Pignataro:
Hello,
I am trying to create an overview image with gdaladdo and tried out
different resampling parameter. My results looks fine o
It may help to supply a small test dataset that causes the problem.
Best Regards,
Brent Fraser
On 5/31/2011 1:28 AM, hajer wrote:
No idea about this issue??
Thanks for help !
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-Clipping-multi-polygons-shapefiles-
Hello,
I am trying to create an overview image with gdaladdo and tried out
different resampling parameter. My results looks fine on large scale,
but zooming out (small scale) the image looks really poor. What I want
to to achieve or reproduce is an effect like in ArcMap. Here embedding
an bla
On 11-05-31 07:20 AM, Emmet Spier wrote:
All,
I have been trying to build GDAL with ECWJP2 support. I have built a test
program using exactly the same build environment (vc80) and flags as the gdal
default gdal build enviroment. In Debug builds in or out of the debugger I
experience a crash in t
Paul,
The schema.table is the most similar to the structure of the fgdb, but may be
unwanted complexity. Can this be an option? Like "yes, consider the dataset
name"? Or "no, discard dataset name". I can see myself in both situations...
Is the driver read only? If not, what will happen when you
All,
I have been trying to build GDAL with ECWJP2 support. I have built a
test program using exactly the same build environment (vc80) and flags
as the gdal default gdal build enviroment. In Debug builds in or out of
the debugger I experience a crash in the ERDAS (debug) dll on
GDALClose(). Bel
No idea about this issue??
Thanks for help !
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-Clipping-multi-polygons-shapefiles-with-Geometry-Intersection-Any-help-to-fix-out-my-method-tp6410874p6421682.html
Sent from the GDAL - Dev mailing list archive at Nabble
21 matches
Mail list logo
