Martin, That certainly makes sense for most GRASS users and devs. And I will develop new features in GRASS 7.
But I am in the special situation that I am developing a GRASS interface for gvSIG/SEXTANTE. And sometimes there are features in GRASS 7 that would make my interface a lot more efficient. Like v.external with 3D geometry support. Or the v.out.ogr speed-ups I recently committed to 6.5. I am willing to live with the risk of using less well-tested features in exchange for more speed and elegance in my interface. So for me, backporting stuff in some situations makes sense. Even if it will never go into GRASS 6.4, I can still use it in my own little "tuned" GRASS distribution that I can bundle with the gvSIG binaries. Thus my question how hard it would be. If it would be really hard, then I won't bother and wait for GRASS 7. Cheers, Ben ----- Original Message ----- > Hi, > > 2011/1/15 Benjamin Ducke <[email protected]>: > > v.external in GRASS 7 allows to link 3D OGR sources as a > > new 3D GRASS map. In GRASS 6, only 2D links are made. > > I tried changing the Vect_open_new() statement in > > GRASS 6's v.external to make a 3D link, but no success. > > > > Is there any deeper reason, why 3D OGR links are not > > possible in GRASS 6? I couldn't find a clue in the API, > > and would be grateful for any info on how difficult > > it might be to backport the 3D OGR access to GRASS 6. > > personally I think it's too much work backport important changes in > vector lib to GRASS 6. I suggest to develop new features in GRASS 7. > > Martin > > -- Martin Landa <landa.martin gmail.com> * > http://geo.fsv.cvut.cz/~landa ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
