[GRASS-dev] [GRASS GIS] #2047: GRASS doesn't build on FreeBSD

[GRASS GIS]

#2047: GRASS doesn't build on FreeBSD
-+--
 Reporter:  lbartoletti  |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:  6.4.3
Component:  Compiling| Version:  6.4.3 RCs
 Keywords:   |Platform:  Other Unix   
  Cpu:  x86-64   |  
-+--
 We have an error "__va_list" into gisdefs.h

 See the log and the FreshPorts' info
 http://www.freshports.org/databases/grass

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #612: g.html2man: parsing leads to man page errors

[GRASS GIS]

#612: g.html2man: parsing leads to man page errors
--+-
 Reporter:  hamish|   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  6.5.0
Component:  Docs  | Version:  svn-develbranch6 
 Keywords:  g.html2man, utf8  |Platform:  Unspecified  
  Cpu:  All   |  
--+-
Changes (by hamish):

  * keywords:  g.html2man => g.html2man, utf8


Comment:

 (G6.x only)
 re. `man` treating flag names as hyphens and breaking them for cut & paste
 when utf8 is used, here's some post-processing sed regex to catch many of
 them:

 {{{
 sed -i -e 's/\([ ([]\)-\([a-z]\)/\1\\-\2/g' \
-e 's/\([ []\)--\([a-z]\)/\1\\-\\-\2/g' \
-e 's/\[-\\fB/[\\-\\fB/' \
-e 's/\[--\\fB/[\\-\\-\\fB/g' \
-e 's/"\\fB-\([a-zA-Z0-9]\)/"\\fB\\-\1/' \
-e 's/"\\fB--\([a-zA-Z0-9]\)/"\\fB\\-\\-\1/' \
"$man_page"
 }}}


 Hamish

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] 4th GRASS GIS Community Sprint in Prague: Exciting achievements!

[Markus Neteler]

The GRASS GIS community is delighted to present the outcome of the *4th
Community Sprint* that took place in a warm and sunny *Prague, Czech
Republic, from July 12 to July 18, 2013*. The event happened after the
Geoinformatics
conferenceat
the Czech Technical University in Prague. The Community Sprint was
once
more a creative gathering of both long-term and new developers, as well as
users.

This meeting was held in the light of *30 YEARS OF GRASS
GIS*
!

[image: 30 YEARS OF GRASS GIS!] 

We wish to cordially thank the *Department of Mapping and Cartography*,
Faculty of Civil Engineering,
*Czech Technical University* in Prague for hosting and technical support.
In particular, we gratefully acknowledge our *association sponsors
OSGeo
and FOSSGIS e.V. *, and many *individual
donors*: *Peter
Löwe, Andrea Borruso, Massimo Di Stefano, Alessandro Sarretta, Joshua
Campbell, Andreas Neumann, Jon Eiriksson, Luca Casagrande, Karyn O Newcomb,
Holger Naumann, Anne Ghisla, Helena Mitasova and Lubos Mitas, Dimitris
Tamp, Mark Seibel, Markus Metz, and Tawny Gapinski*. These financial
contributions were used to cover costs such as meals and to help reducing
travelling and accommodation expenses for participants with far arrival who
came on own expenses.

Developers and users who joined the event *came from various countries like
Italy, Czech Republic, Slovak Republic, Poland, Sri Lanka/France, USA
*and*Germany
*.

The Community Sprint focused on:

   - testing/bugfixing of the upcoming GRASS 7
version
   ,
   - backporting new functionalities to the stable GRASS 6.4 series,
   - testing/bugfixing related to Mac OS X, MS-Windows and Linux,
   - presenting and developing the new Temporal GIS Algebra in GRASS
7
   ,
   - connecting GRASS 7 with the planetary science software
ISIS
   ,
   - discussing integration with rasdaman.org
software, a powerful multidimensional raster
processor,
   - creating 3D vector test data for 3D interpolation,
   - discussing vector conflation,
   - discussing Bundle Block Adjustments,
   - presenting the state of image processing in GRASS
7,
   and discussing its future,
   - improving documentation, with focus on image processing and Temporal
   GIS Algebra,
   - developing/refactoring and bugfixing several wxGUI's components,
   - further developing customizable wxGUI
Toolboxesconcept,
   - improving translationin
Polish and Romanian languages,
   - fixing v.krige in GRASS7 and proposing merge with the recently
   developed v.kriging module,
   - meeting between Google Summer of Code
2013mentor
and students.

A lot of topic oriented discussions happened among small groups of
participants: for more detailed information, please visit the Wiki pages at
http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2013 and the
related discussion page at
http://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2013

*About GRASS GIS*
The Geographic Resources Analysis Support System, commonly referred to as GRASS
GIS , is an Open Source Geographic Information
System providing powerful raster, vector and geospatial processing
capabilities in a single integrated software suite. GRASS GIS includes
tools for spatial modeling, visualization of raster and vector data,
management and analysis of geospatial data, and the processing of satellite
and aerial  imagery. It also provides the capability to produce
sophisticated presentation graphics and hardcopy maps. GRASS GIS has been
translated into about twenty languages and supports a huge array of data
formats. It is distributed
freelyunder the terms of
the GNU General Public License (GPL). GRASS GIS is an
official project of the Open Source Geospatial
Foundation(OSGeo).

*GRASS GIS Development Team, July 2013*

EN:
http://grass.osgeo.org/news/26/15/4th-Community-Sprint-Exciting-achievements/
DE: http://www.fossgis.de/wiki/Bericht_GRASS_GIS_Community_Sprint_2013
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Custom GRASS command line prompt

[Hamish]

Nikos:
> Just a thought: would be nice to customise as to have a top or a
> bottom "info-line", or two "info-lines" below 80 chars (what's the
> max that should be respected?),

see MarkusN's "[Raster MASK present]" command prompt magic using

"$PROMPT_COMMAND" (set in $GISBASE/etc/Init.sh).

> or stuff can go in the terminals title-bar -- this, I
> guess, works easily with a few terminals like xterm.

see $GISBASE/etc/grass-run.sh


re. using terminal colors, a web-search finds a number of pages like this:
http://superuser.com/questions/270214/how-can-i-change-the-colors-of-my-xterm-using-ansi-escape-sequences
# putting that into practice:
CLEAR='\e[2J\e[1;1H'
FG_CYAN='\e[36m'
BG_BLUE='\e[44m'

echo -en "${FG_CYAN}${BG_BLUE}$CLEAR"


# example of adding an RGB border color with a #RRGGBB code:
echo -ne "\033]11;#53186f\007"

for me, xfce4-terminal and rxvt accepted the old EGA colors for fore/background,
but not the full RGB border -- I had to use xterm to see that work. 

But I think changing the border with a RGB color per mapset or location would
scale better if you were having a different color for each mapset/location. 
Or, for the "MASK present" I'd prefer a red terminal border to the extra line
on the command prompt, so it might be nice to search out what the different
escape codes for gnome-terminal et al. might be.


Hamish

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2039: Startup Error

[GRASS GIS]

#2039: Startup Error
--+-
 Reporter:  akdeakin  |   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  6.4.4
Component:  Startup   | Version:  6.4.3 RCs
 Keywords:  wingrass  |Platform:  MSWindows 7  
  Cpu:  x86-64|  
--+-

Comment(by hamish):

 Hi,

 it sounds like you have most of the runtime redistributables in place,
 msvcr100.dll is a new one though. When you installed did you tick the box
 to install "Important Microsoft Redistributable Libraries" on the same
 page in the installer as the option to download the sample datasets? Even
 though you probably have most already it might be a good idea to try that
 anyway.

 To see what the error message is you have to stop the window from closing
 so fast once it exits. Perhaps the easiest way around that is to open a
 command window (start button then type "cmd" into the search and click in
 the "C:\>" icon) and from the DOS prompt change into the grass startup
 directory then run the startup command by hand.

 To make this easy right click on the grass desktop icon and copy and paste
 out the "start from" directory to the terminal with "cd
 c:\path\goes\here", I think that points to the c:\grass64\msys dir (for
 you) but I'm not sure it actually matters.

 Then cut and paste the actual startup command into the command terminal,
 and wait to see the error.

 Is it still "LOCATION_NAME not set"? (which should be recoverable) Do any
 of the other grass session menu items work from the grass menu in start
 menu -> all programs? For example, if you can start from the text based
 command session, maybe that fixes the broken/missing "grassrc6" last-
 settings file which remembers the LOCATION_NAME from the previous session.
 ?


 thanks,
 Hamish

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r57291: configure.in: disable pwd -W (WinGRASS)

[Helmut Kudrnovsky]

Martin Landa wrote:

>When spending time on that and other
>fucking Windows issues

thanks a lot for your attempt to tame the beast!!



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/r57291-configure-in-disable-pwd-W-WinGRASS-tp5069162p5069229.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r57291: configure.in: disable pwd -W (WinGRASS)

[Hamish]

Hamish:
>> re r57291, it's not safe to modify core files after the last RC :-(
Martin:
> but sure, you are right. It was not a good idea.

but seems no harm done :)


It's an interesting conflict -- on one side if we know a fix we wouldn't want
to release without it, on the other side is the law of unintended consequences
resetting the testing clock to zero after any change.

Then add to that taking good advantage of the focused productivity of everyone
pushing to get the release out the door while at the same time not wanting
to raise any dust into the air just prior to release.

it's a delicate balance..


best,
Hamish

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Custom GRASS command line prompt

[Nikos Alexandris]

Nikos:

> > Now it appears like:  "G 7.0.svn (utm_37s/post):~ >".  My understanding is
> > that I probably need to edit the file:
> > grass7_trunk/dist.x86_64-unknown-linux-gnu/grass70.tmp


Hamish:

> I'd suggest to put the change in ~/.grass.bashrc instead.


Nikos:

> Hamish,
> 
> don't want to waist your time, but I have put soemthing like
> 
> SHORT_VER=`echo "$GRASS_VERSION" | cut -f1,2 -d. | sed -e 's/\.//'`
> GLOCATION=`echo "${LOCATION_NAME}"`
> GMAPSET=`echo "${MAPSET}"`
> export PS1='G$SHORT_VER ${GLOCATION}/${GMAPSET}:\w > '
> export PROMPT_DIRTRIM=2
> 
> which doesn't work! :-/
> 
> Where should $LOCATION_NAME, $MAPSET be fed from?

I got it...

GLOCATION=`g.gisenv get="LOCATION_NAME"`
GMAPSET=`g.gisenv get="MAPSET"`

Nikos


___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Custom GRASS command line prompt

[Nikos Alexandris]

Nikos:

> > Now it appears like:  "G 7.0.svn (utm_37s/post):~ >".  My understanding is
> > that I probably need to edit the file:
> > grass7_trunk/dist.x86_64-unknown-linux-gnu/grass70.tmp

Hamish:

> I'd suggest to put the change in ~/.grass.bashrc instead.

Hamish,

don't want to waist your time, but I have put soemthing like

SHORT_VER=`echo "$GRASS_VERSION" | cut -f1,2 -d. | sed -e 's/\.//'`
GLOCATION=`echo "${LOCATION_NAME}"`
GMAPSET=`echo "${MAPSET}"`
export PS1='G$SHORT_VER ${GLOCATION}/${GMAPSET}:\w > '
export PROMPT_DIRTRIM=2

which doesn't work! :-/

Where should $LOCATION_NAME, $MAPSET be fed from?

Thanks, N
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Custom GRASS command line prompt

[Nikos Alexandris]

Nikos:

> > I want to alter the default GRASS command line prompt.
..
> > As a first experiment, I edited the corresponding file in place:
> > grass7_trunk/dist.x86_64-unknown-linux-gnu/grass70.tmp, line 1039:
..
> > f.write("PS1='G %s (%s/%s):\w > '\n" % (grass_version, location_name,
> > mapset))

> > Now it appears like:  "G 7.0.svn (utm_37s/post):~ >".  My understanding is
> > that I probably need to edit the file:
> > grass7_trunk/dist.x86_64-unknown-linux-gnu/grass70.tmp

> > Do you have customised prompts?  Any ideas for a more productive
> > command line?

Hamish wrote:
 
> I'd suggest to put the change in ~/.grass.bashrc instead.

Somehow it got stuck in my mind that I need to do it in the source...

 
> fwiw here's what I have there wrt the prompt:
 
> SHORT_VER=`echo "$GRASS_VERSION" | cut -f1,2 -d. | sed -e 's/\.//'`
> export PS1='G$SHORT_VER:\W > '

Yes! Was thinking exactly about Gxx :-)


> export HISTSIZE=3000

here: export HISTSIZE=15000 :D


> .or.
 
> export PS1='G$SHORT_VER:\w > '
> export PROMPT_DIRTRIM=2
> 
> as full dir path gets much too long, especially on WinGrass where the
> terminal width is a pain to resize.

Just a thought: would be nice to customise as to have a top or a bottom 
"info-line", or two 
"info-lines" below 80 chars (what's the max that should be respected?), like


show a "+" for many Mapsets--- vvv
v
,--%<---
|Gxx | Location/Mapset [Mapset2 Mapset3 Mapset4 +] Datum Units
| n=111 s= w=33 e=44 ns=4 ew=4 cells=4664r x 4446c
`--->%--

or stuff can go in the terminals title-bar -- this, I guess, works easily with 
a few terminals 
like xterm.


> For simplicity one of my favourites is still just:
 
> export PS1='GRASS$SHORT_VER> '
  
> If you do most of your work with a small set of locations, it might
> also be an idea to figure something out with Xresources to color the
> terminal background based on which one you're running in.

Nice!! I was looking the past week at .

Thanks a lot!

Nikos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r57291: configure.in: disable pwd -W (WinGRASS)

[Martin Landa]

2013/7/28 Hamish :
> re r57291, it's not safe to modify core files after the last RC :-(

but sure, you are right. It was not a good idea. Martin

-- 
Martin Landa  * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2039: Startup Error

[GRASS GIS]

#2039: Startup Error
--+-
 Reporter:  akdeakin  |   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  6.4.4
Component:  Startup   | Version:  6.4.3 RCs
 Keywords:  wingrass  |Platform:  MSWindows 7  
  Cpu:  x86-64|  
--+-
Changes (by akdeakin):

  * cpu:  x86-32 => x86-64
  * milestone:  6.4.3 => 6.4.4


Comment:

 I have upgraded to GRASS GIS 6.4.3RC4:
 WinGRASS-6.4.4svn-r57305-650-Setup.exe

 This time, I am trying to launch GRASS on my home computer with full
 administrative privileges.

 I have also installed to the following directory:  C:\grass64 and
 installed the latest Microsoft .NET framework. I also disabled my avast
 antivirus software. I have reinstalled the MSVCR71.dll to both the
 System32 and SysWOW64 folders

 When I try to launch GRASS GIS 6.4.4svn, a command line window flashes
 very quickly and then nothing.

 Do you have any further things I might try? Thanks for your patience and
 help.

 AKD

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r57291: configure.in: disable pwd -W (WinGRASS)

[Martin Landa]

Hi,

2013/7/28 Hamish :
> re r57291, it's not safe to modify core files after the last RC :-(
>
> http://trac.osgeo.org/grass/changeset/57291/grass/branches/releasebranch_6_4/configure.in

it has some background, I spent some days with creating a new
up-to-date OSGEO4W packages for produce environment (`msys`) and
building environment (`mingw`). Disabling `pwd -W` turned to
reasonable even before releasing. When spending time on that and other
fucking Windows issues I took liberty to comment it at least.

> There's a missing " quote at the end of line 110. One thousand times lucky 
> this was in a commented out part!!

OK, Markus already fixed it. Anyway harmless(!!!)

Martin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1275: zipped HGT Import fails on wingrass as "unzip" isn't in the package

[GRASS GIS]

#1275: zipped HGT Import fails on wingrass as "unzip" isn't in the package
+---
 Reporter:  MartinOver  |   Owner:  grass-dev@… 
 
 Type:  defect  |  Status:  new 
 
 Priority:  normal  |   Milestone:  6.4.3   
 
Component:  Packaging   | Version:  svn-releasebranch64 
 
 Keywords:  r.in.srtm, wingrass, unzip  |Platform:  MSWindows XP
 
  Cpu:  All |  
+---

Comment(by martinl):

 Replying to [comment:15 hellik]:
 > unzip [1] seems to be needed to close this ticket.
 >
 > [1] http://gnuwin32.sourceforge.net/packages/unzip.htm

 I have added `unzip` into `msys` package in `1.0.18-4` (1)

 (1)  http://trac.osgeo.org/osgeo4w/wiki/pkg-msys#Majorchanges

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev