I released qgis2web 1.4.0 (stable) yesterday. It's the first stable release
since 1.0.0, and the first stable release of the 2.5d renderer. Thanks once
again to Anita, Luigi, Nyall, and Matthias for all their help in getting
this more stable.
--
View this message in context:
On Tue, Mar 15, 2016 at 12:18 PM, Tom Chadwin
wrote:
> I've corrected that error (no idea why it has never failed for me) in
> master
> on Github, and published to the QGIS plugins repo as 1.3.1 experimental.
>
Great, now it works!
Thanks and best wishes,
Anita
1.3.2 released to fix the bug mentioned above.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5257209.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.
___
Qgis-user
Splendid. Many thanks for the patient testing. However, please be aware of a
nasty bug in the 2.5d renderer:
https://github.com/tomchadwin/qgis2web/issues/221
I can't solve it yet. I've asked for help
(https://lists.osgeo.org/pipermail/qgis-developer/2016-March/041965.html),
but with no reply
Hi Anita
I've corrected that error (no idea why it has never failed for me) in master
on Github, and published to the QGIS plugins repo as 1.3.1 experimental.
Thanks
Tom
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5256425.html
You're right. I have missed that one. Try changing that line to:
symbol = renderer.symbolForFeature2(feature, renderContext)
correctly indented, of course. Thanks!
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5256326.html
Sent from
I'm not at a machine to check, and it could be that I've just missed an
instance of that error, but it almost seems like your plugin is not properly
upgraded. I tried to change all instances of symbolForFeature() to
symbolForFeature2(). Are you able to compare that line which throws the
error in
Seems like it works well on another machine ...
Maybe it's just this one machine which has issues.
Best wishes,
Anita
On Mon, Mar 14, 2016 at 9:32 PM, Anita Graser wrote:
>
>
> On Mon, Mar 14, 2016 at 9:08 PM, Tom Chadwin
> wrote:
>
>> Hrm. I
On Mon, Mar 14, 2016 at 9:08 PM, Tom Chadwin
wrote:
> Hrm. I wonder if Luigi is right. Try running it with the Python console
> open.
> If it still doesn't work, can you try commenting out the print line? It's
> just for debugging. Thanks for testing. Very much
Hrm. I wonder if Luigi is right. Try running it with the Python console open.
If it still doesn't work, can you try commenting out the print line? It's
just for debugging. Thanks for testing. Very much appreciated.
--
View this message in context:
Just upgraded to 1.3.0 but unfortunately no change here. The current error
looks like this:
https://www.dropbox.com/s/ajkz0phmmbwyo42/Screenshot%202016-03-14%2021.16.23.png?dl=0
I'll try on another machine ...
Best wishes,
Anita
On Mon, Mar 14, 2016 at 6:04 PM, Tom Chadwin
I've just uploaded qgis2web 1.3.0 (still experimental), which should fix the
error you were experiencing - many apologies. It was caused by my misreading
the API docs and missing a difference between a C++ method and its bound
Python method.
Also, it should now work on converted 2.5d layers. That
Oh dear. That looks like a bad mistake by me. I think I must have mistakenly
committed some half-built code. I'll fix tomorrow. Is the issue serious
enough that I should delete that version from the plugins repo?
Apologies, all, and thanks, both, for your patience and help in debugging
this one.
Just updated to 1.2.1 and now neither OpenLayers nor Leaflet work.
Best wishes,
Anita
On Thu, Mar 10, 2016 at 7:27 PM, Anita Graser wrote:
> Hi,
>
> Openlayers prints:
>
> Traceback (most recent call last):
> File
Hi,
Openlayers prints:
Traceback (most recent call last):
File "C:/Users/anita/.qgis2/python/plugins\qgis2web\utils.py", line 122,
in exportLayers
symbol = layer.rendererV2().symbolForFeature(feat)
TypeError: Qgs25DRenderer.symbolForFeature(QgsFeature, QgsRenderContext):
not enough
I never investigated this problems deeply... happen only on win, and
seems that stdout is not available by default (=> bad file descriptor)
Anita, did you check if the problem disappear with the qgis python
console opened?
cheers
Luigi Pirelli
Really? print causes an error in Windows if the console is not open?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5255594.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.
Hi Anita,
try to leave opened the Python Console... in Win there is no default
stdout and can happen it is not available executing the print command
(never use print in multi platform qgis plugin)
in this way you'll have the traceback print in the console
cheers
Luigi Pirelli
Hi Tom,
After some trying, I got the following error:
https://dl.dropboxusercontent.com/u/42637169/Screenshot%202016-03-09%2021.20.50.png
Best wishes,
Anita
On Tue, Mar 8, 2016 at 11:22 PM, Tom Chadwin
wrote:
> Thanks for the screencast. After you've opened the dev
Thanks for the screencast. After you've opened the dev tools with F12, can
you click the Console tab? If there are any JS errors, that's where they'll
be reported.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5255229.html
Sent from
Hi Tom,
Interestingly enough, the new OL3 export seems to work but the Leaflet map
does not show anything and I also cannot locate errors. I recorded you a
screencast which shows what I'm doing: http://youtu.be/xTQ5NoM1_5o?hd=1
Best wishes,
Anita
On Mon, Mar 7, 2016 at 10:44 AM, Tom Chadwin
2.5d is now supported in OpenLayers 3 export (thanks to Jan, the creator of
OSMBuildings). Try it out, and do report issues.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/2-5d-webmaps-with-qgis2web-tp5254480p5254804.html
Sent from the Quantum GIS - User mailing list
Thanks for the files. It works for me:
https://www.dropbox.com/s/jz8jbdhx0ny67j6/Screenshot%202016-03-07%2009.48.04.png?dl=0
Were you able to get to the browser console to see what errors might be
there?
Tom
--
View this message in context:
On Sun, Mar 6, 2016 at 12:04 PM, Tom Chadwin
wrote:
> Hi Anita
>
> It's still experimental, and there's no documentation yet, so we can try to
> see what might be going wrong. In the first instance:
>
> - It only works with layers which have the 2.5d renderer explicitly
Hi Anita
It's still experimental, and there's no documentation yet, so we can try to
see what might be going wrong. In the first instance:
- It only works with layers which have the 2.5d renderer explicitly
selected. In other words, if you use that renderer, but then convert to
another to create
On Fri, Mar 4, 2016 at 8:24 PM, Tom Chadwin wrote:
> Those of you who are using 2.14's splendid new 2.5d renderer can now try
> exporting as a webmap. The plugin qgis2web 1.1.0 (experimental) can now
> export 2.5d layers to a Leaflet webmap (Openlayers 3 is not yet
Those of you who are using 2.14's splendid new 2.5d renderer can now try
exporting as a webmap. The plugin qgis2web 1.1.0 (experimental) can now
export 2.5d layers to a Leaflet webmap (Openlayers 3 is not yet supported).
Do try it out, and report any issues you have at
27 matches
Mail list logo