Le dimanche 07 octobre 2012 11:42:30, Even Rouault a écrit :
> Hi,
>
> Following a recent similar move from MapServer, I've setup an instance of
> Travis CI, hosted continuous integration service. After each SVN commit in
> trunk, GDAL is built and the Java, Perl and Python tests are run.
>
> Tra
On 10/09/2012 08:45 PM, Even Rouault wrote:
Did you check that there was no error or warning reported when
building the VRT ?
There is no warning from gdalbuiltvrt, is there a flag for a verbose mode?
What do you mean by "I don't have any data" ? Do you mean that if you
do an extraction from
Hi,
I´m getting a sql parsing error when I tried to execute a query to a
shapefile where column name starts with "_".
When i execute a query like : ogrinfo Provincias.shp -sql "SELECT * FROM
Provincias WHERE tipo = 1"
INFO: Open of `Provincias.shp'
using driver `ESRI Shapefile' successful.
Le mardi 09 octobre 2012 18:27:29, Frank Warmerdam a écrit :
> Motion: The GDAL/OGR 1.9.2RC2 release is promoted to be the
> official GDAL/OGR 1.9.2 release.
>
+1 Even
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/list
On Tue, Oct 9, 2012 at 11:07 AM, Chris Barker wrote:
> On Sun, Oct 7, 2012 at 8:33 PM, Tim Keitt wrote:
>
>>> cool! though I"m a little confused as to how this fits with OGR.
>>
>> OGR is used for i/o.
>>
>
> I see -- so you've written something like the triangle command line
> utility, but with
Le mardi 09 octobre 2012 19:08:33, yvecai a écrit :
> I'm trying to make a world-wide hillshade dataset filling SRTM void from
> Aster, and using Aster data only between 60°N and 72°N.
> I computed all 1x1° hillshade tiles, but now I'm struggling to work with
> a vrt.
> If I make a .vrt of all ~29'
Frank & Nikhil,
Frank asked:
>are, I'm not sure what I or others can do about
>the performance cost of checking.
If I understand the problem, then it cost nothing!
You have to check the winding while loading a OGRGeometryH
like so:
double area = 0;
+1
Tamas
2012/10/9 Frank Warmerdam
> Motion: The GDAL/OGR 1.9.2RC2 release is promoted to be the
> official GDAL/OGR 1.9.2 release.
>
> ---
>
> PSC members are encouraged to review the release candidate
> and vote. Non-PSC members are encouraged to review the
> release candidate and comment
On Oct 9, 2012, at 11:34 AM, Daniel Morissette wrote:
> On 12-10-09 12:27 PM, Frank Warmerdam wrote:
>> Motion: The GDAL/OGR 1.9.2RC2 release is promoted to be the
>> official GDAL/OGR 1.9.2 release.
>>
>
> +1 Daniel
+1 Howard
___
gdal-dev mailing
I'm trying to make a world-wide hillshade dataset filling SRTM void from
Aster, and using Aster data only between 60°N and 72°N.
I computed all 1x1° hillshade tiles, but now I'm struggling to work with
a vrt.
If I make a .vrt of all ~29'000 single 1x1° tiles, I don't have any data
above 60°N, ne
On 12-10-09 12:27 PM, Frank Warmerdam wrote:
Motion: The GDAL/OGR 1.9.2RC2 release is promoted to be the
official GDAL/OGR 1.9.2 release.
+1 Daniel
--
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000
___
Motion: The GDAL/OGR 1.9.2RC2 release is promoted to be the
official GDAL/OGR 1.9.2 release.
---
PSC members are encouraged to review the release candidate
and vote. Non-PSC members are encouraged to review the
release candidate and comment here on problems.
The motion will be open for two days
On Mon, Oct 8, 2012 at 10:28 PM, Nikhil Sai Parupalli <
nikhil.parupa...@iictechnologies.com> wrote:
> HI All,
> ,
>
> Thanks for the reply in below data
>
> NAME_RCNM (IntegerList) = (7:130,130,130,130,130,130,130)
>NAME_RCID (IntegerList) = (7:691,391,690,52,1336,1503,1512)
>ORNT (Int
On Tue, Oct 9, 2012 at 3:41 AM, maning sambale
wrote:
> I see, is there a scripting workaround using 1.9?
ogr2ogr has various -clip. options. It looks like you could
specify using a particular feature in the AdminPoly to do this
(presumably GEOS support is required?).
ogr2ogr -f "ESRI shape
On Sun, Oct 7, 2012 at 8:33 PM, Tim Keitt wrote:
>> cool! though I"m a little confused as to how this fits with OGR.
>
> OGR is used for i/o.
>
I see -- so you've written something like the triangle command line
utility, but with OGR for IO, so you don't need to use triangles
particular data fil
I see, is there a scripting workaround using 1.9?
On Mon, Oct 8, 2012 at 9:14 PM, Etienne Tourigny
wrote:
> generally speaking new features do not go into current stable version
> (1.9), they will be incorporated into next stable version (probably
> 2.0).
>
> Etienne
>
> On Mon, Oct 8, 2012 at 9:
Even Rouault mines-paris.org> writes:
> I've looked at WFS 1.1 spec, and at page 17 (§7.3 Property names), I see that
> the definition of the property name allows a dot character. So this is
> theoretically valid...
TinyOWS is now theoretically fixed
https://github.com/mapserver/tinyows/iss
The problem is OGRSQL (ogr_gensql.cpp) which adds the string "FIELD_%d" when it
doesn't know how to handle column names with dot character in them. Because the
dot character is a special/reserved character it needs to be enclosed in '',
"", ``, [], ..., all depending on which dialect is used (M
18 matches
Mail list logo
