Changes between Version 2 and Version 3 of wxGUIDevelopment/GUIForPs.map


Ignore:
Timestamp:
02/03/11 22:44:43 (14 years ago)
Author:
hamish
Comment:

comment on ps.map issues

Legend:

Unmodified
Added
Removed
Modified

  • wxGUIDevelopment/GUIForPs.map

    v2 v3  
    33Prototype should be able to generate configuration file for `ps.map` based on [http://grass.osgeo.org/wiki/Psmap_simple_example#Simple_example example].
    44
    5 Inspiration: ArcGIS Layout mode, [http://www.qgis.org QGIS Print composer], [http://www.gvsig.org/web/ gvSig] (see also [http://www.google.cz/url?sa=t&source=web&cd=8&ved=0CFMQFjAH&url=http%3A%2F%2Fgvsig-desktop.forge.osor.eu%2Fdownloads%2Fpub%2Fdocuments%2Flearning%2Fgvsig-courses%2Fgvsig_des_1.1.x_u_en%2FgvSIG_workshop_OSGIS09.pdf&rct=j&q=gvsig%20map%20creating&ei=ck0kTfSTENSs8QPRrrW2Ag&usg=AFQjCNEx7iVQDwDHA2gRDFZxyf176VW-uQ&cad=rja workshop])
     5Please 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).
     6
     7Similar tools: [http://www.qgis.org QGIS Print composer], ArcGIS Layout mode, [http://www.gvsig.org/web/ gvSig] (see also [http://www.google.cz/url?sa=t&source=web&cd=8&ved=0CFMQFjAH&url=http%3A%2F%2Fgvsig-desktop.forge.osor.eu%2Fdownloads%2Fpub%2Fdocuments%2Flearning%2Fgvsig-courses%2Fgvsig_des_1.1.x_u_en%2FgvSIG_workshop_OSGIS09.pdf&rct=j&q=gvsig%20map%20creating&ei=ck0kTfSTENSs8QPRrrW2Ag&usg=AFQjCNEx7iVQDwDHA2gRDFZxyf176VW-uQ&cad=rja workshop])
     8
    69=== Prototype 1 ===
    710
    811 * Configuration dialog (paper format, map scale)
    9  * Implement `raster`, `colortable`, `vlines`, `vpoints`, `text`, `mapinfo` instructions
     12 * Implement the `raster`, `colortable`, `vlines`, `vpoints`, `vareas`(?), `text`, `mapinfo` instructions
    1013 * Interactive placement of the features
    11  * Draft mode
    12  * Generate configuration file
    13  * Create output using ps.map/ps.output
     14 * Draft mode (lower raster region resolution)
     15 * Generate ps.map configuration text file
     16 * Create output using ps.map
    1417
    1518=== Prototype 2 ===
    … …  
    1720 * !Draft/Preview mode
    1821 * Implement other instructions
     22 * If the `ps2pdf` program is installed offer a PDF output option
    1923
    2024=== Prototype 3 ===
    2125
    2226 * Read configuration files
     27 * As a parallel task, nice features from ps.output should be ported to ps.map. (contact HB)
    2328
    2429== ps.map bugs and inconsistencies ==
    2530
    26  * color should support RGB for all instructions
     31 * color should support RGB for all instructions (e.g. #192)
    2732 * common usage of ref points and units (absolute, relative)
     33  * 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.
     34  * 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.