Hi Hamish,
I make many changes to the files in ps.map and to avoid conflict with this
standard command I move my custom ps.map to ps3.map.
This ps3.map compile whithout errors in grass6_devel (6.5.svn). Before I send
this addons (or substitute of ps.map) I want debug and improve some part of
code but I like know the opinion and suggestions to improve the command
needed to draw quality maps whitout any other extern software.
The main improvements are:
1. All font has color.
2. All colors are R:G:B (accept named and none, of course).
3. Many dimensions accept unit (milimeters, centimeters and inches, default
points).
- Grid: option of fcolor to look like as ps3_map_grid.jpg (with a border of 2
points)
- Areas: it is possible define style of line to look as 'Geology-262' in
ps3_map_legend.jpg
- Lines: it is possible define style to hline to look as 'Railroads' in
ps3_map_legend.jpg
- Scalebar: now with fcolor to look as ps3_map_scalebar.jpg
- rlegend and vlegend: with frame and multicolumns work well as
ps3_map_legend2.jpg
... and more.
Also I send to Grass-Addons server (GRASS7 subdir) i.landsat.toar and
i.topo.corr; They compile without errors in GRASS7 but I can not test because
teh compilation of GRASS_7 give me errors in many files, mainly because:
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_gets'
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to
`G_get_ask_return_msg'
collect2: ld returned 1 exit status
Thank for suggestions and comments
--
E. Jorge Tizado
Dpto. Biodiversity and Environmental Management
University of León, Spain
(attachments)
Hi,
this looks great! Is there support for i18n as well?
Jachym
E. Jorge Tizado píše v Ne 15. 02. 2009 v 15:07 +0100:
Hi Hamish,
I make many changes to the files in ps.map and to avoid conflict with this
standard command I move my custom ps.map to ps3.map.
This ps3.map compile whithout errors in grass6_devel (6.5.svn). Before I send
this addons (or substitute of ps.map) I want debug and improve some part of
code but I like know the opinion and suggestions to improve the command
needed to draw quality maps whitout any other extern software.
The main improvements are:
1. All font has color.
2. All colors are R:G:B (accept named and none, of course).
3. Many dimensions accept unit (milimeters, centimeters and inches, default
points).
- Grid: option of fcolor to look like as ps3_map_grid.jpg (with a border of 2
points)
- Areas: it is possible define style of line to look as 'Geology-262' in
ps3_map_legend.jpg
- Lines: it is possible define style to hline to look as 'Railroads' in
ps3_map_legend.jpg
- Scalebar: now with fcolor to look as ps3_map_scalebar.jpg
- rlegend and vlegend: with frame and multicolumns work well as
ps3_map_legend2.jpg
... and more.
Also I send to Grass-Addons server (GRASS7 subdir) i.landsat.toar and
i.topo.corr; They compile without errors in GRASS7 but I can not test because
teh compilation of GRASS_7 give me errors in many files, mainly because:
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_gets'
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to
`G_get_ask_return_msg'
collect2: ld returned 1 exit status
Thank for suggestions and comments
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://les-ejk.cz/pgp/JachymCepicky.pgp
Joining the previous comments, I think too that this looks really great! I use ps.map regularly and was sometimes missing these features.
Sticking to grass command naming conventions, this enhanced version of ps.map may better be called ps.map2 and not ps3.map, unless there is new PostScript3 wizardry in there, not only new options.
In the current ps.map, the type of the colortable drawn for rasters is dependent on the type of the raster. CELL rasters get a discrete colortable with labelled categories, FCELL and DCELL maps get a color gradient. Sometimes a DEM is of type CELL, then I would like to have a colortable with gradient, not discrete categories. At least I would like to have the choice. I'm using my own hackish workaround, but maybe you could do that properly, leaving the defaults as they are now? Just a suggestion.
Regards,
Markus M
E. Jorge Tizado wrote:
Hi Hamish,
I make many changes to the files in ps.map and to avoid conflict with this standard command I move my custom ps.map to ps3.map.
This ps3.map compile whithout errors in grass6_devel (6.5.svn). Before I send this addons (or substitute of ps.map) I want debug and improve some part of code but I like know the opinion and suggestions to improve the command needed to draw quality maps whitout any other extern software.
The main improvements are:
1. All font has color.
2. All colors are R:G:B (accept named and none, of course).
3. Many dimensions accept unit (milimeters, centimeters and inches, default points).
- Grid: option of fcolor to look like as ps3_map_grid.jpg (with a border of 2 points)
- Areas: it is possible define style of line to look as 'Geology-262' in ps3_map_legend.jpg
- Lines: it is possible define style to hline to look as 'Railroads' in ps3_map_legend.jpg
- Scalebar: now with fcolor to look as ps3_map_scalebar.jpg
- rlegend and vlegend: with frame and multicolumns work well as ps3_map_legend2.jpg
... and more.
Also I send to Grass-Addons server (GRASS7 subdir) i.landsat.toar and i.topo.corr; They compile without errors in GRASS7 but I can not test because teh compilation of GRASS_7 give me errors in many files, mainly because:
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_gets'
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_get_ask_return_msg'
collect2: ld returned 1 exit status
Thank for suggestions and comments
E. Jorge Tizado wrote:
I make many changes to the files in ps.map and to avoid conflict with this
standard command I move my custom ps.map to ps3.map.
This ps3.map compile whithout errors in grass6_devel (6.5.svn). Before I send
this addons (or substitute of ps.map)
Whatever you do, don't add this to SVN (either addons or grass) as if
it is new code, as that will make it impossible to automatically merge
any changes.
Instead, make a copy of the version of ps.map from which you started,
using "svn copy", then overwrite that copy with your updated version.
Do not overwrite any other version with your changes.
If you've forgotten which version you started from, you will need to
manually merge your changes with any changes which have been made and
committed by other developers.
Also I send to Grass-Addons server (GRASS7 subdir) i.landsat.toar and
i.topo.corr; They compile without errors in GRASS7 but I can not test because
teh compilation of GRASS_7 give me errors in many files, mainly because:
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_gets'
/usr/local/grass-6.4.0svn/lib/libgrass_I.so: undefined reference to `G_get_ask_return_msg'
collect2: ld returned 1 exit status
Something is linking against 6.4.0 libraries. First, ensure that your
GDAL library is built without GRASS support.
--
Glynn Clements <glynn@gclements.plus.com>
E. Jorge Tizado pisze:
<snip>
Also I send to Grass-Addons server (GRASS7 subdir) i.landsat.toar and
i.topo.corr; They compile without errors in GRASS7 but I can not test because teh compilation of GRASS_7 give me errors in many files,
mainly because:
</snip>
Jorge,
Is it absolutely necessary to fork the 2 addons?
http://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.landsat.toar
http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.landsat.toar
http://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.topo.corr
http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.topo.corr
That makes it harder to maintain them.
--
Maciej Sieczka
www.sieczka.org