AFAICT, there is no way for the GUI to know if an EPSG code is bad. Perhaps g.proj can test for this, but I wouldn't count on it.
The procedure to create a location from a georeferenced file is different from the procedure to create it from an EPSG code, so I'm not sure what you are referring to below. Michael On 6/16/07 2:39 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > code R item #428, was opened at 2007-06-16 18:39 > Status: Open > Priority: 3 > Submitted By: Daniel Victoria (dvictori) > Assigned to: Nobody (None) > Summary: Warn about wrong epsg code when creating a location in grass 6.2 > Issue status: None > GRASS component: startup > Operating system: None > Operating system version: Linux > > > Initial Comment: > When creating a location based on a georeferenced files, if the EPSG code is > wrong there is no clear warning and no location gets created. This feature is > already present in 6.3. Could it be backported? > > Also, if a wrong EPSG code is input a tmp directory sometimes is created > thanks > Daniel > > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://wald.intevation.org/tracker/?func=detail&atid=188&aid=428&group_id=21 > > __________________________________________ Michael Barton, Professor of Anthropology 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 _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
