On 16 June 2017 at 06:36, C Hamilton wrote:
> There are several missing methods to QgsDistanceArea
>
> 1. Return the shortest path line between two points. The input would be the
> two points and the maximum distance of travel before a new line segment is
> added to the
That's nice to see someone else with the same ideas and needs. Ultimately
what I would like to see happen is for QgsDistanceArea class to be expanded
to support these better geodesic algorithms, but also support great circle
transforms as well. The advantage of simpler algorithms is their speed
Am Mi, 14.06.2017, 23:41 schrieb Nyall Dawson:
>
> This looks relevant:
>
> https://github.com/sourcepole/kadas-albireo/commit/df64318e5198f40f0e96d27fcf9e179fbbf682fd
Thanks, nice find. After googling a bit: that seems to be the GIS
of the Swiss army :)
On 13 June 2017 at 00:20, C Hamilton wrote:
>>
>> > Right now it could use the Vincinty algorithms in QGIS to calculate the
>> > distances, but eventually I would like to see the geographiclib
>> > algorithms
>> > used.
>>
>> I'd start with the bearing changes (since they
> >
> > 2. I would like to see a check box or selection widget of some sort that
> > chooses between using Geodesic math or the current method of calculating
> the
> > distances which I am still unsure on how it is doing its calculations.
>
> If you expand down the info box you'll get a detailed
On 10 June 2017 at 02:30, C Hamilton wrote:
> Several weeks ago I had proposed a geodesic measure tool that also includes
> the bearing from point A to B and bearing from B to A. Nyall suggested that
> this capability be added to the QGIS measure tool. The question is
Several weeks ago I had proposed a geodesic measure tool that also includes
the bearing from point A to B and bearing from B to A. Nyall suggested that
this capability be added to the QGIS measure tool. The question is would
you want this with the QGIS measure tool or should it be a separate