Re: [Qgis-user] unexpected CRS behavior (GRASS)

[Stefan Blumentrath]

See also:
https://issues.qgis.org/issues/10137 and
https://issues.qgis.org/issues/14499 for the QGIS side of it.

And
https://trac.osgeo.org/grass/ticket/3262
https://trac.osgeo.org/grass/ticket/3193
on the GRASS side, maybe also related:
https://trac.osgeo.org/grass/ticket/2229

I did not check CRS handling in v.out.ogr though (which I guess Processing is 
using for vector data).
It could also be an issue in the way processing generates the location (e.g. 
without explicitly defining EPSG code, (but I did not look at the source 
code)... 

If QGIS would use v.external.out SRID of the output could be handled 
explicitly. But that approach might have drawbacks if tools can be chained in 
processing...

Cheers
Stefan


Von: Qgis-user  im Auftrag von Tobias 
Wendorff 
Gesendet: Sonntag, 11. Juni 2017 09:02
An: Andre Joost
Cc: qgis-user@lists.osgeo.org
Betreff: Re: [Qgis-user] unexpected CRS behavior (GRASS)

Hi Andre,

nice to read from you here.

Am So, 11.06.2017, 07:56 schrieb Andre Joost:
> If you save the Linestring to a shapefile with EPSG:32632, it runs
> correctly.

Interesting :) Thanks for pointing this out.

> It seems that GRASS gets confused over the similar WKT definitions .

GRASS or QGIS? I didn't check the temporary shapefile, which gets
written. I'll do that soon.

Best regards,
Tobias

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Problems to do viewshed (SAGA, GRASS and...)

[Carlos López PSIG]

Hi,
I'm trying to do a visibility layer.
First, I'm try to use "Viewshed analytics" but don't work for me (2.18.9 on
Linux).
But, this closes QGIS every time that I execute the tool.

I think that my layers are OK, the same SRC, the model elevation is the
original from Cartographic Institute "official".

Then I try to use SAGA, but I don't have the tool terrain analysis >
Lighting > visibility (single point) interactive

And finally I try to use grass, r.viewshed, but neither:
Error in `r.viewshed': free(): invalid pointer: 0x016bb218 ***

I need to do a visibility raster,
Do you have any suggestion?

Thanks in advance.

Best regards,


* *
*PSIG*
Implementació, gestió i formació SIG

*Carlos López Quintanilla*

www.psig.es
carlos.lo...@psig.es
+34 699.680.261

Nota legal: Este mensaje y cualquier archivo adjunto está destinado
únicamente a la
persona a quien se dirige y es confidencial. Si usted ha recibido este
mensaje por
error, por favor, comuníqueselo al remitente y bórrelo inmediatamente. La
utilización ,
revelación y/o reproducción del mensaje puede constituir un delito.

Protección de Datos: Le informamos que sus datos de contacto electrónico se
hallan
incorporados a un fichero titularidad de CARLOS LÓPEZ QUINTANILLA, al
objeto de
envío de información, respuesta a consultas y contactos genéricos.
Puede ejercer los derechos de acceso, rectificación, cancelación y
oposición que
establece la LOPD en cualquier momento, mediante escrito, acompañado de
copia de
documento oficial que le identifique, dirigido a CARLOS LÓPEZ QUINTANILLA
CL. P
arellada, 8 E2 de Corbera de Llobregat, 08757-Barcelona.

También podrá oponerse a nuestros envíos de comunicaciones comerciales
(Art.21.2
de la LSSI) a través de la siguiente dirección de correo electrónico:
ad...@psig.es
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] how set correctly atlas composer using pyqgis

[xristosss20]

 try to follow this code to create automate atlas print composer using pyqgis
: 

def quick_export(self, ref, stype, scale): 

# Add all layers in map canvas to render 
myMapRenderer = self.iface.mapCanvas().mapRenderer() 

# Load template from file 
myComposition = QgsComposition(myMapRenderer) 
myFile = os.path.join(os.path.dirname(__file__), 'MMR_Template.qpt') 
myTemplateFile = file(myFile, 'rt') 
myTemplateContent = myTemplateFile.read() 
myTemplateFile.close() 
myDocument = QDomDocument() 
myDocument.setContent(myTemplateContent) 
myComposition.loadFromTemplate(myDocument) 

# Get map composition and define scale 
myAtlasMap = myComposition.getComposerMapById(0) 
myAtlasMap.setNewScale(int(scale)) 

# Setup Atlas 
myAtlas = QgsAtlasComposition(myComposition) 
myAtlas.setCoverageLayer(atlas_desktop) # Atlas run from desktop_search 
myAtlas.setComposerMap(myAtlasMap) 
myAtlas.setFixedScale(True) 
myAtlas.fixedScale() 
myAtlas.setHideCoverage(False) 
myAtlas.setFilterFeatures(True) 
myAtlas.setFeatureFilter("reference = '%s'" % (str(ref))) 
myAtlas.setFilterFeatures(True) 

# Generate atlas 
myAtlas.beginRender() 
for i in range(0, myAtlas.numFeatures()): 
myAtlas.prepareForFeature( i ) 
jobs = r"\\MSUKSERVER\BusinessMan Docs\Jobs" 
job_fol = os.path.join(jobs, str(ref)) 
output_jpeg = os.path.join(job_fol, ref + "_BMS_plan.jpg") 
myImage = myComposition.printPageAsRaster(0) 
myImage.save(output_jpeg) 
myAtlas.endRender() 

specific in atlas with same changes code say : 

myAtlasMap = myComposition.getComposerMapById(0) 
myAtlas = QgsAtlasComposition(myComposition) 
myAtlas.setCoverageLayer(atlas_desktop) 
myAtlas.setComposerMap(myAtlasMap) 
myAtlas.setFixedScale(True) 
myAtlas.fixedScale() 
myAtlas.setHideCoverage(False) 
myAtlas.setFilterFeatures(True) 

this code work for my task and i take  export new 100 atlas feutures maps 

but in my template.qpt i have some labels with code like this : 

QGIS [%concat( "OBJECTID" )%] 

that OBJECTID is the same for all new 100 atlas feutures maps. Any idea why?
If I use manual atlas export, then for any map OBJECTID change. 

And the true is Does not work anything related to layer atlas in my
template.qpt i have some base styles rules or base labels rules like this : 

intersects($atlasgeometry, $geometry ) 

or 

$id = $atlasfeatureid 

but that styles not work with this code. 

i think so that code just export one by one my feutures from my atlas layer
and the atlas in me template stay False. 

any idea ?i want to lern this solution is interesting question



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/how-set-correctly-atlas-composer-using-pyqgis-tp5323903.html
Sent from the QGIS - User mailing list archive at Nabble.com.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] problems with 'geometry creator'

[DelazJ]

Btw, giving a deeper look to the help provided in the code, I wonder if
"geom_to_wkt(line_merge(geom_from_wkt('MULTILINESTRING((0 0, 1 1),(1 1, 2
2))')))"
and especially MULTILINESTRING((0 0, 1 1),(1 1, 2 2))') is a valid
multilinestring (a multipart feature whose parts already touch themselves).
Shouldn't it be two separate linestrings?
Also, in the application function help line_merge(geometry) should instead
be line_merge(geometry1, geometry2,.., geometry n), shouldn't it?
Let me know if I'm right, in which case I can provide a PR if needed.

Regards,
Harrissou

Le lundi 12 juin 2017, DelazJ  a écrit :
> Hi Tobias,
>
> I'm not sure what you did is the way to get what you expected (from what
I've understood); I'd not be that confident on your process (note that I
don't mean your result is false).
>
> Line_merge function like most of the expression functions in QGIS (except
aggregate ones) works feature by feature, meaning that it processes only
the geometry you provide in the bracket and, in your expression, afaict,
you simply provide the existing geometry (of each feature) --> this might
actually return the same geometry. So it won't merge your five features
into one, be it line or multi linestring.
>
> As mentioned by Matthias, virtual layer or collect option in aggregate
function (which I think is a 3.0 feature - didn't test it though) might be
the solution if you want a single feature.
>
> That said, doesn't the Symbol levels option (
http://docs.qgis.org/testing/en/docs/user_manual/working_with_vector/vector_properties.html#symbols-levels)
already solve your issue?
> Looks like your change is simply for a better rendering/join of lines and
it's what this option is designed for...
>
> HTH,
> Harrissou
>
> Envoyé depuis mon HTC
>
> - Reply message -
> De : "Tobias Wendorff" 
> Pour : "Matthias Kuhn" 
> Cc : 
> Objet : [Qgis-user] problems with 'geometry creator'
> Date : lun., juin 12, 2017 01:23
>
> Hi Matthias,
>
> Am So, 11.06.2017, 12:25 schrieb Matthias Kuhn:
>>
>> Sometimes - if you are lucky - they even produce better
>> results for you than trying random things.
>
> got it working - my MultiLinestring was buggy.
> So it wasn't "random trying", but an input error.
>
> Best regards,
> Tobias
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] problems with 'geometry creator'

[DelazJ]

Hi Tobias,

I'm not sure what you did is the way to get what you expected (from what
I've understood); I'd not be that confident on your process (note that I
don't mean your result is false).

Line_merge function like most of the expression functions in QGIS (except
aggregate ones) works feature by feature, meaning that it processes only
the geometry you provide in the bracket and, in your expression, afaict,
you simply provide the existing geometry (of each feature) --> this might
actually return the same geometry. So it won't merge your five features
into one, be it line or multi linestring.

As mentioned by Matthias, virtual layer or collect option in aggregate
function (which I think is a 3.0 feature - didn't test it though) might be
the solution if you want a single feature.

That said, doesn't the Symbol levels option (
http://docs.qgis.org/testing/en/docs/user_manual/working_with_vector/vector_properties.html#symbols-levels)
already solve your issue?
Looks like your change is simply for a better rendering/join of lines and
it's what this option is designed for...

HTH,
Harrissou

Envoyé depuis mon HTC

- Reply message -
De : "Tobias Wendorff" 
Pour : "Matthias Kuhn" 
Cc : 
Objet : [Qgis-user] problems with 'geometry creator'
Date : lun., juin 12, 2017 01:23

Hi Matthias,

Am So, 11.06.2017, 12:25 schrieb Matthias Kuhn:
>
> Sometimes - if you are lucky - they even produce better
> results for you than trying random things.

got it working - my MultiLinestring was buggy.
So it wasn't "random trying", but an input error.

Best regards,
Tobias

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Geodesic Measure Tool With Bearing Information

[C Hamilton]

> >
> > 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 description of
> exactly how QGIS is calculating the distances. Is there something
> missing there?
>

In some sense the measure tool is rather confusing. You can't just use it
without really reading up on how to use it and even then I am not 100% sure
I am getting the results I want, but as I look more into it I also realize
I have had a narrow view on how users might use it.

When you click the configuration button it takes you to the Map Tools
Options. What I didn't initially realize is that there are also project
properties that you also need to set as well. There is not a button on the
measure tool dialog that takes you to that dialog to change those settings.
Can this be simplified some how?

By default it appears that "None / Planimetric" is selected as the
ellipsoid. I think that for many people trying to use QGIS they are not
going to know how to get the settings set correctly to get accurate
measurements. I personally prefer to have the defaults set so that all
measurements make use of the Vincinty algorithm - projecting the
coordinates to latitude and longitudes and then doing that calculation.
This would give relative accurate measurements, but for the user that has a
local projection then they might want to select something else.

By the way there appears to be a problem with selecting Project
Properties->General Ellipsoid settings for QGIS 3. Every time I go into
these settings the Ellipsoid is set to "None / Plainimetric" and it is not
enabled. I have to click on the CRS tab and then go back for it to be
enabled.


>
> > 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 are self contained, and
> the methods for calculating bearing are already present in the QGIS
> api). Then using geographiclib could be discussed as a separate set of
> changes, to be decided on its own merit. If you mix these two changes
> it's likely to get bogged down as one or other part of the changes are
> debated.


Ok.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] QAD Dimension plugin in Qgis 2.10.1 Pisa

[Franco Cazzola]

Hi

I am using QAD plugin  with QGIS Pisa release.

When I use QAD plugin with sample data and  dimension.qgs  it works well.



If I import the three layer: point, symbol, line from QAD sample data into my 
qgis project, I have some malfunction (i.e. rotation text)

May I import part/all   dimension.qgs   setting into my .qgs file   or may I 
import/use   standard.dim   setting   into my qgs project  ?

Can anyone give me any help ?

Tks

Cheers



Franco Cazzola





-Messaggio originale-

Da: ga...@riseup.net [mailto:ga...@riseup.net]

Inviato: giovedì 2 giugno 2016 11:38

A: Franco Cazzola

Oggetto: Re: QAD Dimension plugin in Qgis 2.14.3 Essen (Franco Cazzola)



Have you read the QAD help ? (You can open the help running "help"

command or from QAD menu)



Looking at the italian version, you can focus on "layer" and "quotatura"

chapters.



From the "quotatura" QAD help chapter:

"

QAD memorizza gli elementi costituenti una quotatura in 3 layer

distinti:



· Layer testuale per memorizzare i testi delle quote



· Layer simbolo per memorizzare gli elementi puntuali delle

quote (punti di quotatura, simboli freccia…)



· Layer lineare per memorizzare gli elementi lineari delle

quote(linea di quota, linee di estensione…) "

All layer details are described in this section. Did you follow the 
instructions ?



Many people don't know what a text layer is. Infact it doesn't exist in qgis 
logic. It only exists in QAD world.

From the "layer" QAD help chapter:

"

QAD supporta tutti i tipi di layer vettoriali di QGIS con una distinzione per 
quanto riguarda i layer puntuali. Infatti QAD tratta i layer puntuali di QGIS 
distinguendoli tra layer simboli e layer testi. I primi hanno lo scopo di 
visualizzare dei simboli mentre i secondi hanno lo scopo di visualizzare dei 
testi.



Il layer testo è un layer che visualizza esclusivamente delle etichette.

Si tratta di un layer QGIS puntuale con le seguenti caratteristiche:



 il simbolo deve avere una trasparenza di almeno il 90%

 deve avere una etichetta



I layer puntuali che non sono testuali, verranno considerati dei layer simboli.

"



if you decide to use dimension please make the id field of the text layer a 
unique value column you can see the site:

https://anitagraser.com/2010/10/27/adding-a-unique-id-column-to-layers-in-qgis/

if you use postgis

you can create a field like the following example



CREATE TABLE land (

 -- make the "id" column a primary key; this also creates

 -- a UNIQUE constraint and a b+-tree index on the column

 gidSERIAL PRIMARY KEY,

 name  TEXT,

 the_geom geometry

);



hope it helps





> Hi

> As suggested, I tried QAD plugin and dimension features using the

> sample project provided with the plugin.

> The three dimension features work well.

>

> May I use these features inside other QGIS project ?

> I load a copy of the three layers shape files (dim_line, dim_text,

> dim_symbol) inside a current project.

> I tried to  create a new dimension style:

> in the mask, I can choose and set:   Line.layer, Symbol.layer  but

> Text.layer and all others field are disable

>

> Thanks for your contribution

> Franco Cazzola

>

>

> -Messaggio originale-

> Da: ga...@riseup.net [mailto:ga...@riseup.net]

> Inviato: martedì 24 maggio 2016 17:03

> A: Franco Cazzola

> Oggetto: Re: R: R: [Qgis-user] Dimension plugin in Qgis 2.10.1 Pisa

>

> hi,

> can you write in english, please ?

> Anyway, after loading the sample project you have to set the current

> dimension style.

> You can do it setting the dimstyle variable to "standard" value

> running the _setvar command or _dimstyle command.

> After that you can run dimlinear or dimaligned command.


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] [QGIS-Developer] Geodesic Measure Tool With Bearing Information

[Nyall Dawson]

On 12 June 2017 at 18:43, Neumann, Andreas  wrote:
> +1 for getting these improvements in QGIS core, rather than in a plugin.
>
> fyi: https://map.geo.admin.ch/ has an interesting "all-in-one" measure tool,
> which could server as an inspiration for QGIS.
>
> If you start with a new measure line, you first get a circle with distance
> and bearing. It also shows markers with labels along the line with round
> distances (e.g. 500m, 1000m, etc.). If you close the polygon by going back
> to the first vertex, it autosnaps and shows the area. So it is really just
> one single tool, but it helps to show distances, bearings and areas - along
> with an elevation profile.

That's quite nice! I wonder why the bearing/radius circle is only
shown for the first line segment though...

Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] [QGIS-Developer] Geodesic Measure Tool With Bearing Information

[Paolo Cavallini]

Il 12/06/2017 10:43, Neumann, Andreas ha scritto:
> +1 for getting these improvements in QGIS core, rather than in a plugin.

+1
thanks

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] [QGIS-Developer] Geodesic Measure Tool With Bearing Information

[Neumann, Andreas]

+1 for getting these improvements in QGIS core, rather than in a plugin.


fyi: https://map.geo.admin.ch/ has an interesting "all-in-one" measure
tool, which could server as an inspiration for QGIS. 

If you start with a new measure line, you first get a circle with
distance and bearing. It also shows markers with labels along the line
with round distances (e.g. 500m, 1000m, etc.). If you close the polygon
by going back to the first vertex, it autosnaps and shows the area. So
it is really just one single tool, but it helps to show distances,
bearings and areas - along with an elevation profile. 

Greetings, 

Andreas 

On 2017-06-12 10:27, Nyall Dawson wrote:

> 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 would you
>> want this with the QGIS measure tool or should it be a separate plugin?
> 
> My strong vote would be towards extending the QGIS measure tool. To me
> that's a better solution then requiring users to download a plugin,
> and having to reimplement all the (complex) logic of the measure tool
> again in a python plugin.
> 
>> 1. Where the current measure tool has 'Segments' there would be two more
>> columns with 'Bearing to' and 'Bearing from'.
> 
> Sounds good!
> 
>> 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 description of
> exactly how QGIS is calculating the distances. Is there something
> missing there?
> 
>> 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 are self contained, and
> the methods for calculating bearing are already present in the QGIS
> api). Then using geographiclib could be discussed as a separate set of
> changes, to be decided on its own merit. If you mix these two changes
> it's likely to get bogged down as one or other part of the changes are
> debated.
> 
>> If this is of interest then I will attempt to get a QGIS development
>> environment running to help make the changes to the core measure tool;
>> otherwise, I will just create a plugin to do this. If I create a plugin I
>> will use the geographiclib python library to do the calculations.
>> 
>> Thoughts?
> 
> Go the core! Let us know if you need help setting up a dev
> environment. It's actually much easier for 3.0 then it was for 2.x
> (especially on windows).
> 
> Nyall
> ___
> QGIS-Developer mailing list
> qgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Geodesic Measure Tool With Bearing Information

[Nyall Dawson]

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 would you
> want this with the QGIS measure tool or should it be a separate plugin?

My strong vote would be towards extending the QGIS measure tool. To me
that's a better solution then requiring users to download a plugin,
and having to reimplement all the (complex) logic of the measure tool
again in a python plugin.

>
> 1. Where the current measure tool has 'Segments' there would be two more
> columns with 'Bearing to' and 'Bearing from'.

Sounds good!

>
> 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 description of
exactly how QGIS is calculating the distances. Is there something
missing there?

> 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 are self contained, and
the methods for calculating bearing are already present in the QGIS
api). Then using geographiclib could be discussed as a separate set of
changes, to be decided on its own merit. If you mix these two changes
it's likely to get bogged down as one or other part of the changes are
debated.

> If this is of interest then I will attempt to get a QGIS development
> environment running to help make the changes to the core measure tool;
> otherwise, I will just create a plugin to do this. If I create a plugin I
> will use the geographiclib python library to do the calculations.
>
> Thoughts?

Go the core! Let us know if you need help setting up a dev
environment. It's actually much easier for 3.0 then it was for 2.x
(especially on windows).

Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user