Thanks Chaitanya,
I reported the error there. And waiting for answers.
Kind regards,
Tai
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/How-to-identify-a-point-is-belong-to-a-polygon-tp4989501p4989973.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
Even Rouault mines-paris.org> writes:
>
>
>
> > > 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 node
Even
that's a nice trick to know. I wasn't aware of this
Thanks
Yehiyam
Sent from my mobile
-
From: "Even Rouault"
Subject: Re: [gdal-dev] gdalwarp utility
Date: 22 יולי 2012 20:34
Le dimanche 22 juillet 2012 16:28:48, Livneh Yehiyam a écrit :
> Hi
> I've come upon
Le dimanche 22 juillet 2012 16:28:48, Livneh Yehiyam a écrit :
> Hi
> I've come upon a limitation of the gdalwarp utility under windows. When
> creating a mosaic from a large number of files from the command line, I
> ran into the limit of the command line length in windows (about 8000
> characters
Hi
I've come upon a limitation of the gdalwarp utility under windows. When
creating a mosaic from a large number of files from the command line, I ran
into the limit of the command line length in windows (about 8000 characters).
I added the functionality of reading the source files from a txt fi
Sure, pixels were probably not the best word to use. I have 15
points(elements) per scan line per "variable" directly from an aircraft
instrument. So I might have a 15 element array of brightness
temperatures, a 15 element array of latitudes corresponding to those
points in the BT array, and a
