[GRASS-dev] Re: [GRASS GIS] #94: PROJ file sometimes not created with location

[Michael Barton]

Thanks Paul,

I'll see if I can track down a file that caused this kind of error.

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 Mar 13, 2008, at 11:28 AM, GRASS GIS wrote:

> #94: PROJ file sometimes not created with location
> ----------------------- 
> +----------------------------------------------------
>  Reporter:  cmbarton  |       Owner:  grass-dev at lists.osgeo.org
>      Type:  defect    |      Status:  new
>  Priority:  major     |   Milestone:  6.4.0
> Component:  default   |     Version:  svn-trunk
> Resolution:            |    Keywords:  location PROJ projection g.proj
> ----------------------- 
> +----------------------------------------------------
> Comment (by pkelly):
>
> Hello Michael,
> Please can you give an example of a file that causes this problem  
> (put it
> online somewhere and post a link?) and I will investigate it. As far  
> as I
> know any errors in parsing the projection information are reported.  
> The
> only thing I can think of is that the file doesn't actually contain
> projection information - it's not an error to carry on creating a  
> location
> from this though, as some information from the file (i.e. the  
> extents and
> resolution) can still be used in creating the location.
>
> AND... as far as I can see g.proj already outputs a warning when an
> unprojected file is being used. Something like:
> Read of file ./roads.shp was successful, but it did not contain
> projection information. 'XY (unprojected)' will be used
>
> An additional warning could I suppose be added if a location is being
> created, specifically reminding the user of the need to run  
> g.setproj or
> g.proj at a later date, if we think that's necessary. But I really  
> need to
> see an example of the file that causes this problem as I can't see  
> where
> it would be happening.
>
> Paul
>
> -- 
> Ticket URL: <http://trac.osgeo.org/grass/ticket/94#comment:1>
> GRASS GIS <http://grass.osgeo.org>
> GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/