> Issue created: https://issues.qgis.org/issues/20098
thanks Etienne!
Cheers
Matteo
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe:
Issue created: https://issues.qgis.org/issues/20098
Le ven. 12 oct. 2018 à 10:34, matteo a écrit :
> Hi Etienne,
>
> thanks for the clarifications.
>
> Please let me know if I can help to fix this issue, QuickOSM is a must :)
>
> Cheers
>
> Matteo
>
Hi Etienne,
thanks for the clarifications.
Please let me know if I can help to fix this issue, QuickOSM is a must :)
Cheers
Matteo
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
As a temporary workaround, after you executed your query, go in your
temporary folder (/tmp on linux) and open manually the latest OSM file
provided.
Le ven. 12 oct. 2018 à 07:52, Etienne Trimaille
a écrit :
> Hi Matteo,
>
> I noticed the issue too.
>
> With QGIS 3.2, no problem, QuickOSM is
Hi Matteo,
I noticed the issue too.
With QGIS 3.2, no problem, QuickOSM is working well.
With QGIS 3.3, not working since 1 week. But QuickOSM is not failling in
its processing, no python error. The plugin raises a warning if no OSM
object are found, but this is not the case, no warnings. So it
Hi Harrissou,
> Yes. I had the same issue last week-end. I tried on an area it
> downloaded some data a week ago and I ended up with empty layers (even
> when trying to download data I already had). Thought I was doing
> something wrong and gave up.
ok glad to hear that I'm not the only one. I
Hi Mattheo
Yes. I had the same issue last week-end. I tried on an area it downloaded
some data a week ago and I ended up with empty layers (even when trying to
download data I already had). Thought I was doing something wrong and gave
up.
Greetings,
Harrissou
Le ven. 12 oct. 2018 à 09:38,