thanks. I download the r26999 branch and it works good now. And I am puzzled
what does the stripsize means. the tiff file i create by gdal is tiled with
blocksize 256x256, and the blocksize will be changed to imagewidthx1 if do
some image editing and saved by photoshop. Does the stripsize means
bl
Le mardi 04 mars 2014 21:41:45, agerrius a écrit :
> > Only set the filter on the multipolygons layer.
>
> But if I don't set any filter on the other layers I do get all other point
> and line features (for example highway, etc). And I don't want them, I for
> example only want landuse features. S
> Only set the filter on the multipolygons layer.
But if I don't set any filter on the other layers I do get all other point
and line features (for example highway, etc). And I don't want them, I for
example only want landuse features. So I want no features to be returned
from layers that don't h
Le mardi 04 mars 2014 20:56:59, agerrius a écrit :
> Even,
>
> In my actual application I am looping over all layers, but it still doesn't
> work.
>
> But from your feedback I now know what is going wrong. My problem is what
> to do with layers that don't contain the field I am filtering on. If I
agerrius agerrius.nl> writes:
> So how would one get all the OSM features that have an attribute landuse? As
> you can see I used "landuse IS NOT NULL" for the attribute filter. But if I
> set that on the points layer I get an error, since there are no landuse
> points. How can I set the filter
Even,
In my actual application I am looping over all layers, but it still doesn't
work.
But from your feedback I now know what is going wrong. My problem is what to
do with layers that don't contain the field I am filtering on. If I apply
the filter to them and error is thrown (ERROR 1: 'landuse'
On Tue, 4 Mar 2014 23:13:51 +1100, Nik Sands wrote:
The conversion process is a little slow for large data sets
Hi Nik,
SQLite is a transactional DBMS and consequently your
approach to transaction handling has a very strong
impact on write performances.
just as a quick and dirty rule-of-the-
Thanks to everybody who helped me towards getting this working - it is now
working correctly. The conversion process is a little slow for large data
sets, but the results are excellent, and the Spatialite databases are MUCH
faster for spatial filtered lookups than the Shapefiles I had been usin
Thanks for this information.
I'd like to replicate that ogr2ogr PROMOTE_TO_MULTI functionality in my code,
but I'm having trouble figuring out how to do it. I guess I can take a look at
the ogr2ogr code.
(I could also just include the entire ogr2ogr tool bundled into my app and call
it from t
Selon Nik Sands :
> You are correct - I did misunderstand. Thanks for further explaining the
> multiple geometries to me. :-)
>
> So it looks like the best option for me is to make a copy of each source
> layer which may contain both single and multi variants (eg, point and
> multipoint features
You are correct - I did misunderstand. Thanks for further explaining the
multiple geometries to me. :-)
So it looks like the best option for me is to make a copy of each source layer
which may contain both single and multi variants (eg, point and multipoint
features) and make the new SQLite l
Hi all,
just yo better clarify some relevant details:
a Shapefile can legitimately contain one the following shapes:
Point, PolyLine, Polygon and MultiPoint; and there are further
shape-codes intended to support extended XYZ or XYM dimensions,
such as PointZ and PolyLineM
please note: according
Nik Sands nixanz.com> writes:
>
> Thanks Chaitanya,
> It's finally dawned on me that this is what the following is about in the
OGR SQLite format web page:
>
>
> Tables with multiple geometries
> Starting with OGR 1.10, tables that have multiple geometry columns
registered in geometry_columns
13 matches
Mail list logo
