[GRASS5] [bug #4123] (grass) v.in.ogr PROJ recognition bug

Request Tracker grass-bugs at intevation.de
Tue Feb 28 17:51:19 EST 2006


this bug's URL: http://intevation.de/rt/webrt?serial_num=4123
-------------------------------------------------------------------------

Subject: v.in.ogr PROJ recognition bug

> Hi,
> 
> I tried to import the sample soils map from
> PostGIS (1.1.x, on PG 8.0.x):
> 
> ogrinfo "PG:host=localhost dbname=postgis" soils | head -25
> INFO: Open of `PG:host=localhost dbname=postgis'
> using driver `PostgreSQL' successful.
> 
> Layer name: soils
> Geometry: Polygon
> Feature Count: 737
> Extent: (589443.750000, 4913923.000000) - (609546.187500,
> 4928106.000000) Layer SRS WKT:
> PROJCS["UTM Zone 13, Northern Hemisphere",
>     GEOGCS["clark66",
>         DATUM["North_American_Datum_1927",
>             SPHEROID["clark66",6378206.4,294.9786982]],
>         PRIMEM["Greenwich",0],
>         UNIT["degree",0.0174532925199433]],
>     PROJECTION["Transverse_Mercator"],
>     PARAMETER["latitude_of_origin",0],
>     PARAMETER["central_meridian",-105],
>     PARAMETER["scale_factor",0.9996],
>     PARAMETER["false_easting",500000],
>     PARAMETER["false_northing",0],
>     UNIT["meter",1]]
> FID Column = ogc_fid
> Geometry Column = wkb_geometry
> cat: Integer (0.0)
> label: String (0.0)
> 
> 
> But GRASS tells me:
> v.in.ogr dsn="PG:host=localhost dbname=postgis" layer=soils
> output=soils_pg type=boundary,centroid ERROR: Projection of dataset
> does not appear to match current location.
> 
>        LOCATION PROJ_INFO is:
>        name: UTM
>        datum: nad27
>        nadgrids: conus
>        proj: utm
>        ellps: clark66
>        a: 6378206.4000000004
>        es: 0.0067686580
>        f: 294.9786982000
>        zone: 13
> 
>        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.
> 
> 
> It seems that there are still definition issues with PROJ.
> 
> any ideas?

I have found the opposite behaviour. I can import any dataset with
different proj-information inside the spearfish60-location...

Something is messed up there.

Could anybody have a look into this?

Best
	Stephan

-------------------------------------------- Managed by Request Tracker




More information about the grass-dev mailing list