[GRASS-dev] [GRASS GIS] #2456: read CSV from GDAL data directory

GRASS GIS trac at osgeo.org
Thu Sep 15 00:44:53 PDT 2016


#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 neteler):

 Replying to [comment:33 neteler]:
 > After discussion with Even Rouault at the FOSS4G 2016 code sprint and
 some testing with m.proj
 >  * removal of local copies of NAD and datum shift files which are indeed
 used from GDAL
 >  * extended documentation in lib/proj/README.txt
 >
 > Done in r69211.
 >
 > After extensive testing backport candidate. Test values available in
 https://github.com/OSGeo/proj.4/tree/master/nad . Test cases should be
 implemented with m.proj.

 Issues: the location manager needs to be updated accordingly (at time it
 still seeks for NAD files in the removed etc/proj/nad/ directory):

 {{{
 cd gui/wxpython/location_wizard/
 wizard.py:                # prepare +nadgrids or +towgs84 terms for
 Summary page. first
 wizard.py:                            "towgs84=") != -1 or
 projterm.find("nadgrids=") != -1:
 wizard.py:                # prepare +nadgrids or +towgs84 terms for
 Summary page. first
 wizard.py:                            "towgs84=") != -1 or
 projterm.find("nadgrids=") != -1:
 }}}

 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

 I wonder if we should revert r69211 for now (except for the README
 update).

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



More information about the grass-dev mailing list