Yes, I see that problem too.
I think it's because we're not applying buffering to the MVT tile encoder,
so client applications are falsely led to believe that they are legit
separate features and not a single feature that crosses multiple tile
boundaries.
- Jackie
--
Sent from:
Hi Jackie,
at least I can now see features on the map. But I think there are two more
issues:
1. When rendering the features in the client application (OpenLayers, QGIS)
the borders of the tiles are rendered, too. It's hard to see with the
Sheboygan dataset. But when you decrease the "Min scale"
Hi Jackie,
this works fine now. Thanks a lot.
Gunter
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
Hi Gunter,
Please try this patched MgFoundation.dll
https://download.osgeo.org/mapguide/patches/MG_ticket2832/MgFoundation.7z
Extract and overwrite *all existing copies* of MgFoundation.dll in your MGOS
4.0 Preview 2 installation.
This dll contains this compiled code change:
Hi Gunter,
The issue appears to be that current OpenLayers is expecting extra MVT
metadata that the MVT encoder is not encoding in (namely the default extent
of 4096). This screws up the resulting OL feature coordinate computation
(that is expecting this extent value to be there), rendering all
