[GRASS-dev] Which v.* modules are working with v.external'ed data

[Helmut Kudrnovsky]

Markus Metz-3 wrote
> On Wed, Nov 15, 2017 at 1:36 PM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>>
>> Background of the question in subject: the GRASS algs in upcoming QGIS3
> are
>> working with v.external linked data.
>>
>> I've seen some modules doesn't work with such kind of data.
>>
>> Is there maybe a list already available?
> 
> It depends also on the format that is linked in with v.external. For all
> formats that do not have a key column (e.g. shapefile), attributes are not
> accessible, and attributes would get lost when modifying the
> geometries.Therefore it is generally not safe to link vector data with
> v.external. In many cases it does not make sense to use v.external linked
> data with simple features, instead vector data should be imported to get
> true topology. If upcoming QGIS3 is working with v.external linked data,
> the GRASS interface of QGIS is effectively broken.
> 
> Markus M
> 
> _______________________________________________
> grass-dev mailing list

> grass-dev at .osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-dev

in QGIS 3 options, a switch to  v.in.ogr is possible..

I think we should communicate to the QGIS devs that v.external isn't the
best choice.



-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html