I hoping someone can help me with this.
I'm having a few problems with v.support. Occasionally, v.support will return
errors when run after editing linework. Upon exiting v.digit, I run v.support to
build new topology and get the following error messages:
Building areas
Building islands
Attaching labels
PNT_TO_AREA failed: (-22928.293381, 2328298.233617) (Category 2)
PNT_TO_AREA failed: (-285865.336725, 1820096.995142) (Category 57)
PNT_TO_AREA failed: (-350885.939743, 1860159.241012) (Category 57)
PNT_TO_AREA failed: (-404478.463559, 1527592.117214) (Category 134)
PNT_TO_AREA failed: (-399131.708403, 1524785.622589) (Category 134)
PNT_TO_AREA failed: (-509009.406574, 1424217.991164) (Category 141)
PNT_TO_AREA failed: (-510129.947177, 1423329.238582) (Category 171)
PNT_TO_AREA failed: (444027.343043, 1217287.368895) (Category 213)
PNT_TO_AREA failed: (441750.937226, 1208780.872999) (Category 213)
PNT_TO_AREA failed: (113621.646197, 1168144.867585) (Category 177)
PNT_TO_AREA failed: (112299.261130, 1170670.998272) (Category 162)
PNT_TO_AREA failed: (200610.643394, 1072343.642725) (Category 213)
I end up with a map with numerous open areas. Im running GRASS 4.1.2 on Linux
1.0 with 16 Megs RAM & 14 Megs of swap. File size is around 10 megs. I've not
seen this behavior with GRASS4.0 before - does anyone have any ideas what's
going wrong?. I've also seen v.support fail on a regular basis after using
v.proj to move data between UTM and albers projections. Other than these
instances it seems to work fine.
On another subject - is it possible to change the colors of the bounding box
used for zooming both inside and outside of v.digit? My box always seems to
be a variation of black on black. Kinda hard to see.
Any advice is appreciated. Thanks for all replies.
-Ted Cox
USDA/SCS
Palmer, Alaska
astec@acad2.alaska.edu