Opened 17 years ago
Closed 16 years ago
#171 closed defect (fixed)
d.vect: -c type=area doesn't draw boundary
Reported by: | hamish | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 6.4.0 |
Component: | Default | Version: | svn-develbranch6 |
Keywords: | d.vect | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
'd.vect -c type=area' doesn't draw boundaries.
If you use type=area,boundary you get them, but IIUC "area" is an alias for "centroid,boundary", so you shouldn't have to do that.
I am not sure if 'd.vect -a type=area' will or not.
Hamish
Attachments (1)
Change History (8)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
I assume that in darea() of d.vect/area.c some test is needed in the loop therein to distinguish the various vector types while looping over all vectors.
Markus
follow-ups: 4 5 comment:3 by , 17 years ago
Hi I don't know it is the same issue but I can not draw any vector map with d.vect when I use command like d.vect output=map1 i got this error message: output <map1> exist. If I put an inexistant vector, I got: map <map1> not found. Thank you
comment:4 by , 17 years ago
Replying to neuba:
Hi I don't know it is the same issue but I can not draw any vector map with d.vect when I use command like d.vect output=map1 i got this error message: output <map1> exist. If I put an inexistant vector, I got: map <map1> not found.
There is no 'output' parameter
d.vect --help
d.vect output=x Sorry, <output> is not a valid parameter ERROR: Required parameter <map> not set: (Name of input vector map).
Martin
comment:5 by , 17 years ago
Replying to neuba:
Hi I don't know it is the same issue but I can not draw any vector map with d.vect when I use command like d.vect output=map1 ...
IMPORTANT to all SVN users: After the recent change in parser.c you need to RECOMPILE GRASS from scratch.
I wanted to post this but forgot about it. So
make distclean sh configure ... make
to get the parameters right again.
@neuba: this is unrelated to this bug report.
Markus
by , 16 years ago
Attachment: | d.vect.diff added |
---|
comment:6 by , 16 years ago
CPU: | → Unspecified |
---|---|
Platform: | → Unspecified |
Attached diff should fix the bug. I don't really understand why there was a conditioning on the value of rgb in there. Looking through the code, I don't think it is useful, but please test (notably with some of the flags, such as table color and z-color).
Moritz
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
correction: it draws the boundaries, but uses the same color as the fill when it should make the area color random and the line color respect color=. e.g.:
see the d.vect symbol drawing code for an example of using a primary and secondary color in place of line= and fill=.
Hamish