Hi Raymond
Lova is doing some excellent work on the plugin repository recently.
Maybe he will find the time to look into this?
In any case, I think it would be worth opening an issue with your research
on https://github.com/qgis/QGIS-Django/issues to not forget about it and
have a contextualized d
Diving in the code I found a few suspicious lines.
1. In the Django code, there's no mention of "repository" in this list:
https://github.com/qgis/QGIS-Django/blob/6d03c8428abe9df7634bbf810bbcb63709b11d45/qgis-app/plugins/views.py#L908
2. In the QGIS code, the PluginManager seems to look for
"
Update: actually, instead of completely disabling server side spatial
filtering with geographic SRS, I just found a hack... One can use
ST_SRID() to hack a "random" projected CRS, and then things work
So now the OGR mySQL driver will do things like:
select MBRIntersects(ST_GeomFromText('POLYGO
But, my point: why can QGIS apparently show attributes, while not
showing a geom.. Apparently the features were fully retrieved.
When displaying the attribute table, QGIS doesn't apply a spatial
filter. Whereas when displaying features on the canvas, it does. And as
I found out, something's
On 1/28/24 19:04, Even Rouault wrote:
what I don't understand is how you manage to create with ogr2ogr a table
without explicit SRS with features whose coordinates are not compatible of
geographic coordinates. As mentioned previously, I do get a hard error from
ogr2ogr when trying that. Which
Richard,
what I don't understand is how you manage to create with ogr2ogr a table
without explicit SRS with features whose coordinates are not compatible
of geographic coordinates. As mentioned previously, I do get a hard
error from ogr2ogr when trying that. Which GDAL version do you use?
Th
On 1/23/24 23:21, Even Rouault wrote:
So all in all, no issues on my side...
You were off course right :-)
I found out how to fix the missing crs in mysql and wrote some info (for future
reference) in a comment:
https://github.com/qgis/QGIS/issues/55463#issuecomment-1913602140
One thing I
Ok, lift off :-) See screenie.
Thank Even, I had mixed version qwt headers and libs.
So on Debian Trixie, there seems no libqwt for qt6 available yet?
Had to pull these from experimental:
libqwt-headers_6.2.0-1_amd64.deb
libqwt-qt6-6.2_6.2.0-1_amd64.deb
libqwt-qt6-dev_6.2.0-1_amd64.deb
Then QG