Le mardi 07 décembre 2010 02:05:51, Seth Price a écrit :
> Ah, the joys of multiple platform development.
>
> The first two warnings should be fixable by replacing "-99.0" with
> "-99.0f".
>
> Your fix for read_imagef() should work fine.
ok, I'll commit that then
>
> To fix that last error, tr
On 10-12-06 06:13 PM, iomeneandrei wrote:
Hi Frank,
Frank Warmerdam wrote:
I am not aware of a way to do this from the commandline utilities.
could I use the -nlt parameter of ogr2ogr and force POLYGON? If no, what's
the "power" of -nlt parameter?
Andrea,
Reviewing the ogr2ogr code I see
Ah, the joys of multiple platform development.
The first two warnings should be fixable by replacing "-99.0" with
"-99.0f".
Your fix for read_imagef() should work fine.
To fix that last error, try changing the image size from "1, 1" to "2,
2" or "4, 4". It shouldn't matter because the imag
Hi Frank,
Frank Warmerdam wrote:
>
> I am not aware of a way to do this from the commandline utilities.
>
could I use the -nlt parameter of ogr2ogr and force POLYGON? If no, what's
the "power" of -nlt parameter?
Once again, thank you,
a
-
Andrea Borruso
-
Hi Seth,
I gave a try to Frank's integration of your work with my ATI Radeon HD 5400. I
got the ATI SDK 2.2 correctly installed with latest ATI drivers (10-11). The
few OpenCL demos provided with the SDK I tried work on the GPU device.
(Note: "thanks" to the errors bellow, I've made a few clean
Greetings
following Jean-Claud message
(http://lists.osgeo.org/pipermail/gdal-dev/2010-December/026983.html)
I identified 2 EPSG's with Equidistant Cylindrical:
EPSG 3786 and EPSG 32663. Does anyone, that has used ECWMF ERA Interim
dataset, can tell me which one is used by ECMWF? (I asked t
Hi Frank,
Frank Warmerdam wrote:
>
> At the API or scripting level there is the
> OGRGeometryFactory::forceToPolygon()
> method to try and convert a multipolygon to a simple polygon.
>
I will try using OGR API. I will be slow, but I hope I'll be able to do it.
Thank you very much,
a
-
Frank,
Thanks for tip. I was able to rasterize my polygon and used that to
calculate my sum. Very fast.
bw
On Fri, Dec 3, 2010 at 2:28 PM, Frank Warmerdam wrote:
> Brian Walawender wrote:
>
>> Hello,
>>
>> I am looking for some assistance in optimizing a section of code for
>> faster perfor
Ludovic,
This is excellent news and again any improvement to the original
code is welcome. I actually am in the process of how to map the projection
information for a potential ISIS3 writer. I also have a Python PDS label
creation routine that I was thinking about pushing into library pr
Ralf,
>
> I have created a ticket for the NAS reader. Long numbers (13 digits) are
> read as integer. Maybe there are more drivers who have the same trouble.
Yes, this is an issue that can be potentially found in other drivers. The
situation could improve if/when RFC 31 / OGR 64bit integer is ad
On 10-12-06 06:54 AM, iomeneandrei wrote:
Hi all,
is there in OGR a command that I can use to convert multipart polygons in
singleparts?
Andrea,
At the API or scripting level there is the OGRGeometryFactory::forceToPolygon()
method to try and convert a multipolygon to a simple polygon. I am
Le lundi 06 décembre 2010 12:54:28, iomeneandrei a écrit :
> Hi all,
> is there in OGR a command that I can use to convert multipart polygons in
> singleparts?
None that I am aware of, but if you have some scripting/programming abilities,
you could do that by using the OGR API.
>
> Thank you,
>
Ludovic,
would you mind opening a ticket in the GDAL trac with your patch attached so
it doesn't get lost ?
I see that you've cc'ed Robert Soricone. Does this mean that he or Trent Hare
have already reviewed the patch ?
Some links to public datasets if available would be helpful for testing I
> Does it help at all what I did when trying to reduce the memory demand:
> to loop through the geometries by some CODE value? Does gdal_rasterize
> always load *all* the geometries into memory, independent of the -where
> filter ?
It will only load the geometries that match the -where filter, so
Frank, thanks for your response :
On 3 déc, 22:05, Frank Warmerdam wrote:
>
> GDAL only supports single nodata values as part of the data model. You
> can add arbitrary metadata describing other nodata values, but generally
> GDAL itself and other client software won't realize the significance
On 12/3/10 6:26 PM, Brian Wilson wrote:
Greetings, I am looking for some suggestions on how to build the
python bindings for the latest gdal sources (1.7.3) for Windows.
I haven't done it for a while, but a few notes that might help get you
moving:
Environment: Windows 7, Visual Studio 2010
Hi,
i have a patch for gdal 1.7.3 to improve isis2 driver.
The patch had
* writing functionality for QUBE object
* grab null value
* improve the type reading
* can read qube with back plane, side plane and bottom plane
* can read a file with label detached or attached.
and i have modify nasakeyw
Over the summer I rewrote the warper to use OpenCL. There was a 2x to
50x speedup. Here is a description of what I did:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-gdalwarp-OpenCL-Performance-Week-9-td5341226.html
~Seth
On Dec 6, 2010, at 5:10 AM, Konstantin Baumann wrote:
Hi,
what be
On 10-12-06 07:10 AM, Konstantin Baumann wrote:
Hi,
what benefit/improvement would the OpenCL integration bring to GDAL?
Additional functionality or a speedup of existing functions? Probably only
operations on images and/or rasters are supported; reprojection/warping and
filtering would be good
Le 06/12/2010 13:19, António Rocha a écrit :
Hi Jean-Claude
So, how can I know which EPSG CRS codes are use this projection?
Thanks
Antonio
You can look at http://www.spatialreference.org and find your projection.
___
gdal-dev mailing list
gdal-dev@l
On 06/12/2010 13:15, Even Rouault wrote:
Selon Hermann Peifer:
Even,
Thanks for the quick feedback.
Just to clarify: last week, I compiled revision 21190 from
http://svn.osgeo.org/gdal/trunk/gdal, configured
--with-libtiff=internal.
Hum OK so there's definitely a bug somewhere. Would be worth
e
database 5677 (20101206) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Selon Hermann Peifer :
> Even,
>
> Thanks for the quick feedback.
>
> Just to clarify: last week, I compiled revision 21190 from
> http://svn.osgeo.org/gdal/trunk/gdal, configured
> --with-libtiff=internal.
Hum OK so there's definitely a bug somewhere. Would be worth opening a ticket if
you had a
Hi,
what benefit/improvement would the OpenCL integration bring to GDAL? Additional
functionality or a speedup of existing functions? Probably only operations on
images and/or rasters are supported; reprojection/warping and filtering would
be good candidates, right? What concrete operations wou
Hi all,
is there in OGR a command that I can use to convert multipart polygons in
singleparts?
Thank you,
a
-
Andrea Borruso
email: aborr...@tin.it
website: http://blog.spaziogis.it
my 2.0 life: http://aborruso.spaziogis.it
feed: http://
Hello list,
I have created a ticket for the NAS reader. Long numbers (13 digits) are read
as integer. Maybe there are more drivers who have the same trouble.
I have tested some workarounds. Changing the attribut definition in gfs file
is successful, when destination driver is PGdump or Postgres
Le 06/12/2010 11:21, António Rocha a écrit :
Greetings
I'm using gdal15 and gdal16 and I'm trying to use gdalwarp with the
following command:
gdalwarp -s_srs EPSG:9823 -t_srs EPSG:3763 file.nc file.tif and I get
the error:
ERROR 6: EPSG PCS/GCS code 9823 not found in EPSG support files. Is this
Even,
Thanks for the quick feedback.
Just to clarify: last week, I compiled revision 21190 from
http://svn.osgeo.org/gdal/trunk/gdal, configured
--with-libtiff=internal. I have 8G of memory, which is about 20 times
the size of the shapefile. However, I might have been processing other
shapef
Greetings
I'm using gdal15 and gdal16 and I'm trying to use gdalwarp with the
following command:
gdalwarp -s_srs EPSG:9823 -t_srs EPSG:3763 file.nc file.tif and I get
the error:
ERROR 6: EPSG PCS/GCS code 9823 not found in EPSG support files. Is this
a valid EPSG coordinate system?
ERROR 1: T
Selon Hermann Peifer :
Herman,
About your attempt to try to rasterize everything at once, it is likely that you
ran out of virtual memory as gdal_rasterize will load all the geometries in
memory before proceeding to the rasterization (it requires probably much more
memory than the on-disk size of
Hi,
Over the weekend, I tried to gdal_rasterize a 350+ MB shapefile with
149671 polygon features into a 64116 x 61850 GeoTIFF.
I first had some trouble while trying to rasterize everything at once,
because after some time, the gdal_rasterize process got killed by the
kerned (that's how I un
31 matches
Mail list logo
