#2456: read CSV from GDAL data directory
---------------------------------+---------------------------------
  Reporter:  martinl             |      Owner:  grass-dev@…
      Type:  task                |     Status:  new
  Priority:  blocker             |  Milestone:  7.4.0
 Component:  Projections/Datums  |    Version:  svn-releasebranch70
Resolution:                      |   Keywords:  gdal, g.proj
       CPU:  Unspecified         |   Platform:  Unspecified
---------------------------------+---------------------------------

Comment (by martinl):

 Replying to [comment:37 neteler]:
 > Furthermore the g.proj code needs updates. Or in lib/proj/?
 >
 > For some tests, see
 > https://lists.osgeo.org/pipermail/grass-user/2016-September/075035.html

 what is exact problem? I tried in G72 and G73

 {{{
 g.proj -t epsg=2992 datumtrans=-1
 }}}

 Both version gives me the same output:

 {{{
 ---
 1
 Used in whole nad83 region
 towgs84=0.000,0.000,0.000
 Default 3-Parameter Transformation (May not be optimum for older datums;
 use this only if no more appropriate options are available.)
 ---
 2
 Used in Florida
 nadgrids=FL
 Transforms 'Old NAD83' to 'HPGN NAD83'
 ---
 3
 Used in Maryland
 nadgrids=MD
 Transforms 'Old NAD83' to 'HPGN NAD83'
 ---
 4
 Used in Tennessee
 nadgrids=TN
 Transforms 'Old NAD83' to 'HPGN NAD83'
 ---
 5
 Used in Wisconsin
 nadgrids=WI
 Transforms 'Old NAD83' to 'HPGN NAD83'
 ---
 6
 Used in Washington - Oregon
 nadgrids=WO
 Transforms 'Old NAD83' to 'HPGN NAD83'
 }}}

 BTW, instead of

 {{{
 grass72 -c epsg:2992 ~/grassdata/oregon2992_nad83_WO --exec g.proj -t
 epsg=2992 datumtrans=6 -p
 }}}

 you can do

 {{{
 grass72 -c epsg:2992:6 ~/grassdata/oregon2992_nad83_WO --exec g.proj -p
 }}}

 The same approach works also in G73.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2456#comment:38>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to