[GRASS5] [bug #3876] (grass) g.proj: proj4= fails, wkt= works partialy
neteler at itc.it
Thu Feb 9 08:51:30 EST 2006
On Thu, Feb 09, 2006 at 11:30:42AM +0000, Paul Kelly wrote:
> On Mon, 6 Feb 2006, Maciek Sieczka via RT wrote:
> >Creating new location from an EPSG code fails. Maybe due to Paul's recent
> >changes? This problem could be populate to 6.02 candidate as well then.
> >I tried to create a location from EPSG code 2180. There was no error,
> >was created. My path to /usr/local/share/proj/epsg is ok. However the
> >is not projected:
> The EPSG codes are read from $(GISBASE)/etc/ogr_csv/pcs.csv and not
> /usr/local/share/proj/epsg, if that makes any difference.
> Something to try to be sure is g.proj -p proj4=+init=epsg:2180 and it
> should print the correct co-ordinate system in GRASS format.
> The conversion logic is mostly in OGR. The PROJ.4 string is never
> interpreted by PROJ in this case but by OGR.
g.proj -p proj4=+init=epsg:2180
works again (tested in Spearfish).
v.in.ogr still fails (here it should display the contents of the .prj
file, not 0):
GRASS 6.1.cvs (spearfish60):~/data/vmap0 > v.in.ogr polbnda_italy_GB_ovest.shp out=test
ERROR: Projection of dataset does not appear to match current location.
LOCATION PROJ_INFO is:
cellhd.proj = 0 (unreferenced/unknown)
You can use the -o flag to v.in.ogr to override this check.
Consider to generate a new location with 'location' parameter from
input data set.
GRASS 6.1.cvs (spearfish60):~/data/vmap0 > cat polbnda_italy_GB_ovest.prj
Maybe it has to do with the definition of
More information about the grass-dev