Sorry for the delay No, I was not able to fix the problem with
v.patch. Although I tried several different suggestions, none of them
worked. It still dropped some of the larger regions that were shared
between the maps. My only remaining idea, which I have not tried
primarily because of the number of separate vector maps is to run
v.patch on all of them, and then add the dropped regions one at a
time. This may be completely off base, but I wonder if it might have
something to do with bounding boxes surrounding each vector map. The
box might cut the dropped region when we run v.patch. Just a thought
if anyone else reads this.
I did finish the task, but using a less than optimal work around. I
converted each of the vector maps to a raster map, and then I patched
them together. As I said, less than optimal, but it got the job done.
Brian
On Jun 9, 2008, at 7:49 PM, Oliver Sonnentag wrote:
Hi Brian, just wondering if you ever figured out why v.patch drops
boundary vector regions ....
http://lists.osgeo.org/pipermail/grass-user/2008-March/044155.html
I'm facing exactly the very same problem as described in your post
at the moment and I can't figure how to get this vector maps v.patch-
ed correctly.
In advance, thanks a lot.
Regards,
Oliver
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
