[GRASS-dev] [GRASS GIS] #2402: v.distance in Long/Lat Locations on GRASS 7.0

[GRASS GIS]

#2402: v.distance in Long/Lat Locations on GRASS 7.0
-------------------------+--------------------------------------------------
 Reporter:  micha        |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  7.0.0                    
Component:  Default      |     Version:  unspecified              
 Keywords:               |    Platform:  All                      
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by mlennert):

 Replying to [comment:6 mmetz]:
 > Replying to [comment:5 mlennert]:
 > > Replying to [comment:4 mmetz]:
 > > > Replying to [ticket:2402 micha]:
 > > > > In stable version 6.4, when working in a Long-Lat LOCATION,
 v.distance returns geodesic distance on a sphere in meters (in the cases
 of point to point, and point to line).
 > > >
 > > > > In GRASS 7.0 this feature is lost, and distances are always
 returned in the LOCATION units (i.e. degrees in a Long-Lat LOCATION).
 Geodesic distance should be the preferred behavior.
 > > >
 > > > Fixed for trunk in r61850.
 > >
 > > With the NC-data reprojected to EPSG 4326, I get the following now:
 > >
 > >
 > {{{
 > v.distance -p from=comm_colleges to=comm_colleges upload=dist col=dist
 dmin=0.0001
 >
 > Finding nearest features...
 >  100%
 >  100%
 > from_cat|dist
 > 1|null
 > 2|null
 > 3|null
 > [...]
 > 55|null
 > 56|null
 > 57|null
 > 58|null
 >  100%
 > 58 categories - no nearest feature found
 > }}}
 > >
 >
 > Oops. Fixed in r61861.

 I just found a difference in distances calculated with grass6 and grass7
 for points to areas (see explanation in #2401). Needs checking.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2402#comment:7>
GRASS GIS <http://grass.osgeo.org>