[GRASS-dev] Re: g.proj won't parse PROJ.4 string

[Michael Barton]

On 7/4/07 3:26 PM, "Paul Kelly" <paul-grass at stjohnspoint.co.uk> wrote:

> In fact yes I've been thinking about this the last few days and realised
> it would be a problem. Using g.proj in this way is more complicated than
> it first appeared. It may be simpler to manually create the directories
> (in Python) and write out the PROJ_INFO and PROJ_UNITS files directly.
> Skeleton DEFAULT_WIND and WIND files would also have to put in too.

This also not as easy as it sounds.

> 
> As I said I don't have a lot of time to devote to this but I'm working on
> a proposal for how I think a location creation wizard should work (what is
> included on each screen etc.) and when finished I will post it to the
> list, in the hope that the thinking behind it will prove to be some help.
> I'm doing it blind, i.e. without looking at what's there already in the
> new GUI - hopefully we can then share the best ideas from both approaches.
> 

Before doing this, can you take a look at the existing location wizard,
since it is about 90+% done and represents a big investment. Suggestions for
improvements are very welcome, but I'd be loathe to scrap the whole thing
unless there is very good reason to do so. I'm currently debugging it since
g.proj is not accepting the PROJ.4 strings it is creating, but they've got
to be close. All is otherwise working except extents.

Michael

__________________________________________
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-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton