Re: [GRASS-user] error using v.in.gns
Updating on the svn, I get this configure error checking for gdal-config... /usr/bin/gdal-config configure: error: *** Unable to locate GDAL library Running ldconfig seems that my gdal libarary's are in the right place: [EMAIL PROTECTED]:~/source/develbranch_6$ sudo /sbin/ldconfig -p | grep gdal libgdal1.5.0.so.1 (libc6) => /usr/lib/libgdal1.5.0.so.1 libgdal1.5.0.so (libc6) => /usr/lib/libgdal1.5.0.so libgdal1.4.0.so.1 (libc6) => /usr/lib/libgdal1.4.0.so.1 cheers, maning On 7/2/08, Markus Neteler <[EMAIL PROTECTED]> wrote: > On Fri, Jun 27, 2008 at 4:26 AM, maning sambale > <[EMAIL PROTECTED]> wrote: >> I get thios message with v.in.gns: >> Converted 74072 place names. >> >> Scanning input for column types... >> >> Unparsable latitude value: LAT >> >> Unable to open vector map <[EMAIL PROTECTED]> on topology level 2 >> AFAIK is used the original data from downloaded from GNS Repo, sample >> data: > > Yesterday/today, in GRASS SVN (both 6.4.svn and 7.svn) some v.in.ascii > buffer overflow was fixed (for v.in.geonames which reads in potentially > better > quality data than v.in.gns). > > If you can, please update from SVN and try again. Hopefully fixed now. > > Markus > -- |-|--| | __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda | | '-._"7' |"Freedom is still the most radical idea of all" -N.Branden| | /'.-c |Linux registered user #402901, http://counter.li.org/ | | | /T |http://esambale.wikispaces.com| | _)_/LI |-|--| ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Output question - ps.map
Richard Chirgwin: > 2) Set the paper size to 200" x 200" AFAIU now, the issue is that the PDF output is compressed, not the PostScript output of ps.map, which should be a best resolution. The above trick is to get a create a resolution PDF, at the expense of incorrect paper size. ie fool acrobat reader. I have struggled with the same issue -- PDF conversion with the ps2pdf13 gs wrapper reduces the images to 72dpi. for the PS -> PDF conversion try: gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/printer \ -sOutputFile=out.pdf in.ps I tried with "-r1200" and "-r600x600" and "-density600" gs options but those had no discernible effect AFAICT*, although the file sizes changed a small amount (got smaller!). Probably due to the fact that I don't know ghostscript very well. "-dPDFSETTINGS=/printer" seemed to do the trick though. [*] ah ha!, -r1200 works, but only when you define -dPDFSETTINGS as well. now my 24M ps.map .ps file (1.6M gzipped) is a 1.1M PDF instead of a 600K one, and looks nicer too. (debian/etch gs version 8.15.3) http://milan.kupcevic.net/ghostscript_ps_pdf --snip-- PDF optimization level selection options -dPDFSETTINGS=/screen (screen-view-only quality — 72 dpi images) -dPDFSETTINGS=/ebook(low quality — 150 dpi images) -dPDFSETTINGS=/printer (high quality — 300 dpi images) -dPDFSETTINGS=/prepress (high quality with color preserving — 300 dpi images) -dPDFSETTINGS=/default (almost identical to /screen) --/snip-- Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Output question - ps.map
On 02/07/08 10:11, Hamish wrote: Richard Chirgwin: 2) Set the paper size to 200" x 200" AFAIU now, the issue is that the PDF output is compressed, not the PostScript output of ps.map, which should be a best resolution. The above trick is to get a create a resolution PDF, at the expense of incorrect paper size. ie fool acrobat reader. I have struggled with the same issue -- PDF conversion with the ps2pdf13 gs wrapper reduces the images to 72dpi. for the PS -> PDF conversion try: gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/printer \ -sOutputFile=out.pdf in.ps I tried with "-r1200" and "-r600x600" and "-density600" gs options but those had no discernible effect AFAICT*, although the file sizes changed a small amount (got smaller!). Probably due to the fact that I don't know ghostscript very well. "-dPDFSETTINGS=/printer" seemed to do the trick though. Normally, you should actually be able to give this option directly to ps2pdf: http://pages.cs.wisc.edu/~ghost/doc/AFPL/6.50/Ps2pdf.htm Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Output question - ps.map
On Wed, Jul 2, 2008 at 10:11 AM, Hamish <[EMAIL PROTECTED]> wrote: > for the PS -> PDF conversion try: > > gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/printer \ > -sOutputFile=out.pdf in.ps maybe there's something interesting also in here: http://www.grassbook.org/neteler/highres_pdf.html Creating High Resolution PDF files for book production with Open Source tools Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Gdal-config with 6.4svn
Hello everybody. Building today svn checkout, I have this error with gdal-config: checking whether to use GDAL... yes checking for gdal-config... /usr/bin/gdal-config configure: error: *** Unable to locate GDAL library. 3 days ago, it built with no problem. The system is an Ubuntu Hardy with Jachym's repository Gdal installed: libgdal1-1.4.0 libgdal1-1.4.0-grass libgdal1-1.5.0 libgdal1-dev wich gdal-config: /usr/bin/gdal-config gdal related files in /usr/lib/ libgdal1.4.0.so.1 libgdal1.4.0.so.1.11.4 libgdal1.5.0.a libgdal1.5.0.la libgdal1.5.0.so libgdal1.5.0.so.1 libgdal1.5.0.so.1.12.1 gdal-config --version: 1.5.1 Thanks for your help Luca -- View this message in context: http://www.nabble.com/Gdal-config-with-6.4svn-tp18234142p18234142.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Gdal-config with 6.4svn
Hi, I'm also experiencing the same problem from todays's svn checkout I'm using ubuntu hardy. I have the same configuration with dokotoreas cheers, maning On 7/2/08, doktoreas <[EMAIL PROTECTED]> wrote: > > Hello everybody. > > Building today svn checkout, I have this error with gdal-config: > checking whether to use GDAL... yes > checking for gdal-config... /usr/bin/gdal-config > configure: error: *** Unable to locate GDAL library. > > 3 days ago, it built with no problem. > > The system is an Ubuntu Hardy with Jachym's repository > > Gdal installed: > libgdal1-1.4.0 > libgdal1-1.4.0-grass > libgdal1-1.5.0 > libgdal1-dev > > wich gdal-config: > /usr/bin/gdal-config > > gdal related files in /usr/lib/ > libgdal1.4.0.so.1 libgdal1.4.0.so.1.11.4 libgdal1.5.0.a > libgdal1.5.0.la libgdal1.5.0.so libgdal1.5.0.so.1 > libgdal1.5.0.so.1.12.1 > > gdal-config --version: > 1.5.1 > > Thanks for your help > Luca > > > -- > View this message in context: > http://www.nabble.com/Gdal-config-with-6.4svn-tp18234142p18234142.html > Sent from the Grass - Users mailing list archive at Nabble.com. > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user > -- |-|--| | __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda | | '-._"7' |"Freedom is still the most radical idea of all" -N.Branden| | /'.-c |Linux registered user #402901, http://counter.li.org/ | | | /T |http://esambale.wikispaces.com| | _)_/LI |-|--| ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Gdal-config with 6.4svn
On Wed, Jul 2, 2008 at 12:13 PM, doktoreas <[EMAIL PROTECTED]> wrote: > > Hello everybody. > > Building today svn checkout, I have this error with gdal-config: > checking whether to use GDAL... yes > checking for gdal-config... /usr/bin/gdal-config > configure: error: *** Unable to locate GDAL library. > > 3 days ago, it built with no problem. apparently you updated in those 3 days, see below: > The system is an Ubuntu Hardy with Jachym's repository > > Gdal installed: > libgdal1-1.4.0 > libgdal1-1.4.0-grass > libgdal1-1.5.0 > libgdal1-dev personally, I would not mix those versions. One version should be enough. > gdal related files in /usr/lib/ > libgdal1.4.0.so.1 libgdal1.4.0.so.1.11.4 libgdal1.5.0.a > libgdal1.5.0.la libgdal1.5.0.so libgdal1.5.0.so.1 > libgdal1.5.0.so.1.12.1 > > gdal-config --version: > 1.5.1 As you can see, gdal-config points to a nonexisting library version. It's a packager error, not a GRASS error. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Gdal-config with 6.4svn
Markus Neteler OSGeo wrote: > > >> The system is an Ubuntu Hardy with Jachym's repository >> >> Gdal installed: >> libgdal1-1.4.0 >> libgdal1-1.4.0-grass >> libgdal1-1.5.0 >> libgdal1-dev > > personally, I would not mix those versions. One version should > be enough. > > Yes, you are right. The 1.4.0 comes with qgis-grass-plugin from Tim Ubuntu repository. Hopes to see just one repository for Ubuntu (Osgeo?) :) Thanks for all your suggestion. Bye Luca -- View this message in context: http://www.nabble.com/Gdal-config-with-6.4svn-tp18234142p18234719.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] error using v.in.gns
maning sambale wrote: > Updating on the svn, I get this configure error > checking for gdal-config... /usr/bin/gdal-config > configure: error: *** Unable to locate GDAL library Look in the config.log file for relevant error messages. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Poseidon Linux 3.0
Hi Folks, Poseidon Linux is here! For GIS people it comes with: GIS/Mapping: SPRING 4.3.3 GRASS 6.2.1 + plugins GDAL 1.4.4 and OGR 1.4.4 GMT 4.2.0 PROJ 4.6 QGIS 0.10 + plugins (including GRASS Plugin) Terraview 3.2 Plus MB System 5.1.0 GPS Manager GPS Drive Mapserver 5.0 + Pmapper 3.2 (pmapper don't work running from live-DVD, just work when installed on a PC) For more details please visit our site: http://sites.google.com/site/poseidonlinux/Home Yes, I know... there is GRASS 6.3 out... but to minimize download time for users we plan to release each 3-4 months a maintenance version with updates (normal/security) and a few upgrades... and GRASS is already our list. Best regards, Christian ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] ps.map dilemma
Hi all, I come here with a question/dilemma... Why ps.map lacks so much user support? A lot of people know about GRASS all over the world, but nearly nobody use it, since nearly any software in the world is less difficult to produce maps. GRASS is a wonderful tool for analysis, but it fails to produce the ultimate result: a map. Even GMT is widely used, because a lot of people SHARE the scripts, and there is the "GMT cookbook" on the official website. But for GRASS everybody can see some good examples here: http://grass.itc.it/screenshots/cartography.php But nearly nobody share the scripts to make these wonderful maps... and you know, a lot of people will never "lose" their time trying to figure out how ps.map works just using the man page. Ps.map also needs a "cookbook" in the future. And at: http://grass.osgeo.org/wiki/Ps.map_scripts Ok, we have finally a few scripts, but poorly documented. I use GRASS since 2001, it is nearly a complete solution for GIS (in my opinion), but ps.map was always the weak point (in my opinion too)... normally I need to export all my region/data to GMT/ArcView/Surfer to make the final map. For example, my latest work was two pages for an atlas for National Geographic Brasil/Brazil, with a work that I started developing with GRASS since 2001... but guess if GRASS was used for the final map? This is a shame for me. :-( I am aware of g-ps.map (the alternate GUI for ps.map), but will take sometime until it became truth. So... If there someone who wants to share his knowlegde, I can at least help to compile and document the material to prepare a real "ps.map cookbook" on the GRASS-Wiki. Who will join me, and share some material? Best regards, Christian -- Christian dos Santos Ferreira Oceanographer Coordinator of Poseidon Linux QGIS translator (EN to Brazilian Portuguese) GRASS user since 2001 and "philosopher" for features ;-) ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
RE: [GRASS-user] ps.map dilemma
Good questioning. My solution is that I use Qgis with PDF output to produce the ilustration part of the map and them make the final product with all the legend and titles with Scribus. Pablo Torres CarreiraINCRA/Araraquara - Brazil. > Date: Wed, 2 Jul 2008 20:17:18 +0200> From: [EMAIL PROTECTED]> To: > grass-user@lists.osgeo.org> Subject: [GRASS-user] ps.map dilemma> > Hi all,> > > > I come here with a question/dilemma...> > Why ps.map lacks so much user > support?> > A lot of people know about GRASS all over the world, but nearly > nobody> use it, since nearly any software in the world is less difficult to> > produce maps.> > GRASS is a wonderful tool for analysis, but it fails to > produce the> ultimate result: a map.> > Even GMT is widely used, because a > lot of people SHARE the scripts,> and there is the "GMT cookbook" on the > official website.> > But for GRASS everybody can see some good examples > here:> > http://grass.itc.it/screenshots/cartography.php> > But nearly nobody > share the scripts to make these wonderful maps...> and you know, a lot of > people will never "lose" their time trying to> figure out how ps.map works > just using the man page.> > Ps.map also needs a "cookbook" in the future.> > > And at: http://grass.osgeo.org/wiki/Ps.map_scripts> > Ok, we have finally a > few scripts, but poorly documented.> > I use GRASS since 2001, it is nearly a > complete solution for GIS (in> my opinion), but ps.map was always the weak > point (in my opinion> too)... normally I need to export all my region/data > to> GMT/ArcView/Surfer to make the final map.> > For example, my latest work > was two pages for an atlas for National> Geographic Brasil/Brazil, with a > work that I started developing with> GRASS since 2001... but guess if GRASS > was used for the final map?> > This is a shame for me. :-(> > I am aware of > g-ps.map (the alternate GUI for ps.map), but will take> sometime until it > became truth.> > So... If there someone who wants to share his knowlegde, I > can at> least help to compile and document the material to prepare a real> > "ps.map cookbook" on the GRASS-Wiki.> > Who will join me, and share some > material?> > Best regards,> Christian> > --> Christian dos Santos Ferreira> > Oceanographer> Coordinator of Poseidon Linux> QGIS translator (EN to > Brazilian Portuguese)> GRASS user since 2001 and "philosopher" for features > ;-)> ___> grass-user mailing > list> grass-user@lists.osgeo.org> > http://lists.osgeo.org/mailman/listinfo/grass-user _ Receba GRÁTIS as mensagens do Messenger no seu celular quando você estiver offline. Conheça o MSN Mobile! http://mobile.live.com/signup/signup2.aspx?lc=pt-br___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] ps.map dilemma
On Wednesday 02 July 2008, Christian Ferreira wrote: > Hi all, > > > I come here with a question/dilemma... > > Why ps.map lacks so much user support? Good question. > A lot of people know about GRASS all over the world, but nearly nobody > use it, since nearly any software in the world is less difficult to > produce maps. > > GRASS is a wonderful tool for analysis, but it fails to produce the > ultimate result: a map. Partially by design, GRASS is primarily geared toward data processing and analysis. > Even GMT is widely used, because a lot of people SHARE the scripts, > and there is the "GMT cookbook" on the official website. Glad you mention GMT. It could potentially become what ps.map isn't quite once the python bindings for both GMT and GRASS are a little more mature. > But for GRASS everybody can see some good examples here: > > http://grass.itc.it/screenshots/cartography.php > > But nearly nobody share the scripts to make these wonderful maps... > and you know, a lot of people will never "lose" their time trying to > figure out how ps.map works just using the man page. > > Ps.map also needs a "cookbook" in the future. > > And at: http://grass.osgeo.org/wiki/Ps.map_scripts > > Ok, we have finally a few scripts, but poorly documented. A ps.map cookbook would be nice- would you like to start it? I imagine that you will get a couple good ones after posting this. Once you have them, along with a screen shot, you could post the annotated examples on the wiki. > I use GRASS since 2001, it is nearly a complete solution for GIS (in > my opinion), but ps.map was always the weak point (in my opinion > too)... normally I need to export all my region/data to > GMT/ArcView/Surfer to make the final map. > > For example, my latest work was two pages for an atlas for National > Geographic Brasil/Brazil, with a work that I started developing with > GRASS since 2001... but guess if GRASS was used for the final map? > > This is a shame for me. :-( It is a shame. GMT is usually my map-making favorite. Alternatively GRASS + GMT + Inkscape / Illustrator. > I am aware of g-ps.map (the alternate GUI for ps.map), but will take > sometime until it became truth. > > So... If there someone who wants to share his knowlegde, I can at > least help to compile and document the material to prepare a real > "ps.map cookbook" on the GRASS-Wiki. > > Who will join me, and share some material? > > Best regards, > Christian Good luck, Dylan > -- > Christian dos Santos Ferreira > Oceanographer > Coordinator of Poseidon Linux > QGIS translator (EN to Brazilian Portuguese) > GRASS user since 2001 and "philosopher" for features ;-) > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] ps.map dilemma
Hi, 2008/7/2 Dylan Beaudette <[EMAIL PROTECTED]>: >> Why ps.map lacks so much user support? > > Good question. I am planning to design the GUI for ps.map as a part of wxGUI [1], should be done in the next few mouths. Martin [1] http://grass.osgeo.org/wiki/WxPython-based_GUI_for_GRASS#GUI_for_ps.map -- Martin Landa * http://gama.fsv.cvut.cz/~landa * ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] ps.map dilemma
Martin Landa wrote: > >> Why ps.map lacks so much user support? > > > > Good question. > > I am planning to design the GUI for ps.map as a part of wxGUI [1], > should be done in the next few mouths. FWIW, I'm planning to remove ps.map from 7.x. Equivalent functionality will be available through d.* commands. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] ps.map dilemma
Hi, 2008/7/2 Glynn Clements <[EMAIL PROTECTED]>: > > Martin Landa wrote: > >> >> Why ps.map lacks so much user support? >> > >> > Good question. >> >> I am planning to design the GUI for ps.map as a part of wxGUI [1], >> should be done in the next few mouths. > > FWIW, I'm planning to remove ps.map from 7.x. > > Equivalent functionality will be available through d.* commands. I know, GUI for ps.map is just temporary solution (at least for grass6), some notes here http://grass.osgeo.org/wiki/WxPython-based_GUI_for_GRASS#Direct_printing Martin -- Martin Landa * http://gama.fsv.cvut.cz/~landa * ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] ps.map dilemma
[moving this to the grass-dev list..] Glynn: > FWIW, I'm planning to remove ps.map from 7.x. > > Equivalent functionality will be available through d.* > commands. any reason other than redunancy? It is highly useful to some and currently outpaces d.* for quality. Duplicate functionality is only a reason if: a) it does a worse job for the task (debatable->personal choice), or b) it distracts the developer pool too much from working on new things. c) adds too much bulk none of which are the case, IMO. it does a good job and the code hardly changes (I think I'm the only one who actually works on it). It doesn't touch anything outside its directory and the code is a fairly small portion of the overall tarball. i.e., what is the cost of leaving it there for those who depend on it? AFAICS the primary thing it lacks is a nice GUI frontend composer. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-dev] Re: [GRASS-user] ps.map dilemma
Hamish wrote: > > FWIW, I'm planning to remove ps.map from 7.x. > > > > Equivalent functionality will be available through d.* > > commands. > > any reason other than redunancy? Partly redundancy, mainly to ensure that people complain about any deficiencies with the alternative. > It is highly useful to some and currently outpaces d.* for quality. Just about anything currently outpaces d.* for quality. That will change once the graphics architecture is re-written. > Duplicate functionality is only a reason if: > > a) it does a worse job for the task (debatable->personal choice), or > b) it distracts the developer pool too much from working on new things. > c) adds too much bulk The main reasons are b) and: d) it distracts the user pool from testing new things. Essentially, if ps.map is left, it will "steal" both developers and testers from d.*, which (AFAIK) is still the primary mechanism for graphics. [Unless you're planning on entirely replacing d.* with ps.map, in which case ps.map is going to have to become a great deal simpler (code-wise) and more flexible.] -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-dev] Re: [GRASS-user] ps.map dilemma
Glynn: > > > FWIW, I'm planning to remove ps.map from 7.x. > > > > > > Equivalent functionality will be available through d.* > > > commands. Hamish: > > any reason other than redunancy? Glynn: > Partly redundancy, mainly to ensure that people complain > about any deficiencies with the alternative. ok. As d.* is the main track and ps.map is mostly a periphery I wouldn't get too worried about that. But I really have no idea how many people use ps.map versus d.out.file/Cairo, or the PNG driver, or QGIS, or .. You are correct in that I expect the hard core ps.map users will probably be among the better/noisier testers for the next generation d.* PS driver. FWIW once grass7 goes mainstream if I still need ps.map for work, I'll port it (can't afford downtime, etc). The question then becomes whether to include it [back] in the main distro or keep it as an addon. I don't see much point in debating that too much until both grass7 and the port actually exist. wrt ps.map usability: In my experience, once you have spent the time to learn how to use it, ps.map rocks for publication quality stuff- where you don't mind throwing in a bit more time. Maybe "oh, just edit the PostScript file by hand to fix that" is a bit over the top, but part of my point in doing that is to show that it really isn't that scary, it's just a text file with commands in it and the user is in charge. I will try and add a few more tips&hints onto the wiki page. wrt GMT: perhaps the output is more refined, but the learning curve and command line comfort is about the same and the integration not as good so far. I look forward to seeing improved *.out.gmt scripts and hope the ones we have now can be consolidated. Maybe a nice (albeit perhaps off-topic enough to not make the cut) Google Summer of Code project for next year would be to improve GRASS<->GMT flow. enjoys choices and working on clunky old sports cars, Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-dev] Re: [GRASS-user] ps.map dilemma
Hamish ha scritto: > enjoys choices and working on clunky old sports cars, talking about choices and duplication, please note that work is also well underway for a new printing mechanism for qgis https://trac.osgeo.org/qgis/browser/branches/advanced_printing_branch due probably in a month or two, I guess. all the best. pc -- Paolo Cavallini, see: * http://www.faunalia.it/pc * ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
