> Giovanni, > > I'm afraid I don't really follow your point. Are you wanting to > be able to do something like -t_srs GFOSSIT:3033 ?
No Frank, that would be a hell! :) I was just thinking about the relation that can be assumed between the epsg strings produced by gdal and the epsg codes from the EPSG registry. I mean, if I say that I'm using an EPSG:3003, it's different if I assume it in its original definition (without transformation parameters) and the one produced by gdal (with a best available transformation). For anything custom I would strictly use the rule of using code ranges beyon 32767, and to avoid clashes an authority field would help. >> The idea of a DATUMSHIT selector would be nice ;) > I'm not too sure if your misspelling is intentional or not, > though it captures how I often feel about datums. I was referring to the extended -t_srs option you were suggesting... giovanni > > Best regards, > -- > ---------------------------------------+-------------------------------------- > I set the clouds in motion - turn up | Frank Warmerdam, [email protected] > light and sound - activate the windows | http://pobox.com/~warmerdam > and watch the world go round - Rush | Geospatial Software Developer _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
