[GRASS-dev] nasty gotcha in alternate ogr2ogr solution comment

Markus Neteler neteler at osgeo.org
Wed Nov 5 14:15:44 EST 2008


On Wed, Nov 5, 2008 at 3:39 PM, Patton, Eric <epatton at nrcan.gc.ca> wrote:
>>> AFAICT `g.proj -wf` doesn't include grid file, while `g.proj -jf` does.
>>> So I think my "best use `g.proj -wf` in that case" might be wrong as it
>>> drops the grid file, so really best to use:
>>>
>>> IN_PROJ="`g.proj -jf` +wktext"
>>>
>>> http://trac.osgeo.org/gdal/ticket/2638#comment:6
>>> http://trac.osgeo.org/gdal/changeset/15681
>
>>Mhh, that's fairly bad. Perhaps we need a note on
>>the g.proj and g.region manual pages?
>>
>>However. I feel that 'g.proj -jf' is a poor representation
>>compared to 'g.proj -wf', at least it doesn't help to
>>maintain metadata in a reasonable way.
>>
>>Markus
>
> Just so I understand the problem: g.proj fails to report nadgrids information
> with the -wf whereas -jf does? Should I go ahead and update the page, or is this
> a relatively simple fix in the code?

I feel that using -wf will severly damage the metadata (but apparently
ignores nadgrids information which is bad, too - if present).

I didn't go through the entire story, so no suggestion from me.

Markus


More information about the grass-dev mailing list