Hi guys,
When asking gdalwarp to warp from a WKT projection generated by ESRI, it
will fail when attempting to convert it to Proj4 (ex: Lambert_Conform_Conic
projections).
Wouldn't it be possible to integrate some check/transformation like the one
done in Python here :
(file or WKT string) with ESRI::
I'm pretty sure that gdalwarp uses SetFromUserInput to get the SRS
definition.
[1]
http://www.gdal.org/ogr/classOGRSpatialReference.html#aec3c6a49533fe457ddc763d699ff8796
On Fri, Jun 29, 2012 at 7:09 AM, Matthieu Rigal ri...@rapideye.net
wrote:
Hi guys
band. The -b parameter would have been
perfect. Is it something that may be implemented/added in the future ?
For now, I am creating virtual rasters and I am then merging them or I
generate the 5 bands and then use gdal_translate, but it is more time and
space consuming.
Regards,
Matthieu Rigal
here...
Sorry again,
Regards,
Matthieu
On Monday 28 March 2011 17:53:47 Matthieu Rigal wrote:
Dear GDAL heroes,
I have encountered a very strange behaviour of the python bindings. I am
using version 1.7.3 with Python 2.6 on a OpenSuse 11 64bits.
We developped an in-house C++ python accessor
not give easily a sample)
But also, the fact that this only occurs with 1 osgeo packages (I tried
several other ones) indicates that there might be a problem on this side, or
am I wrong ?
Any help or hint on something I could have forgotten would be appreciated !
Best Regards,
Matthieu Rigal
be added, as it is quite widely used properties...
Regards,
Matthieu
--
Matthieu Rigal
Product Development
RapidEye AG Tel: +49-(0)3381-89 04 331
Molkenmarkt 30 Fax: +49-(0)3381-89 04 101
14776 Brandenburg/Havel
Germany
3, 2010 at 9:23 AM, Matthieu Rigal ri...@rapideye.de wrote:
Hi guys,
I was checking and I did not found a proper way for now to add a unique
or not null constraints to columns of a layer created/edited by OGR.
If I am wrong, please correct me.
Else, as I saw that a big refactoring
Hi folks,
Currently running GDAL 1.7.1, I noticed a regression towards the 1.6.x branch
which I could not find in the tickets.
Teh GetDescription() always seems to return empty strings, except for just
created file and just setted description...
Here is a description of the bug, I don't think
or to python...
I just filed this discussion as a ticket, her you can find it
http://trac.osgeo.org/gdal/ticket/3780
Thanks for all the great job you're doing !
Best Regards,
Matthieu
On Monday 11 October 2010 16:33:51 Frank Warmerdam wrote:
Matthieu Rigal wrote:
Hi folks,
Currently running
layers having names created by other
software, the GetDescription() did return it, whereas know it is not returning
it...
Regards,
Matthieu
On Monday 11 October 2010 16:43:02 you wrote:
Selon Matthieu Rigal ri...@rapideye.de:
Matthieu,
I can reproduce in trunk too. I'm not aware
Hi folks,
I am currently implementing a tool to allow band-to-band computations on
array values out of 2 images with different projection and different
resolution in python.
The operation is quite complex, so I will summarize it here and below give
the solution I am currently testing to see if
/ogrsf_frmts/pg/ogrpgtable
layer.cpp#L1895 ) So it was never returning more than 500 features. IMHO,
the number 500 looks like an intentional limitation, probably set on the
server connection.
On Fri, Oct 9, 2009 at 4:11 PM, Matthieu Rigal ri...@rapideye.de wrote:
Hi people,
I recently
: Failed to open Shapefile `merge.shp/fileone.shp'.
If it was resolved, forget it, if I am the only one, forget it maybe also...
but this is strange...
Regards,
Matthieu
--
Matthieu Rigal
Product Development
RapidEye AG Tel: +49-(0)3381-89 04 331
Molkenmarkt 30
Hi Frank and GDAL-dev team,
By reading the following message and unsuccessfully searching for
documentation and possibilities to rasterize geometries, I would be pleased
to know if the Python bindings for GDALRasterizeGeometries() are still
somehow planned.
If no bindings are planned is there
is the Datum set to unknown and the spheroid to unnamed ?
It also causes some other software to warn that the projection is not the same
(as the desired)...
Best regards,
Matthieu
--
Matthieu Rigal
Product Development
RapidEye AG Tel: +49-(0)3381-89 04 331
Molkenmarkt 30
On Friday 29 May 2009 13:49:01 Lucena, Ivan wrote:
If you use DATUM[GRS_1980 instead of DATUM[D_GRS_1980 it might work.
See http://spatialreference.org for more info.
---Original Message---
From: Matthieu Rigal ri...@rapideye.de
Subject: [gdal-dev] non-fully conform output
script will display two eacute characters,
provided that your text editor is indeed using UTF-8 encoding.
#!/usr/bin/python
# -*- coding: utf-8 -*-
print '\xc3\xa9'
print 'é'
Best regards,
Even
Le Tuesday 05 May 2009 13:07:47 Matthieu Rigal, vous avez écrit :
Hi all,
I have a problem
enhancement to have the possibility to set
-dsco X:5 Y:5
or similar when translating a shapefile to a meter/UTM projection ?
Best regards,
Mattheu
--
Matthieu Rigal
Product Development
RapidEye AG Tel: +49-(0)3381-89 04 331
Molkenmarkt 30 Fax: +49-(0
text is LATIN1 you could set
the environment variable to LATIN1 before using OGR and input would be
assumed to be LATIN1 instead of UTF-8.
Any suggestions or help is highly appreciated !
Regards,
Matthieu
--
Matthieu Rigal
Product Development
RapidEye AG Tel: +49-(0
:17 you wrote:
Matthieu Rigal wrote:
Hi all, hi Frank,
I am encountering problem with gdal_translate and gdalinfo with very
little images. I have for example a 9*16 pixels image, georeferenced,
16bits and 8bits, that I have tested in 2 formats : .pix PCIDSK and .tif
GTiff.
And both
Hi all, hi Frank,
OOps, I have forgot to say that I unfortunately have only the version
1.4.2 of GDAL/OGR here. If it works on your machine, then it may come from
this out-of-date version
But please check it also from your side...
Best regards,
Matthieu Rigal
RapidEye AG
Molkenmarkt
Geomatica...
If you have any ideas or if it is a known bug... let me know !
Best regards,
Matthieu Rigal
PS : it may be related to the bug described before, but just to know, is there
anything wrong in this portion of Python code :
sName = sFile[:-3] + tif
Hi all,
Since the method of Create, SetGeoTransform, etc... is complicated and
unefficient from a performance point of view, what is the way to quickly add
the GeoTransform, taken from a referenced raster to a raster that have lost
the information.
Best regards,
Matthieu
--
Matthieu Rigal
23 matches
Mail list logo