You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that loading custom vector tile data can, in certain circumstances, cause RapiD v2 to give up and fall over. Severe slowdowns, not showing all the data in each layer, etc. are just a couple of the issues we're seeing in internal testing.
Version
2.0.0-beta.0
What browser are you seeing the problem on? What version are you running?
Chrome 109.0.5414.119
Steps to reproduce
Load custom vector tile data using the Map Data (F) menu, click 'edit custom map data' button, paste the vector tile data URL, observe RapiD slow to a crawl / not display everything.
The browser URL at the time you encountered the bug
Container ids for custom data containers had 'undefined' elements
The projection being fed into the custom data viewer didn't have a projection boundary- so only tiles in the upper left of the screen were being loaded on startup.
Ensure that we re-render any custom data features that get updated (say, those getting merged into other features with the same feature class).
Description
It appears that loading custom vector tile data can, in certain circumstances, cause RapiD v2 to give up and fall over. Severe slowdowns, not showing all the data in each layer, etc. are just a couple of the issues we're seeing in internal testing.
Version
2.0.0-beta.0
What browser are you seeing the problem on? What version are you running?
Chrome 109.0.5414.119
Steps to reproduce
Load custom vector tile data using the Map Data (F) menu, click 'edit custom map data' button, paste the vector tile data URL, observe RapiD slow to a crawl / not display everything.
The browser URL at the time you encountered the bug
http://127.0.0.1:8080/#background=Maxar-Premium&datasets=fbRoads,msBuildings&disable_features=boundaries&map=15.00/48.8742/2.3415 but with an internal vector tile dataset.
The text was updated successfully, but these errors were encountered: