WxGUI Cartographic Composer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Back to [[wxGUI]] | Back to [[wxGUI]] | ||
For development issues see '''[http://trac.osgeo.org/grass/wiki/wxGUIDevelopment/GUIForPs.map Trac page]'''. | |||
{{cmd|ps.map}} (see also {{AddonCmd|ps.output}}) is a ''cartographic composer'', intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls. | {{cmd|ps.map}} (see also {{AddonCmd|ps.output}}) is a ''cartographic composer'', intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls. | ||
Revision as of 12:28, 9 January 2011
Back to wxGUI
For development issues see Trac page.
ps.map (see also ps.output) is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a Print button for the maps currently displayed in the map canvas, that will need it own controls.
The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript PDF output directly. Loading a ps.map control file is harder and can happen later.
- Start with most important mapping instructions
- paper
- scale
- maploc
- rast
- vects
- grids
- scalebar
- mapinfo
- text labels
Outputs
- ps.map instructions file
- PostScript file (ps.map instructions tmp file)
- lpr [PostScript tmp file]
- PDF File [PostScript tmp file]
Inputs
- Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.