[GRASS-user] Re: Can't create location from file

[Gerald Nelson]

I took a quick look at the 6.3 error message. Can I make a couple of suggestions?

1. Instead of "Error creating new location from EPSG code. g.proj returned following message:" replace with 
"Unable to create new location from the EPSG code xxxx provided in the input box [or whereever it came from]. The module that creates new locations, g.proj, returned the following message;"

2. Put the message from g.proj into double or single quotes and have it not break at strange places.

3. Add a list of possible sources of the problem. I guess these might be an invalid path or a typo in the EPSG number.

There's probably better ways to do this than my suggestions. 

Thanks, Jerry



---- Original message ----
>Date: Sat, 16 Jun 2007 22:44:53 +0200
>From: Maciej Sieczka <tutey at o2.pl>  
>Subject: Re: [GRASS-user] Re: Can't create location from file  
>To: Daniel Victoria <daniel.victoria at gmail.com>
>Cc: grass <grassuser at grass.itc.it>
>
>Daniel Victoria wrote:
>> Just an update.
>> 
>> I just noticed that grass is looking for the epsg file in
>> /usr/local/share/proj and it's installed in /usr/share/proj. Could
>> that be related?
>
>You should put the path to where your "epsg" file resides into the
>"Path to the EPSG codes file" dialog. The file comes with PROJ.4.
>
>> Also, the geotiff has several epsg codes in it and
>> the only one valid is 4326.
>
>Your gdalinfo output seems corrupted. Compare with the output of
>"epsg_tr.py 4326" to see the difference. It is missing EPSG codes for
>prime meridian and unit. That's propably why GRASS fails to creata a
>location using it.
>
>Also please note that only the last EPSG code designates the coordinate
>system. Those coming before it are for the CS components, like
>spheroid, datum etc.
>
>> If I create a location with this EPSG code
>> all goes fine. If I use the others, a tmp.<somenumber> directory is
>> created.
>
>That's because you are passing wrong EPSG coordinate system code, which
>GRASS 6.2 can't handle and creates a corrupted location. As expected,
>only "4326" works OK. In GRASS 6.3, using an invalid coordinate system
>EPSG code yields an error message like on the attached screendump.
>Please fill in a wish in the tracker for backporting this usefull
>feature to GRASS 6.2. Maybe it will get included in 6.2.2 release.
>
>Maciek
>________________
>wrong_epsg_grass63.png (6k bytes)
>________________
>_______________________________________________
>grassuser mailing list
>grassuser at grass.itc.it
>http://grass.itc.it/mailman/listinfo/grassuser
Gerald Nelson
Professor, Dept. of Agricultural and Consumer Economics
University of Illinois, Urbana-Champaign
office: 217-333-6465 
cell: 217-390-7888
315 Mumford Hall
1301 W. Gregory
Urbana, IL 61801