Table of Contents
See also page at GRASS User Wiki.
Prototype should be able to generate configuration file for ps.map
based on example.
Please contact Hamish before getting started with the GUI front-end or before significant changes to ps.map back-end (as primary maintainer of that code).
Similar tools: QGIS Print composer, ArcGIS Layout mode, gvSig (see also workshop)
WxGUI Cartographic Composer
WxGUI Cartographic Composer (formerly called Hardcopy Map Output Utility) is available in GRASS 6.4.2+.
Prototype 1 (ready)
- Configuration dialog (paper format, map scale)
- Implement the
raster
,colortable
,vlines
,vpoints
,vareas
,vlegend
,scalebar
,text
,mapinfo
instructions - Interactive placement of the features
- Draft mode (lower raster region resolution)
- Draft/Preview mode
- Create PS output using ps.map
- EPS output option
- If the
ps2pdf
program is installed offer a PDF output option - Generate ps.map configuration text file
- Read configuration files
Known Issues
- map scale for ll projections (map window)
To be implemented
- Implement other instructions (
grid
,geogrid
,eps
,rectangle
,line
,point
,rgb
,region
, ...) - Add north arrow (
eps
instruction) - wxGUI integration (load maps from current map display - problem is that ps.map supports only 1 raster map)
- GUI preferences
- If
pstoimg
program is installed offer a PNG output option (latex2html linux package; uses ghostscript. Imagemagick'sconvert
does not do as nice a job AFAICT. Alt to try: Inkscape can do non-interactive conversions from the commandline.) - Snap to grid
- Alignment of map elements (expected problem: inaccurate size of map elements)
- latex support (
ps2eps
, it would add more possibilities for text customizing and solve the encoding problem) - As a parallel task, nice features from ps.output should be ported to ps.map. (contact HB)
Open Tickets
No results
Ps.map bugs and inconsistencies
- ps.map file must be in Latin 1 encoding (missing certain accented characters - #1349)
- mapinfo position (it aligns to the left side of map frame - #1333) and color (background color is not visible outside the map frame)
- color should support RGB for all instructions (e.g. #192)
- common usage of ref points and units (absolute, relative)
- The trouble is, percentage is given relative to the map box (which is sized and placed dynamically at run-time), while absolute is given relative to the page size. Although it may seem like it to the end user, the existing usage is not due to the programmer's whim, it is out of necessity. Note that to place relative decorations out-of-box, it is valid to go beyond 0-100% (e.g. -25%, 115%).
- The GUI has to do these calculations and feed ps.map what it wants in the form it wants. IMO it is not practical to have the python code mirror the C code's placement logic (a lot of work to mimic, then a lot of discipline to keep in sync). This may take a two-pass solution, e.g. a new ps.map flag which would output map box corners in inches and then exit. The GUI could then do the needed conversions between %, PostScript points(?), inches, cm, mm, or map coords. See wish #153.
Open Tickets
- #153
- ps.map: support for placement by % for decorations
- #192
- ps.map: geogrid RGB color and ellipsoid
- #250
- ps.map: connected lines for region instruction box
- #342
- ps.map: vpoints support for rgbcolumn as primary/secondary color
- #487
- ps.map: legend
- #874
- ps.map: submeter grid sizes
- #876
- ps.map rfe: new instruction to flood fill background color
- #900
- Transparent background on geogrid labels in psmap
- #901
- ps.map - comment command applies last location/font to all previous comments
- #1225
- Include support for kilometres / metres (re) as unit options, alongside of kilometers/meters (er)
- #1333
- ps.map mapinfo aligns horizontally to map
- #1350
- Ps.map mapinfo - show scale only
- #1356
- Ps.map vlines cwidth subcommand - can't choose other column than cat
- #1453
- ps.map: various enhancements
- #1688
- ps.map: adding negative scale and offset to vpoints plotting -- patch provided
- #1906
- Raster "title" longer than 100 characters segfaults ps.map -- Request to extend the field's capacity.
- #1907
- ps.map does not respect the drawing order of objects
- #1939
- Add line style option to vareas ps.map
- #2948
- ps.map output to stdout
- #3650
- Cartographic composer: scale and rotation options do not work for north arrow
- #3907
- ps.map: vlegend throws error
Note on Jachym's GUI for ps.map
- What happened to the wiki page content describing Jachym's existing ps.map GUI-frontend python prototype? check old versions of the main wxGUI wiki page.
- Jachym's prototype is not available at least for one year, so the info has been removed from wiki page...
- HB: Well, we could always ask him.. and I think I've got a copy of it sitting somewhere in a dusty corner as well. Let me know if you want me to look for it.
- ML: AFAIR this prototype has been very initial and Anna's work is much more robust at this time
- HB: Well, we could always ask him.. and I think I've got a copy of it sitting somewhere in a dusty corner as well. Let me know if you want me to look for it.
- Jachym's prototype is not available at least for one year, so the info has been removed from wiki page...
Last modified
11 years ago
Last modified on 02/05/14 20:30:32
Note:
See TracWiki
for help on using the wiki.