[GRASS-dev] Re: [GRASS-user] Unable to create new project with Grass

[Michael Barton]

This suggests a problem with g.proj, since both EPSG and georeferenced  
file methods use it for creating a location, but specifying parameters  
does not. This is beyond my area of expertise, but maybe someone else  
on the dev list can troubleshoot now.

Michael
______________________________
Michael Barton, Professor
Professor of Anthropology
Director of Graduate Studies
School of Human Diversity & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

On Jan 14, 2008, at 9:20 AM, Jan Schorn wrote:

> Hi Michael,
> creating Locations specifying projection parameters works fine.
>
> Creating Locations from georeferenced file ( http://atlastenerife.es/TeIDE2/Descarga_Publica.do?fichero=830 
>  ) causes an 'Error de la aplicación' ;-). Both versions, the 6.2.2  
> (64 bit) and 6.2.3 (32 bit) one, are displaying the same error log  
> (see below).
> The file used doesn't make problems importing it into a location.
>
> Good luck :-)
> Jan
>
>
> Error: /usr/bin/x-terminal-emulator: ...
>
> *Details:*
>
> /usr/bin/x-terminal-emulator: to set an icon, please use -name  
> <profile> and set a profile icon
> /usr/bin/x-terminal-emulator: to set an icon, please use -name  
> <profile> and set a profile icon
>   while executing
> "exec -- $env(GISBASE)/etc/grass-xterm-wrapper -T g.proj -n g.proj - 
> e $env(GISBASE)/etc/grass-run.sh g.proj -c georef=$filepath location= 
> $fileLocation"
>   invoked from within
> ".fileloc.def invoke"
>   ("uplevel" body line 1)
>   invoked from within
> "uplevel #0 [list $w invoke]"
>   (procedure "tk::ButtonUp" line 22)
>   invoked from within
> "tk::ButtonUp .fileloc.def"
>   (command bound to event)
>
>
>
>
> Michael Barton escribió:
>> Jan,
>>
>> Is EPSG location creation the only thing that fails? Can you create  
>> locations from georeferenced files and by specifying projection  
>> parameters?
>>
>> I just tried creating a location from EPSG code 4326 and it worked  
>> fine in GRASS 6.3 compiled a few days ago. I don't know if this is  
>> a problem related to 6.2 or not
>>
>> Glynn Clements discussed a problem with shared libraries in Linux  
>> that might or might not be a help. I am copying it below.
>>
>> Michael
>> ____________________
>> C. Michael Barton, Professor of Anthropology
>> Director of Graduate Studies
>> School of Human Evolution & Social Change
>> Center for Social Dynamics & Complexity
>> Arizona State University
>>
>> Phone: 480-965-6262
>> Fax: 480-965-7671
>> www: <www.public.asu.edu/~cmbarton>
>>
>> ======== shared library post ==============
>> Date: Sun, 13 Jan 2008 23:34:52 +0000
>> From: Glynn Clements <glynn at gclements.plus.com>
>> Subject: Re: [GRASS-user] Error creating new mapset
>> To: "Jose A. Ruiz-Arias" <jararias at ujaen.es>
>> Cc: grass-user at lists.osgeo.org
>> Message-ID: <18314.40988.419833.583423 at cerise.gclements.plus.com>
>> Content-Type: text/plain; charset=us-ascii
>>
>>
>> Jose A. Ruiz-Arias wrote:
>>
>>
>>> i have installed GRASS-6.2.3 from source code with no apparent  
>>> errors during
>>> configuration, compilation and installation. However, when i run  
>>> grass and
>>> try to create a new mapset i get next error:
>>>
>>> g.region: error while loading shared libraries: libgdal.so.1:  
>>> cannot open
>>> shared object file: Error 40
>>>
>>> In fact, when i was setting the projection parameters and chose a  
>>> UTM
>>> projection, the program did not ask me for the UTM zone, the  
>>> ellipsoid and
>>> the datum.
>>>
>>> In the GRASS configure process I explicitely used the
>>> flag --with-gdal=/usr/local/bin/gdal-config and there were no  
>>> errors. I
>>> checked for the shared library and it is placed in /usr/local/lib  
>>> directory.
>>>
>>> Before the GRASS installation, I installed the GDAL/OGR bundle  
>>> from the source
>>> code, with netcdf support, and the GRASS support disabled. Again,  
>>> there were
>>> no apparent errors. Next I installed the gdal-grass plugin (gdal- 
>>> grass-1.4.3
>>> with the following options:
>>> configure --with-gdal=/usr/local/bin/gdal-config --with-grass=/usr/ 
>>> local/grass-6.2.3)
>>>
>>> I did not detect any problem during the installation of these  
>>> bundles. Anyone
>>> knows about the problem??
>>>
>>
>> Most systems won't load shared libraries from /usr/local/lib without
>> some additional configuration.
>>
>> For Linux, you need to either set the LD_LIBRARY_PATH environment
>> variable to a path which includes /usr/local/lib, or add
>> /usr/local/lib to /etc/ld.so.conf then run ldconfig (as root).
>>
>