I agree. I think having mixed geometries per layer can make things a hell of a lot harder and I would rather have a single geom type per layer. I used to use MapInfo and it can store different geom types in one layer, this makes it hard to style (more of a limitation of MapInfo I admit), hard to work with from a programming point of view (you now have to check the geom type each time because it might have changed), and just a pain to manage. It makes sense to keep things apart.
Like the GPX import, QGIS should handle multi geom layers better by just splitting it out into many layers. - Nathan On Wed, Aug 1, 2012 at 1:02 AM, Andre Joost <[email protected]> wrote: > Am 31.07.2012 16:51, schrieb Zoltan Szecsei: >> >> On 2012/07/31 16:30, Ralf Wessels wrote: >>> >>> Andre is right - qgis (_like other gis systems too)_ cannot display >>> >>> points, lines and polygons in one layer. It has to be either points or >>> lines or polygons. In a kml-file this is no problem. >> >> >> The "like other gis systems" part of your statement is total hogwash. >> Sorry. >> You've obviously only been brought up on a diet of ShapeFiles. >> > > To calm down: > > It has some advantages to have different geometry types separately in > different layers. > > The GPX import in Qgis makes three different layers out of points, routes > and tracks within the same file. It would be nice to implement this in kml > import, if several geometry types are encountered in the same folder. This > is far better than just throw away elements of other types. > > Greetings, > Andre Joost > > > _______________________________________________ > Qgis-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-user _______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
