Tai,
You can use the spatial filter of the ogr layer to filter the point
features to speed things up. You will still have to test if the point is
within the polygon but it will be faster.
Also, make sure the test is like point-Within(polygon) and not
polygon-Within(point)
We should have this discussion in the gdal-dev list.
dhonjuh,
Try this at the command prompt; not the python command prompt.
$ gdal_calc.py -A cknp_dem_30m.tif --calc A/2 --outfile t.tif
Also, make sure you did not make any inadvertent changes to the script.
On Fri, Jul 20, 2012 at 2:00 PM,
Rahkonen Jukka Jukka.Rahkonen at mmmtike.fi writes:
Even Rouault wrote:
Do you have comparisons of the performance with osm2pgsql on the same
PC and
with the same data ? I'd be curious if that slow down effect is
found with every
tool, or if it is something specific to the way
If you want I can remove the MemoryDriver, but it is still the same thing.
[code]
string request = SELECT * FROM MY_TABLE WHERE CHART_ID = 'Z15F43AJ';
Layer serverLayer = RclDataSource.ExecuteSQL(request, null, );
int nbFeature = serverLayer.GetFeatureCount(1);
Feature serverFeature =
I'm attempting to put aircraft scan data into geotiffs (1-3 scanlines
each) and then use gdal_merge.py to combine them into one large geotiff
that has the entire aircraft's path. The scan lines are 15 pixels wide
and taken every 10 seconds, the geotiffs are wgs84 lat/lon, and I have
lat/lon
Le vendredi 13 juillet 2012 16:22:34, Pierluigi Guasqui a écrit :
Even,
I opened a ticket in GDAL Trac: http://trac.osgeo.org/gdal/ticket/4749.
Confirmed and fixed now. Thanks for reporting.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
Le vendredi 13 juillet 2012 12:40:34, Smith, Michael ERDC-CRREL-NH a écrit :
Ticket created
http://trac.osgeo.org/gdal/ticket/4748
Confirmed and fixed now. Thanks for reporting
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
However, select with SQL feels sub-optimal.
Yes, when you use ogr2ogr with explicit layer names, there are
optimizations. For example, when you only specify the layer 'points', the
OSM driver will not even try to index the nodes into the temporary
database because it is not needed.
