This content has been marked as final. Show 3 replies
Will try to reproduce this and respond. The coordinate transformation may be the issue.
This seems to be a bug. When a transformation (to 3785, 3857) is involved it seems to query the whole table to build up the cache. Will investigate further to see if caching=none makes a difference.
Because we are allowing the user to edit the data we always set the cache to none. So, in theory, you should get the same result.