If I'm reading this thread properly I'd suggest this may be a regression
in QGIS 3. There's a scenario (as explained by Richard) which was better
handled with QGIS 2.
I'd suggest opening a bug report for it and including as much
information as possible.
On 2018-10-18 09:50, magerlin wrote:
Thanks for your input (which I do not fully understand ;-)
I think you are pointing at possible problems at the server of the data
distributor?
But QGIS 2.18 reads it without problems - only QGIS 3 cannot?
-----
Regards Morten
Currently using Qgis 2.18.23 (OSGeo4) and Qgis 3.2.2 in parrallel
Windows 7, 64bit
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
_______________________________________________
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
