Am 05.07.2014 23:40, schrieb klausenlie:
Hi again.
Some of you have said something about opening sosi-files
in QGIS. I myselft haven't found any other place than in the
file explorer, but opening from there i get the error message.
I have tried to look in the toolbox for gdal but havnet found any
Matthias,
have a look at the Layer list widget for PyQGIS applications [1], perhaps
it could fit your needs.
Not sure if it works on recent QGIS versions, though.
Regards,
Germán
-
[1]
http://geotux.tuxfamily.org/index.php/en/component/k2/item/270-tabla-de-contenido-leyenda-para-aplicacione
Hi again.
Some of you have said something about opening sosi-files
in QGIS. I myselft haven't found any other place than in the
file explorer, but opening from there i get the error message.
I have tried to look in the toolbox for gdal but havnet found anything there
for sosi.
--
View this me
You misunderstood me Andrea. I've never said that :)
I said that when geometry collections need to be treated within QGIS, you
have to work at the GEOS level.
giovanni
Il 05/lug/2014 21:40 "Andrea Peri" ha scritto:
> Hi Larry,
>
> probably I don't understand well the concept of "at geos level".
Hi Larry,
probably I don't understand well the concept of "at geos level".
My english is worsened ultimately.
:(
I understand that Giovanni say to add some change to geos library , to
change the methods or adding some new method in the geos.
:)
I agree that the solution is to add to qgis the c
HI,
On Sat, Jul 5, 2014 at 12:10 PM, Andrea Peri wrote:
> Is wrong.
> The geos return a collection when the collectionis the right result.
>
> if the result is a collection like:
> collection (multipolygons, multilinestrings, multipoint)
>
> why it should remove the lines and points.
>
> It cou
Sorry for the buzz. It's not QGIS fault, it's GDAL itself which reads the
ASCII Grid as Float64, but I wonder why contrarily gdalinfo and
gdal_translate treats it as Float32...
2014-07-05 18:56 GMT+02:00 G. Allegri :
> I haven't spot tha exact point where this happens but QGIS exports
> Float64,
Well, Andrea, QGIS adopts GEOS capabilities as far as it can.
As you will know it doesn't support Z and M geoms as well.
I hope future founders will help extending its capabilities...
giovanni
2014-07-05 20:10 GMT+02:00 Andrea Peri :
> Is wrong.
> The geos return a collection when the collectio
Is wrong.
The geos return a collection when the collectionis the right result.
if the result is a collection like:
collection (multipolygons, multilinestrings, multipoint)
why it should remove the lines and points.
It could be useful to the client.
The fact that the client is capable to understa
I haven't spot tha exact point where this happens but QGIS exports Float64,
even if the origin was Float32.
giovanni
2014-07-05 16:54 GMT+02:00 G. Allegri :
> Causally I hit the save as raster dialog, and I tried to export a raster
> to layer (coming from an ASCII Grid source) to Geotiff, with
I'm working with conflict data, and because of escalation (e.g., kidnappings,
bombings and insurgent attacks can lead to full-scale territorial disputes),
temporal point features can become stacked. I was initially trying to figure
out a way to highlight a record within a selected set in the att
(I changed the topic)
Geometry collections in QGIS must be treated at the GEOS level.
There isnt a QGIS::wkbType for geometry collections, so if GEOS return a
collection they must be managed as GEOS geometries, before "moving them up"
to QgsGeometry.
Correct me if I'm wrong.
giovanni
2014-07-0
Thx GioHappy, this is imprtant for me to know.
So is surely better to use the postgis or spatialite
because it allow you to extract from the collection the section with
the right type.
If you do a difference beetwen two polygons is the result is a
collection with a polygon section and a point sec
Causally I hit the save as raster dialog, and I tried to export a raster to
layer (coming from an ASCII Grid source) to Geotiff, with no creation
options set.
The result was a file 3 times bigger then the original ASCII, and 5 times
bigger then the Geotiff created by gdal_translate.
gdalinfo on th
AFAICS whenever a new feature needs to be created, geom collections are
discarded, because QGIS cannot manage them.
giovanni
2014-07-05 16:40 GMT+02:00 Andrea Peri :
> Ok, sorry.
>
> Just a my personal curiosity:
> The difference could give also a collection not empty.
> If the difference of tw
Ok, sorry.
Just a my personal curiosity:
The difference could give also a collection not empty.
If the difference of two polygons is a collection with some polygons,
some lines and some points.
What happened to this collection in QGIS ?
Thx,
A.
2014-07-05 16:03 GMT+02:00 G. Allegri :
> Hi Andre
Hi Andrea, as I said above I'm not considering it an error.
The topic of this post is QGIS message logging.
The processing completes as expected, with the same results as Spatialite
and PostGIS. These simply do it silently :)
giovanni
2014-07-05 15:59 GMT+02:00 Andrea Peri :
> Hi GioHappy,
>
>
Hi GioHappy,
the empty-collection is absolutelly not necessarylly a bug.
It is the obviously result of an operation on a machine (like the
computer) with a binary finite arithmetic.
Usually the empty is due to a too low value to be describe with a
finite binary arithmetic.
If the dataset is smal
On 28-06-14 08:11, Martin Dobias wrote:
> Let me paste some example code. Let's prepare few things to begin with:
>
> # add few layers at the beginning so the legend is not completely empty
> v1 = iface.addVectorLayer("Point", "Layer 1", "memory")
> v2 = iface.addVectorLayer("Point", "Layer 2", "m
Hi Jurgen,
I wouldn't call them errors. GEOSDIfference returned a lot of empty
geomcollections, which the QgsVectorFileWriter couldn't manage.
Consequently it wrote a log message for each geometry it couldn't write [1].
Surely the logging should be improved in this specific case. Anyway, I
think t
Hi Giovanni,
On Sat, 05. Jul 2014 at 10:27:24 +0200, G. Allegri wrote:
> As I reported in a previous post, I was unable to conclude a difference
> operation on a vector because the tool was running in exponential time.
> Debugging pointed me to the problem: QgsVectoFileWriter was logging tons of
I've added a pull request about this https://github.com/qgis/QGIS/pull/1499
giovanni
2014-07-05 11:15 GMT+02:00 G. Allegri :
> I meant QgsMessageLog, not QgsLogger...
>
>
> 2014-07-05 10:27 GMT+02:00 G. Allegri :
>
> As I reported in a previous post, I was unable to conclude a difference
>> ope
I meant QgsMessageLog, not QgsLogger...
2014-07-05 10:27 GMT+02:00 G. Allegri :
> As I reported in a previous post, I was unable to conclude a difference
> operation on a vector because the tool was running in exponential time.
>
> Debugging pointed me to the problem: QgsVectoFileWriter was logg
As I reported in a previous post, I was unable to conclude a difference
operation on a vector because the tool was running in exponential time.
Debugging pointed me to the problem: QgsVectoFileWriter was logging tons of
empty geometres with an incompatible type which will be discarded.
After comme
24 matches
Mail list logo
