Hi,
This will interest mostly GDAL driver authors.
I've just added ( http://trac.osgeo.org/gdal/changeset/23077 ) 2 new methods,
GDALRasterBand::ReportError() and GDALDataset::ReportError(), that prepend the
dataset name (and band) before the actual error message.
The use case that lead to the
Have a look at
http://www.gina.alaska.edu/projects/gina-tools/
Best Regards,
Brent Fraser
On 9/7/2011 2:22 PM, David Shean wrote:
Forgive me if this is not the proper forum (no gdal-users list?) or if this
question has been answered in the past - I've been using GDAL for a while now,
but ju
Le mercredi 07 septembre 2011 22:49:58, Etienne Tourigny a écrit :
> Thanks for the info Even
>
> I can see that there is not yet "One standard to rule them all"...
> Correct me if I am wrong: is WKT the preferred way GDAL stores the
> information?
I'd say that WKT serves as a pivot representatio
Thanks for the info Even
I can see that there is not yet "One standard to rule them all"...
Correct me if I am wrong: is WKT the preferred way GDAL stores the
information?
There was a proposal some time ago in the CF trac to add descriptive
variables such as crs_id (EPSG code), crs_name and crs_
Forgive me if this is not the proper forum (no gdal-users list?) or if this
question has been answered in the past - I've been using GDAL for a while now,
but just joined the mailing list and I'm relatively new to python.
I have large (>2GB uncompressed) UInt16 geotiffs that I need to convert to
> How important is this information? Assuming we drop all the citation
> strings, or authority names and codes, but retain the important
> parameters of each projection (in CF and proj format), are we missing
> anything important numerically?
>
> In other words, are there any show-stopper issues
Le mercredi 07 septembre 2011 19:36:54, vasile a écrit :
> Frank Warmerdam wrote:
> > The fix then is to clone it when you want it to live for a while.
> > Also, I believe that the Union method returns the unioned
> > geometry - it does not modify the geometry on which it is invoked.
>
> That did
Le mercredi 07 septembre 2011 17:05:50, Andreas Neumann a écrit :
> HI Jukka,
>
> Thank you for your thoughts. Yes, perhaps I should use update instead
> of append.
>
> I actually found out what the problem is:
>
> Tables or views that do not have an entry in public.geometry_columns
> (the
Welcome aboard Etienne!
"De um ex-aluno do INPE" (From an INPE's alumnus) and fellow commiter.
> ---Original Message---
> From: Etienne Tourigny
> To:
> Cc: gdal-dev@lists.osgeo.org
> Subject: Re: [gdal-dev] Motion: Commit Access for Etienne Tourigny
> Sent: Sep 07 '11 12:42
>
>
Andreas,
Segfaulting is a serious issue. Can you tell the version of GDAL you used?
On Wed, Sep 7, 2011 at 8:35 PM, Andreas Neumann wrote:
> HI Jukka,
>
> Thank you for your thoughts. Yes, perhaps I should use update instead of
> append.
>
> I actually found out what the problem is:
>
> Tables
On Wed, Sep 7, 2011 at 2:33 AM, Even Rouault
wrote:
>
>> In case you feel like testing it, the functions needed are
>> OGRSpatialReference::importFromProj4() and exportToProj4(), the later
>> which is not documented.
>>
>> Perhaps others can comment on the suitability of exporttoProj4() ???
>>
>
Le mercredi 07 septembre 2011 18:34:14, Jukka Rahkonen a écrit :
> I tried to convert data from text file into Spatialite through VRT file.
> Everything goes otherwise OK but the non-ASCII characters in the original
> text do not convert correctly. I am on Windows and the text file is using
> Windo
Le mercredi 07 septembre 2011 13:14:55, Malm Paul a écrit :
> Hi,
> I would lige to update PostgreSQL from 8.3.7 to 9.0.
> Is GDAL, including ogr2ogr, compatible with that version (postgres driver)?
> I'm Using Linux redhat 5. Kind regards,
> Paul
A fix has been done during GDAL 1.8.0 developeme
I would like to thank Frank, Even and Kyle for their support as well
as other PSC members for their trust.
Also big thanks to all the developers and users which help make GDAL
the great software it is.
regards,
Etienne
On Wed, Sep 7, 2011 at 2:14 AM, Even Rouault
wrote:
>> Motion: Extend GDAL
Frank Warmerdam wrote:
>
> The fix then is to clone it when you want it to live for a while.
> Also, I believe that the Union method returns the unioned
> geometry - it does not modify the geometry on which it is invoked.
>
That did the trick, it works just fine, thanks !
Frank Warmerdam wrote
On Wed, Sep 7, 2011 at 9:59 AM, vasile wrote:
> Hello all,
>
> I have a Shapefile layer and try to merge some features from it using OGR
> Python bindings. Basically there are simple polylines that are connected
> each-other, so the result should be a simple polyline as well (and not a
> collectio
Hello all,
I have a Shapefile layer and try to merge some features from it using OGR
Python bindings. Basically there are simple polylines that are connected
each-other, so the result should be a simple polyline as well (and not a
collection)
I am using this snippet of code(warning: that's my beg
Thanks Frank!
I just noticed that in the resulting file, the contents of the first
file are not shifted, whereas the contents of the second file only are
shifted. Not what I would like but certainly correct, considering the
input files.
regards,
Etienne
___
I tried to convert data from text file into Spatialite through VRT file.
Everything goes otherwise OK but the non-ASCII characters in the original text
do not convert correctly. I am on Windows and the text file is using Windows
Latin 1 encoding. I haven't found a place to give codepage in any of t
HI Jukka,
Thank you for your thoughts. Yes, perhaps I should use update instead
of append.
I actually found out what the problem is:
Tables or views that do not have an entry in public.geometry_columns
(the postgis metadata table) cause the segmentation fault. Once the
entry is there, it co
Andreas Neumann carto.net> writes:
>
> Hi,
>
> I am converting several tables from Postgis to SpatiaLite using
> ogr2ogr.
>
> Here is my command:
>
> ---
> ogr2ogr -append -lco LAUNDER=yes -lco SPATIAL_INDEX=yes -nln
> av_grenzpunkte -f SQLite uster.sqlite PG:"dbname='mydb' h
Hi,
I am converting several tables from Postgis to SpatiaLite using
ogr2ogr.
Here is my command:
---
ogr2ogr -append -lco LAUNDER=yes -lco SPATIAL_INDEX=yes -nln
av_grenzpunkte -f SQLite uster.sqlite PG:"dbname='mydb' host='myserver'
port='5432' user='username' password='pw' schemas
Hi,
I would lige to update PostgreSQL from 8.3.7 to 9.0.
Is GDAL, including ogr2ogr, compatible with that version (postgres driver)? I'm
Using Linux redhat 5.
Kind regards,
Paul
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org
On 06/09/2011 17:39, Frank Warmerdam wrote:
On 11-09-06 12:54 AM, Schmitz, Uwe wrote:
So if I conclude:
ESRI and GDAL have different WKT formats. It is not
possible to write GeoTIFF files which are fully
ESRI *and* GDAL compatible.
Uwe,
I do not agree with this conclusion! However, it is
diff
Frank,
> >
> > So if I conclude:
> > ESRI and GDAL have different WKT formats. It is not
> > possible to write GeoTIFF files which are fully
> > ESRI *and* GDAL compatible.
>
> Uwe,
>
> I do not agree with this conclusion! However, it is
> difficult to produce a GeoTIFF file that will exactly
>
25 matches
Mail list logo
