[GRASS-dev] g.setproj from XY locn?
hamish_b at yahoo.com
Mon May 25 18:36:04 EDT 2009
> > g.setproj doesn't let you run it from a XY location.
> > is that really necessary?
> > it makes it hard to import unprojected imagery, reset to
> > known bounds with r.region, and then change into a lat/lon
> > location. note in that workflow the raster's cellhd/
> > file must be hacked to be proj: 3.
> You could probably merge the "case 0" with
> PROJECTION_OTHER, so it prompts for the projection.
I don't think it's a problem to technically do it, I'm just
trying to figure out if there's any good reason for it being
the way it is.
I have worked around the long-standing problem of "illegal
latitude for north" by adding a new -l flag to r.in.gdal which
will reset the image bounds to within 90N,S. With lots of
warnings to run r.region of course. I figure coords based on
pixels are arbitrary as well, so it is not any more wrong to do
that, and much better than removing the libgis restriction.
More information about the grass-dev