Re: [QGIS-Developer] Documentation and algorithm news

[Alexandre Neto]

Hi!

It seems that I have forgotten to send my reply to the mailing list...

matteo  escreveu no dia sexta, 16/03/2018 às 08:38:

> Hi Alexandre,
>
> > Maybe I am missing something, why would lose the information? Because it
> > has not been released?
>
>
> I mean that if not documented step by step (so new algorithms or changes
> to existing ones), in a couple or releases a lot of documentation will
> be orphaned.
>
> Right now (actually after months of discussions, PRs, ecc.) we have a
> pretty stable system also for this doc section and we should try to keep
> it updated like we are trying to do with the general doc.
>

I see no reason for us to not update any new feature imediately,
independently of the QGIS version it has landed. Testing documentation is
aiming for QGIS 3.4, until then, it's just that, testing documentation.

IMHO. After QGIS 3.4, if the documentation is too behind, we can think of
branching to allow keeping documenting new features arriving in master
(3.5+).

But as you well know we are too few to maintain all the dev work.. And I
> cannot see an easy way out of this.
>
> Matteo
>

cheers,

Alex
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Visual Changelog: ready? Move to Website? Or Not?

[Etienne Trimaille]

2018-03-16 13:39 GMT+01:00 Régis Haubourg :

> I would suggest that the validation workflow submits the new version to
> moderators, and that a copy of the old version stays published. A message
> to inform the author he needs some validation would be necessary too.
>

Régis, there is a ticket to remove the pending queue in projecta.
Please check and comment on https://github.com/kartoza/projecta/issues/806

Andreas, about translations of changelog, the 2.18 version has been fully
translated to French:
https://qgis.org/fr/site/forusers/visualchangelog218/index.html
We never know ;-)

Regards,
Etienne


>
> Cheers!
>
> Régis
>
>
>
> 2018-03-16 12:51 GMT+01:00 Andreas Neumann :
>
>> Hi,
>>
>> Personally, I don't think that the visual changelog will be translated (I
>> might be wrong though). Given that we struggle to get enough contributors
>> for even the english master version chances are low, that they will be
>> translates. I kind of promised to continue to work on it, but was too busy
>> with other stuff so far. I will have more time soon, though.
>>
>> Can we let it "as is" for now - let's say until the end of April (so
>> people can still contribute to it) and then copy it to our website at the
>> beginning of May o so? The nice thing about moving it to the website is
>> that we have an archive and no dependency on external services.
>>
>> Thanks,
>>
>> Andreas
>>
>> On 2018-03-16 11:52, Richard Duivenvoorde wrote:
>>
>>
>> See subject :-)
>>
>> Should we 'freeze' current status of the visual changelog?
>>
>> Or are there any items which should be a added/polished.
>>
>> For earlier releases we always 'ported' the changelog to the website:
>> https://qgis.org/en/site/forusers/visualchangelog218/index.html
>> This made the changelog translatable in the website.
>>
>> For 3.0 there is a temporary link to the changelog app now:
>> http://changelog.qgis.org/en/qgis/version/3.0.0/
>>
>> But... do we still want to move it to the website?
>> Or is everybody happy with a link to the above changelog application?
>>
>> I'm ok to move it to the website again, it's always some work because of
>> some styling issues... But that is ok.
>>
>> But if nobody cares, I'll go and do something else, or sit in the sun ;-)
>>
>> Regards,
>>
>> Richard Duivenvoorde
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Set text of QgsLayoutItemLabel

[KOHLMANN Hannes]

Hello!

I am facing difficulties trying to set the text of a  QgsLayoutItemLabel.
I do something like the following to load a .qpt composer template and print 
this to a .png file (which works)

path = "C:\\QGIS3\\apps\\qgis\\composer_templates"
template_file = open(path+"\\ANSR_print_composer2.qpt")
template_content = template_file.read()
template_file.close()

document = QDomDocument()
document.setContent(template_content)
composition = QgsLayout(QgsProject.instance())
composition.loadFromTemplate(document, QgsReadWriteContext())

map_item = composition.itemById('map')
legend_item = composition.itemById('legend')
text_item = composition.itemById('textbox')
QgsLayoutExporter(composition).exportToImage( path+"\\report.png", 
QgsLayoutExporter.ImageExportSettings())

And now I'd like to modify only the text of the QgsLayoutItemLabel, which is 
the "textbox":


1)  I can move it around with setX(), setY(), but I don't know how to edit 
the text of the label. I thought of something like text_item.setText() or 
text_item.setLabelText(), but I think that text_item is just an instance of 
QgsLayoutItem, not QgsLayoutItemLabel. And there I get stuck.

2)  How would you manually add another text label, set the main property 
etc, such that, at the end of the day, my above code would export a .png 
containing this QgsLayoutItem?
I would have begun this way:
new = QgsLayoutItemLabel(composition)
new.setText("New label")
But it does not quite work that way!

Would be of great help, if you could give me some hints on that.

Thank you in advance! :)

Hannes
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Bug ajout d'une couche WMS IGN

[Régis Haubourg]

Bonjour Thomas,
cette liste est dédiée aux développeurs QGIS et anglophone.
Ce type de question très française doit être adressée plutôt sur georezo /
forum QGIS ou la liste qgis utilisateurs fr
https://lists.osgeo.org/mailman/listinfo/qgis-fr-user
Regards
Régis

Le 16 mars 2018 à 15:34, thomas cerisay  a écrit :

> Bonjour,
>
>
>
> j'ai un problème pour ajouter des nouvelles couches WMS que j'ai obtenu
> via l'IGN avec une clé. Au moment où QGIS me demande de m'identifier pour
> avoir accès à mes couches IGN, la fenêtre d'identification se bloque à
> chaque fois et QGIS ne répond plus. Pouvez vous m'aider à résoudre ce
> problème?
>
>
>
> Cordialement
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Bug ajout d'une couche WMS IGN

[thomas cerisay]

Bonjour, 
 
j'ai un problème pour ajouter des nouvelles couches WMS que j'ai obtenu via 
l'IGN avec une clé. Au moment où QGIS me demande de m'identifier pour avoir 
accès à mes couches IGN, la fenêtre d'identification se bloque à chaque fois et 
QGIS ne répond plus. Pouvez vous m'aider à résoudre ce problème?
 
Cordialement___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-developer] $id not working as default value

[DelazJ]

Hi Nyall,


2016-12-27 2:03 GMT+01:00 Nyall Dawson :

> On 23 December 2016 at 23:37, Paolo Cavallini 
> wrote:
> > Il 23/12/2016 14:32, Giovanni Manghi ha scritto:
> >
> >> The solution from the Gitter discussion
> >>
> >> aggregate( 'layername','max',"id")+1
> >
> > thanks Giovanni
> >
> >> We need of course a more user friendly way to allow users have
> >> incremental/serial ids in their shapefiles...
> >
> > sure, e.g. a named preset expression, as previously suggested.
> > all the best.
>
> In master you can add UNIQUE and NOT NULL constraints to the field
> from within QGIS. This will cause QGIS to automatically populate it
> with a serial type value whenever a new feature is created.
>
>
How does this work? I thought to document this tip in the User manual and
wanted to give it a try before but always fail:
I created an integer field which is recognized in the Attribute Forms
dialog as a range
I checked "unique" and "not null" constraints (and unchecked "allow null
values" from the range widget properties)
The first created feature had value =0
The second one also got 0 with the yellow cross on the side But changes
(with two 0 values) are saved in the layer.
Enforcing the constraints do not help, neither do setting the widget as
"Text Edit".

Did I miss something (btw i'm using a temporary layer but also failed with
shapefile) or is it broken.
Any help is welcome.

Thanks,
Harrissou



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

Re: [QGIS-Developer] issues in QGIS Server 2,18

[René-Luc Dhont]

Hi Giovanni,

I have found the reason why QGIS Server 2.18 and probably 3 are slower 
than 2.14 in generating GeoJSON.

I'll fix it.

Regards,
René-Luc

Le 09/03/2018 à 17:43, Régis Haubourg a écrit :

Hi Giovanni,
 GetFeatures  can output GML with a different format.
What is sure is that GeoJSON spec doesn't leave any choice, unless we 
go for a proprietary output format allowing another SRS.
I'll keep that in mind when testing OGC compliancy for WFS. We are 
working on that currently to evaluate how much work is needed to reach 
a certification for WFS.

Regards
Régis

2018-03-09 14:34 GMT+01:00 Giovanni Manghi >:


Hi René-Luc,



> Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :
>> Hi all,
>> now that 2.18 is LTR I guess that many have also updated their QGIS
>> Server installation to this release. Problem is that I see a few
>> issues in 2.18 and would like to have gsome feedback from others.
>>
>> *) slower: it seems this version is slower compared to 2.14, at
least
>> for some specific request like WFS GetFeatures. See for example:
>>
>> https://issues.qgis.org/issues/18249#note-1

>>
>> where in the same condition (same server, same postgis
datasource of
>> around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.
>
> This issue is simply due to the transformation of the geometry
from the
> layer CRS to the GeoJSON CRS standard: EPSG:4326

ok thanks, but one doubt: I guess that this change (compared to 2.14)
was to make qgis server more compliant and this also means that we
need to accept that for such requests will be always slower than it
was before? sorry for the dumb question as I'm not much into the ogc
internals.


cheers

-- G --
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org 
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe:
https://lists.osgeo.org/mailman/listinfo/qgis-developer





___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] $geometry does not consider changes in the edit uffer

[Denis Rouzaud]

Hi Nyall,

Thanks for testing.

I tried again and still observe the issue.
I have found worst issues with setting this virtual fields with expression
"num_points( $geometry )"

- when adding a new feature and committing I get an error saying:
Feature has too many attributes (expecting 1, received 2)
although feature is correctly written to the provider

- the function seems to return actually 1 vertex more than there actually
is in the geometry

- I do need to commit to get the changes

I tested both with geopkg and shapefiles.
And I did not started alcohol yet today.

Cheers,
Denis




Le mar. 13 mars 2018 à 16:47, Nyall Dawson  a
écrit :

> On 14 March 2018 at 03:19, Denis Rouzaud  wrote:
> > Hi again,
> >
> > I'd like to bump this issue once more to the list
>
> >>
> >> If I set a virtual field with the vertex count (i.e. num_points(
> >> $geometry ) ), it does not consider changes in the edit buffer.
> >> In other words, I have to commit the changes so the expression is
> correct.
> >>
> >> Is this an expected behavior?
> >> I would have expect to be updated directly.
>
> I can't reproduce -- it works fine here (testing through the attribute
> table).
>
> Nyall
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Visual Changelog: ready? Move to Website? Or Not?

[Régis Haubourg]

Hi,

I agree with what Andreas proposes, ie announce clearly a date to the end
of April, then make a copy to the website.

I still try to polish the changelog currently, some entries are hard to
understand or deserve animated gif's and some entries can be factorized in
one only for a shorter changelog. If the changelog is too long to be read,
that means it is too long :)

Another glitch linked to the validation workflow. When someone submit an
entry, the entry disappears until it is validated. So that leaded to
duplicates, probably because some thought they had an issue with the
website.

I would suggest that the validation workflow submits the new version to
moderators, and that a copy of the old version stays published. A message
to inform the author he needs some validation would be necessary too.

Cheers!

Régis



2018-03-16 12:51 GMT+01:00 Andreas Neumann :

> Hi,
>
> Personally, I don't think that the visual changelog will be translated (I
> might be wrong though). Given that we struggle to get enough contributors
> for even the english master version chances are low, that they will be
> translates. I kind of promised to continue to work on it, but was too busy
> with other stuff so far. I will have more time soon, though.
>
> Can we let it "as is" for now - let's say until the end of April (so
> people can still contribute to it) and then copy it to our website at the
> beginning of May o so? The nice thing about moving it to the website is
> that we have an archive and no dependency on external services.
>
> Thanks,
>
> Andreas
>
> On 2018-03-16 11:52, Richard Duivenvoorde wrote:
>
>
> See subject :-)
>
> Should we 'freeze' current status of the visual changelog?
>
> Or are there any items which should be a added/polished.
>
> For earlier releases we always 'ported' the changelog to the website:
> https://qgis.org/en/site/forusers/visualchangelog218/index.html
> This made the changelog translatable in the website.
>
> For 3.0 there is a temporary link to the changelog app now:
> http://changelog.qgis.org/en/qgis/version/3.0.0/
>
> But... do we still want to move it to the website?
> Or is everybody happy with a link to the above changelog application?
>
> I'm ok to move it to the website again, it's always some work because of
> some styling issues... But that is ok.
>
> But if nobody cares, I'll go and do something else, or sit in the sun ;-)
>
> Regards,
>
> Richard Duivenvoorde
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Visual Changelog: ready? Move to Website? Or Not?

[Andreas Neumann]

Hi, 

Personally, I don't think that the visual changelog will be translated
(I might be wrong though). Given that we struggle to get enough
contributors for even the english master version chances are low, that
they will be translates. I kind of promised to continue to work on it,
but was too busy with other stuff so far. I will have more time soon,
though. 

Can we let it "as is" for now - let's say until the end of April (so
people can still contribute to it) and then copy it to our website at
the beginning of May o so? The nice thing about moving it to the website
is that we have an archive and no dependency on external services. 

Thanks, 

Andreas 

On 2018-03-16 11:52, Richard Duivenvoorde wrote:

> See subject :-)
> 
> Should we 'freeze' current status of the visual changelog?
> 
> Or are there any items which should be a added/polished.
> 
> For earlier releases we always 'ported' the changelog to the website:
> https://qgis.org/en/site/forusers/visualchangelog218/index.html
> This made the changelog translatable in the website.
> 
> For 3.0 there is a temporary link to the changelog app now:
> http://changelog.qgis.org/en/qgis/version/3.0.0/
> 
> But... do we still want to move it to the website?
> Or is everybody happy with a link to the above changelog application?
> 
> I'm ok to move it to the website again, it's always some work because of
> some styling issues... But that is ok.
> 
> But if nobody cares, I'll go and do something else, or sit in the sun ;-)
> 
> Regards,
> 
> Richard Duivenvoorde
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Add "QGIS3 compatible" link to plugins repo on the web

[Alessandro Pasotti]

On Fri, Mar 16, 2018 at 12:41 PM, Richard Duivenvoorde 
wrote:

> On 16-03-18 12:33, Alessandro Pasotti wrote:
>
> > I reckon for a Django guru it should be not so difficult?
> > FYI: current plugin site is a django website:
> > https://github.com/qgis/qgis-django
> > 
> >
> > Any takers?
> >
> >
> > I suppose it's need to be me :)
>
> No, Non, Nee, Nein :)
>
> My (honest) intention was truly to invite somebody else wanting to
> invest some time in community work. And this looks line a nice
> 'incomer'-task?
>
> Unless you're afraid that that will ruin all your work off course ;-)
>
>
No problems then, if the crowd of volunteers needs help, I'm here  ;)


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Add "QGIS3 compatible" link to plugins repo on the web

[Richard Duivenvoorde]

On 16-03-18 12:33, Alessandro Pasotti wrote:

> I reckon for a Django guru it should be not so difficult?
> FYI: current plugin site is a django website:
> https://github.com/qgis/qgis-django
> 
> 
> Any takers?
> 
> 
> I suppose it's need to be me :)

No, Non, Nee, Nein :)

My (honest) intention was truly to invite somebody else wanting to
invest some time in community work. And this looks line a nice
'incomer'-task?

Unless you're afraid that that will ruin all your work off course ;-)

Regards,

Richard


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Add "QGIS3 compatible" link to plugins repo on the web

[Alessandro Pasotti]

On Fri, Mar 16, 2018 at 12:30 PM, Richard Duivenvoorde 
wrote:

> On 16-03-18 12:21, Tom Chadwin wrote:
> > Hello all
> >
> > There are quite a lot of questions, comments, and opinions expressed
> online
> > about the availability of plugins in QGIS3. How easy would it be to add
> > another plugins filter link to the menu on http://plugins.qgis.org/
> plugins/
> > (the one with My plugins, Featured, All, Stable, Fresh, Experimental,
> etc)
> > which only shows plugins with minversion <= 2.99 and maxversion >=2.99?
> >
> > This would allow people to check plugin availability easily without
> > upgrading to QGIS3 on spec.
>
> Hi Tom,
>
> good idea, we could (where now is 'All plugins') maybe add:
> - '3.x' plugins
> - '2.x' plugins
>
> then pointing to https://plugins.qgis.org/plugins/?qgis=3
> and https://plugins.qgis.org/plugins/?qgis=2
>
> I reckon for a Django guru it should be not so difficult?
> FYI: current plugin site is a django website:
> https://github.com/qgis/qgis-django
>
> Any takers?
>

I suppose it's need to be me :)


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Future of OSM integration

[Etienne Trimaille]

2018-03-16 12:21 GMT+01:00 Alexander Bruy :

> I think it should be QuickOSM plugin.
>

I got a few requests this week when the port to QGIS 3 will be done about
QuickOSM. I'm planning to do that next week.



> 2018-03-16 11:36 GMT+02:00 DelazJ :
> > Hi,
> >
> > Following this discussion, the "Vector --> OpenStreetMap" feature has
> been
> > removed from QGIS3 [0].
> > Issue is that in the Training manual, it's the first tool used to help
> users
> > download data to work with [1] (and also used in other places). This
> > situation renders some exercises obsolete.
> > Question (to trainers?): what would then be the appropriate replacement
> > tool, here, in the Training manual?
> >
> > [0] https://github.com/qgis/QGIS/pull/5354
> > [1]
> > https://docs.qgis.org/testing/en/docs/training_manual/
> foreword/preparing_data.html#hard-ty
> >
> > Regards,
> > Harrissou
> >
> >
> > 2017-10-12 16:37 GMT+02:00 Andre Joost :
> >>
> >>
> >> Am 12.10.2017 um 10:26 schrieb Tim Sutton:
> >> > Hi
> >> >
> >> >> On 12 Oct 2017, at 10:20, Martin Dobias 
> >> >> wrote:
> >> >>
> >> >>
> >> >> So my question really is - shall we just get rid of it? Would
> >> >> anyone miss it? :-)
> >> >
> >> > Sorry to say I wont miss it :-( There is quick-osm and InaSAFE also
> >> > has a downloader and I think if we were going to have something in
> core,
> >> > Quick OSM would be a better choice. So +1 from me to clean house.
> >> >Let’s see if others have different ideas…
> >> >
> >>
> >> Unless https://issues.qgis.org/issues/10790 gets fixed, the importer is
> >> broken for data that is newly added to the OSM database.
> >> The OGR import and QuickOSM can handle that better.
> >>
> >> Greetings,
> >> André Joost
> >>
> >> ___
> >> QGIS-Developer mailing list
> >> QGIS-Developer@lists.osgeo.org
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> >
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alexander Bruy
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Add "QGIS3 compatible" link to plugins repo on the web

[Richard Duivenvoorde]

On 16-03-18 12:21, Tom Chadwin wrote:
> Hello all
> 
> There are quite a lot of questions, comments, and opinions expressed online
> about the availability of plugins in QGIS3. How easy would it be to add
> another plugins filter link to the menu on http://plugins.qgis.org/plugins/
> (the one with My plugins, Featured, All, Stable, Fresh, Experimental, etc)
> which only shows plugins with minversion <= 2.99 and maxversion >=2.99?
> 
> This would allow people to check plugin availability easily without
> upgrading to QGIS3 on spec.

Hi Tom,

good idea, we could (where now is 'All plugins') maybe add:
- '3.x' plugins
- '2.x' plugins

then pointing to https://plugins.qgis.org/plugins/?qgis=3
and https://plugins.qgis.org/plugins/?qgis=2

I reckon for a Django guru it should be not so difficult?
FYI: current plugin site is a django website:
https://github.com/qgis/qgis-django

Any takers?

Regards,

Richard Duivenvoorde


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Future of OSM integration

[Tom Chadwin]

My apologies. I missed the crucial word "vector" in Harrissou's message.
Sorry for the noise.

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Add "QGIS3 compatible" link to plugins repo on the web

[Tom Chadwin]

Hello all

There are quite a lot of questions, comments, and opinions expressed online
about the availability of plugins in QGIS3. How easy would it be to add
another plugins filter link to the menu on http://plugins.qgis.org/plugins/
(the one with My plugins, Featured, All, Stable, Fresh, Experimental, etc)
which only shows plugins with minversion <= 2.99 and maxversion >=2.99?

This would allow people to check plugin availability easily without
upgrading to QGIS3 on spec.

Thanks

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Future of OSM integration

[Alexander Bruy]

I think it should be QuickOSM plugin.

2018-03-16 11:36 GMT+02:00 DelazJ :
> Hi,
>
> Following this discussion, the "Vector --> OpenStreetMap" feature has been
> removed from QGIS3 [0].
> Issue is that in the Training manual, it's the first tool used to help users
> download data to work with [1] (and also used in other places). This
> situation renders some exercises obsolete.
> Question (to trainers?): what would then be the appropriate replacement
> tool, here, in the Training manual?
>
> [0] https://github.com/qgis/QGIS/pull/5354
> [1]
> https://docs.qgis.org/testing/en/docs/training_manual/foreword/preparing_data.html#hard-ty
>
> Regards,
> Harrissou
>
>
> 2017-10-12 16:37 GMT+02:00 Andre Joost :
>>
>>
>> Am 12.10.2017 um 10:26 schrieb Tim Sutton:
>> > Hi
>> >
>> >> On 12 Oct 2017, at 10:20, Martin Dobias 
>> >> wrote:
>> >>
>> >>
>> >> So my question really is - shall we just get rid of it? Would
>> >> anyone miss it? :-)
>> >
>> > Sorry to say I wont miss it :-( There is quick-osm and InaSAFE also
>> > has a downloader and I think if we were going to have something in core,
>> > Quick OSM would be a better choice. So +1 from me to clean house.
>> >Let’s see if others have different ideas…
>> >
>>
>> Unless https://issues.qgis.org/issues/10790 gets fixed, the importer is
>> broken for data that is newly added to the OSM database.
>> The OGR import and QuickOSM can handle that better.
>>
>> Greetings,
>> André Joost
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alexander Bruy
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Future of OSM integration

[Alexander Bruy]

These are not related at all to the raised question.

2018-03-16 13:15 GMT+02:00 Tom Chadwin :
> Native XYZ layer, calling the OSM raster tiles? Alternatively,
> QuickMapServices is now funded, and should be published soon.
>
> Tom
>
>
>
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alexander Bruy
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Future of OSM integration

[Tom Chadwin]

Native XYZ layer, calling the OSM raster tiles? Alternatively,
QuickMapServices is now funded, and should be published soon.

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Visual Changelog: ready? Move to Website? Or Not?

[Richard Duivenvoorde]

See subject :-)

Should we 'freeze' current status of the visual changelog?

Or are there any items which should be a added/polished.

For earlier releases we always 'ported' the changelog to the website:
https://qgis.org/en/site/forusers/visualchangelog218/index.html
This made the changelog translatable in the website.

For 3.0 there is a temporary link to the changelog app now:
http://changelog.qgis.org/en/qgis/version/3.0.0/

But... do we still want to move it to the website?
Or is everybody happy with a link to the above changelog application?

I'm ok to move it to the website again, it's always some work because of
some styling issues... But that is ok.

But if nobody cares, I'll go and do something else, or sit in the sun ;-)

Regards,

Richard Duivenvoorde
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Michel Stuyts]

Sophie,

What happens if you add the full path before the pyrcc5 command when you’re in 
the plugin folder?

So  you go to the plugin folder and there you run:
C:\OSGeo4W64\apps\Python36\Scripts\pyrcc5 –o resources.py resources.qrc

Michel



Van: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] Namens 
Sophie Crommelinck
Verzonden: vrijdag 16 maart 2018 10:53
Aan: KOHLMANN Hannes ; j...@norbit.de
CC: qgis-developer@lists.osgeo.org
Onderwerp: Re: [QGIS-Developer] Unable to compile QGIS3 plugin

I think my images broke while sending,
here they are again:

Jürgen's suggestion:
[cid:image002.jpg@01D3BD17.8A7FB8C0]
Hannes' suggestion:
[cid:image004.jpg@01D3BD17.8A7FB8C0]
python-core.bat
[cid:image005.png@01D3BD17.8A7FB8C0]


2018-03-16 10:45 GMT+01:00 Sophie Crommelinck 
>:
Hello Jürgen and Hannes,
thanks for your support. I tried both suggestions, with little success.
Jürgen's suggestion:
[http://?ui=2=ad514a8e24=att=1622e15a2bbbae15=0.1=safe=ii_jetq74350_1622e15a2bbbae15]
This creates the resources.py file (attached). However, when I open QGIS3 it 
crashes every time I reload the plugin (crash report attached).
Hannes' suggestion:
[http://?ui=2=ad514a8e24=att=1622e24472fdda7d=0.2=safe=ii_jetqrnzt1_1622e24472fdda7d]
which results in the same as above. However, here I am not entirely sure if I 
followed the suggestion correctly as I go back to the plugin folder for 
compiling.
Also, I wonder, why the result of calling python-qgis-dev.bat lists win32, 
while I have a win64 machine.

I also tried changing the python path as suggested in the stack exchange 
question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success
[http://?ui=2=ad514a8e24=att=1622e29d99d79ebd=0.0.3=safe=ii_jetqzhre4_1622e29d99d79ebd]
Best,
Sophie




2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes 
>:
Hey Sophie!

There is one .bat file that does all the work of setting the Environment 
variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
Call that file in the console and in the same console cd to the directory with 
the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)

Here is the link to a gis.stackexchange question concerning that:
https://gis.stackexchange.com/questions/260743/how-to-compile-qtdesigner-user-interface-ui-and-resource-qrc-files-with-qg/264377#264377

Good luck and compiling ;)

Cheers,
Hannes
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[KOHLMANN Hannes]

Hey Sophie!

Exactly. You first call …/pyrcc.bat without any arguments, and the console 
tells you what arguments pyrcc.bat takes.
Then you change directory, away from the pyrcc.bat and try to call after having 
changed to the directory where your resource file is.

Remain in the folder where the pyrcc5.bat is (otherwise the console will not 
know the command) and give the absolute paths of your target files in quotation 
mark (in case you have whitespaces in your dirs.) like I did in the below 
screenshot.

You might encounter the same problem with the pyuic5.bat -> which you use, when 
you want to translate the .ui file to python code with the pyqt5 bindings. In 
that case, I built myself a .bat file with the following commands, making the 
same as Jürgen suggested, (just in case of further tampering attempts ;) )

REM take all .ui files and apply it to the pyuic5.bat to all of them and output 
them as .py files
REM when calling this batch file the first argument needs to be the path to 
/python36/script
pushd %~dp0
echo off
call c:
cd %1
cd ../../../bin/
call "o4w_env.bat"
call qt5_env.bat
call py3_env.bat

path %OSGEO4W_ROOT%\apps\qgis-dev\bin;%PATH%
set QGIS_PREFIX_PATH=%OSGEO4W_ROOT:\=/%/apps/qgis-dev
set GDAL_FILENAME_IS_UTF8=YES
rem Set VSI cache to be used as buffer, see #6448
set VSI_CACHE=TRUE
set VSI_CACHE_SIZE=100
set 
QT_PLUGIN_PATH=%OSGEO4W_ROOT%\apps\qgis-dev\qtplugins;%OSGEO4W_ROOT%\apps\qt5\plugins
set PYTHONPATH=%OSGEO4W_ROOT%\apps\qgis-dev\python;%PYTHONPATH%

echo off

popd
for %%i in (*.ui) do (
call "%1\pyuic5.bat" -o "%%~ni.py" "%%~ni.ui"
)

I hope that helped

Cheers,
Hannes


[cid:image006.png@01D3BD18.F7381970]

Von: Sophie Crommelinck [mailto:sophie.crommeli...@gmail.com]
Gesendet: Freitag, 16. März 2018 10:53
An: KOHLMANN Hannes; j...@norbit.de
Cc: qgis-developer@lists.osgeo.org
Betreff: Re: [QGIS-Developer] Unable to compile QGIS3 plugin

I think my images broke while sending,
here they are again:

Jürgen's suggestion:
[cid:image002.jpg@01D3BD19.8B6D6230]
Hannes' suggestion:
[cid:image004.jpg@01D3BD19.8B6D6230]
python-core.bat
[cid:image005.png@01D3BD16.85DD2830]


2018-03-16 10:45 GMT+01:00 Sophie Crommelinck 
>:
Hello Jürgen and Hannes,
thanks for your support. I tried both suggestions, with little success.
Jürgen's suggestion:
[http://?ui=2=ad514a8e24=att=1622e15a2bbbae15=0.1=safe=ii_jetq74350_1622e15a2bbbae15]
This creates the resources.py file (attached). However, when I open QGIS3 it 
crashes every time I reload the plugin (crash report attached).
Hannes' suggestion:
[http://?ui=2=ad514a8e24=att=1622e24472fdda7d=0.2=safe=ii_jetqrnzt1_1622e24472fdda7d]
which results in the same as above. However, here I am not entirely sure if I 
followed the suggestion correctly as I go back to the plugin folder for 
compiling.
Also, I wonder, why the result of calling python-qgis-dev.bat lists win32, 
while I have a win64 machine.

I also tried changing the python path as suggested in the stack exchange 
question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success
[http://?ui=2=ad514a8e24=att=1622e29d99d79ebd=0.0.3=safe=ii_jetqzhre4_1622e29d99d79ebd]
Best,
Sophie




2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes 
>:
Hey Sophie!

There is one .bat file that does all the work of setting the Environment 
variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
Call that file in the console and in the same console cd to the directory with 
the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)

Here is the link to a gis.stackexchange question concerning that:
https://gis.stackexchange.com/questions/260743/how-to-compile-qtdesigner-user-interface-ui-and-resource-qrc-files-with-qg/264377#264377

Good luck and compiling ;)

Cheers,
Hannes
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

 I think my images broke while sending,

here they are again:

*Jürgen's suggestion:*

*Hannes' suggestion:*


*python-core.bat*


2018-03-16 10:45 GMT+01:00 Sophie Crommelinck 
:

> Hello Jürgen and Hannes,
>
> thanks for your support. I tried both suggestions, with little success.
>
> *Jürgen's suggestion:*
>
> This creates the resources.py file (attached). However, when I open QGIS3
> it crashes every time I reload the plugin (crash report attached).
>
> *Hannes' suggestion:*
>
> which results in the same as above. However, here I am not entirely sure
> if I followed the suggestion correctly as I go back to the plugin folder
> for compiling.
> Also, I wonder, why the result of calling python-qgis-dev.bat lists win32,
> while I have a win64 machine.
>
>
> I also tried changing the python path as suggested in the stack exchange
> question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success
>
>
> Best,
>
> Sophie
>
>
>
>
>
> 2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes :
>
>> Hey Sophie!
>>
>> There is one .bat file that does all the work of setting the Environment
>> variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
>> Call that file in the console and in the same console cd to the directory
>> with the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)
>>
>> Here is the link to a gis.stackexchange question concerning that:
>> https://gis.stackexchange.com/questions/260743/how-to-compil
>> e-qtdesigner-user-interface-ui-and-resource-qrc-files-
>> with-qg/264377#264377
>>
>> Good luck and compiling ;)
>>
>> Cheers,
>> Hannes
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

Hello Jürgen and Hannes,

thanks for your support. I tried both suggestions, with little success.

*Jürgen's suggestion:*

This creates the resources.py file (attached). However, when I open QGIS3
it crashes every time I reload the plugin (crash report attached).

*Hannes' suggestion:*

which results in the same as above. However, here I am not entirely sure if
I followed the suggestion correctly as I go back to the plugin folder for
compiling.
Also, I wonder, why the result of calling python-qgis-dev.bat lists win32,
while I have a win64 machine.


I also tried changing the python path as suggested in the stack exchange
question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success


Best,

Sophie





2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes :

> Hey Sophie!
>
> There is one .bat file that does all the work of setting the Environment
> variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
> Call that file in the console and in the same console cd to the directory
> with the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)
>
> Here is the link to a gis.stackexchange question concerning that:
> https://gis.stackexchange.com/questions/260743/how-to-
> compile-qtdesigner-user-interface-ui-and-resource-qrc-
> files-with-qg/264377#264377
>
> Good luck and compiling ;)
>
> Cheers,
> Hannes
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
# -*- coding: utf-8 -*-

# Resource object code
#
# Created by: The Resource Compiler for PyQt5 (Qt v5.9.2)
#
# WARNING! All changes made in this file will be lost!

from PyQt5 import QtCore

qt_resource_data = b"\
\x00\x00\x04\x0a\
\x89\
\x50\x4e\x47\x0d\x0a\x1a\x0a\x00\x00\x00\x0d\x49\x48\x44\x52\x00\
\x00\x00\x17\x00\x00\x00\x18\x08\x06\x00\x00\x00\x11\x7c\x66\x75\
\x00\x00\x00\x01\x73\x52\x47\x42\x00\xae\xce\x1c\xe9\x00\x00\x00\
\x06\x62\x4b\x47\x44\x00\xff\x00\xff\x00\xff\xa0\xbd\xa7\x93\x00\
\x00\x00\x09\x70\x48\x59\x73\x00\x00\x0b\x13\x00\x00\x0b\x13\x01\
\x00\x9a\x9c\x18\x00\x00\x00\x07\x74\x49\x4d\x45\x07\xd9\x02\x15\
\x16\x11\x2c\x9d\x48\x83\xbb\x00\x00\x03\x8a\x49\x44\x41\x54\x48\
\xc7\xad\x95\x4b\x68\x5c\x55\x18\xc7\x7f\xe7\xdc\x7b\x67\xe6\xce\
\x4c\x66\x26\x49\xd3\x24\x26\xa6\xc6\xf8\x40\x21\xa5\x04\xb3\x28\
\xda\x98\x20\xa5\x0b\xad\x55\xa8\x2b\xc5\x50\x1f\xa0\x6e\x34\x2b\
\x45\x30\x14\x02\xba\x52\x69\x15\x17\x66\x63\x45\x97\x95\xa0\xad\
\x0b\xfb\xc0\x06\x25\xb6\x71\x61\x12\x41\x50\xdb\x2a\x21\xd1\xe2\
\x24\xf3\x9e\xc9\xcc\xbd\xe7\x1c\x17\x35\x43\x1e\x33\x21\xb6\xfd\
\x56\x87\xf3\x9d\xfb\xfb\x1e\xf7\xff\x9d\x23\x8c\x31\x43\x95\xf4\
\x85\x1e\x3f\x3b\x35\xac\xfd\xcc\x43\xdc\xa4\x49\x3b\xfe\x9d\x1d\
\xdb\x7b\x22\x90\x78\xf8\xb2\x28\xa7\xbe\x7d\xc1\x4b\x9d\x79\xdf\
\x18\x15\xe5\x16\x99\x10\x56\xde\x69\xdc\x3f\x22\xfd\xec\xd4\xf0\
\xad\x04\x03\x18\xa3\xa2\x7e\x76\x6a\x58\xde\x68\x2b\xb4\x36\xf8\
\xbe\xc6\x18\x53\xdb\xef\xe7\xfa\xec\xed\x67\x63\x10\x42\x00\xf0\
\xfb\xd5\x65\x2a\x15\x45\xc7\x6d\x0d\x00\xc4\xa2\xc1\xaa\x6f\x0d\
\x3e\x6c\xab\xc2\x1c\x56\xa4\x77\x4b\xb0\xf2\x35\x15\x5f\x21\x85\
\xe0\xc8\x6b\x5f\x92\x2d\x37\x33\x39\xf9\x03\x27\x8e\x1f\xa2\xf7\
\xbe\x9d\x04\x1c\x0b\x37\xe4\xac\xff\xa6\x30\x87\xbd\xba\x00\x6a\
\x06\x79\xe5\xf5\xaf\x89\xd9\x92\xc5\xcc\x0a\xd9\x7c\x19\xcf\xe9\
\xe2\xe4\xa9\x2f\x78\x7c\xff\x01\x72\x85\x0a\x2b\x65\x1f\xa5\x4c\
\xb5\xb2\x55\x16\x80\xbd\x31\xda\xda\x20\x1f\x7d\x3e\xcd\xc2\xfd\
\x59\xa6\x93\x39\x92\xd1\x22\xea\x9b\x16\xce\x9d\x3f\xce\xe0\x83\
\x03\x24\x82\x59\x3a\xdb\x7b\x88\xc7\x82\x68\x63\x58\xc9\xcc\x62\
\x8c\x21\x18\xb0\x6a\xc3\x37\x06\x49\x16\xff\x24\x6b\xa5\x49\xbb\
\x25\xbc\xa2\xa6\x21\xbb\x40\x7f\xdf\x00\x83\xbd\x01\x8e\x3c\xd5\
\x45\xd7\x8e\x6b\x9c\x9c\x98\x25\x1a\xb6\xe8\xbe\x3d\xc2\xdd\x77\
\x44\x48\xc4\x1c\x22\xe1\xeb\x58\x59\xaf\xcf\xd3\x33\x29\x2e\x34\
\x2d\x91\x93\x3e\xbe\x34\x78\x01\xc5\xe2\x61\xc5\xae\x72\x8e\x70\
\xc8\xc2\x0d\x5a\xbc\xf5\xee\x2f\x9c\xfa\x3e\x86\x69\x7a\x8e\xcf\
\x26\xe6\xf9\x63\xa1\x44\xa1\xa4\xd0\xda\x6c\x0d\x2f\x15\x7c\xb4\
\x67\x28\x59\x0a\xcf\xd6\x54\xe2\x06\x13\x87\x2b\x6f\x68\xa6\x27\
\xaf\x31\x32\x36\xc7\xb2\x7f\x17\xef\x7d\x7c\x8c\x33\x67\xcf\x12\
\x70\x24\x4a\x69\xd6\x6a\x46\xd6\xd3\x70\x72\xa9\x82\x67\x34\x45\
\xad\x28\xdb\x1a\x15\x34\x98\xff\x46\xed\xef\x37\x0d\x99\xbf\x4a\
\x3c\x30\x38\xc0\xc8\x4b\xaf\x92\x5a\x9c\xe2\xe0\x23\x6d\x74\xb4\
\xba\x84\x5d\x0b\x29\x45\x7d\xb8\x94\x82\x96\xb6\x10\xf3\xc5\x12\
\x2a\xef\x53\x11\x1a\x63\xad\x3f\x93\x19\x85\xf1\xb1\x77\x58\x5a\
\xf8\x99\x97\x9f\xe9\xa6\x75\x47\x90\xc6\xb8\x43\xd8\xb5\xb6\xce\
\xfc\xfa\xfd\x00\xfb\x3e\xf4\xc8\x05\x35\xba\x5e\xeb\x46\x21\xf9\
\xcf\x0a\xa9\x8c\x87\xe3\x48\xdc\x90\xb5\x6e\x98\x6a\xaa\x65\xf2\
\x52\x92\x43\x2f\x5e\xc2\x8c\x02\x1a\x10\xf5\x07\xac\xc3\x75\x70\
\x83\x92\x80\xb3\xf9\xd0\x26\xf8\x8f\xb3\x29\xc6\x3e\xb8\x8c\x19\

Re: [QGIS-Developer] Future of OSM integration

[DelazJ]

Hi,

Following this discussion, the "Vector --> OpenStreetMap" feature has been
removed from QGIS3 [0].
Issue is that in the Training manual, it's the first tool used to help
users download data to work with [1] (and also used in other places). This
situation renders some exercises obsolete.
Question (to trainers?): what would then be the appropriate replacement
tool, here, in the *Training manual*?

[0] https://github.com/qgis/QGIS/pull/5354
[1]
https://docs.qgis.org/testing/en/docs/training_manual/foreword/preparing_data.html#hard-ty

Regards,
Harrissou


2017-10-12 16:37 GMT+02:00 Andre Joost :

>
> Am 12.10.2017 um 10:26 schrieb Tim Sutton:
> > Hi
> >
> >> On 12 Oct 2017, at 10:20, Martin Dobias 
> >> wrote:
> >>
> >>
> >> So my question really is - shall we just get rid of it? Would
> >> anyone miss it? :-)
> >
> > Sorry to say I wont miss it :-( There is quick-osm and InaSAFE also
> > has a downloader and I think if we were going to have something in core,
> > Quick OSM would be a better choice. So +1 from me to clean house.
> >Let’s see if others have different ideas…
> >
>
> Unless https://issues.qgis.org/issues/10790 gets fixed, the importer is
> broken for data that is newly added to the OSM database.
> The OGR import and QuickOSM can handle that better.
>
> Greetings,
> André Joost
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer