Opened 9 years ago

Closed 9 years ago

#2522 closed defect (fixed)

d.vect.thematic, d.thematic.area in GRASS 7.0

Reported by: martinl Owned by: grass-dev@…
Priority: blocker Milestone: 7.0.0
Component: Display Version: svn-trunk
Keywords: d.vect.thematic, d.thematic.area Cc:
CPU: Unspecified Platform: Unspecified

Description

Currently we have two modules for thematic rendering vector data:

  • d.vect.thematic
  • d.thematic.area

d.vect.thematic is a Python script which has been rewritten from Bash based on code from GRASS 6. This module runs several times d.vect command to render thematic data. This makes an integration of this module in wxGUI as problematic.

d.thematic.area is a C module which use C library. This make this module quicker to render data and more flexible. The code can be shared eg. with v.colors to calculate breaks, etc. Unfortunately it's just written for areal features and seems to be somehow not finished.

My suggestion is (before GRASS 7 release):

  • to move python script d.vect.thematic to addons
  • rename d.thematic.area to d.thematic or better d.vect.thematic (in this case to rename d.vect.thematic in addons to d.vect.thematic2) - any other name?

In the future to improve C module based on functionality of Python script.

Any comments, ideas?

Change History (2)

in reply to:  description ; comment:1 by martinl, 9 years ago

Replying to martinl:

  • to move python script d.vect.thematic to addons

I moved d.vect.thematic to addons as d.vect.thematic2 in r63974:63975

  • rename d.thematic.area to d.thematic or better d.vect.thematic (in this case to rename d.vect.thematic in addons to d.vect.thematic2) - any other name?

done in r63976:63983. If no objection I will backported to relbr70.

In the future to improve C module based on functionality of Python script.

[...]

in reply to:  1 comment:2 by martinl, 9 years ago

Resolution: fixed
Status: newclosed

Replying to martinl:

done in r63976:63983. If no objection I will backported to relbr70.

done r64002. Closing this ticket.

Note: See TracTickets for help on using tickets.