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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: HolgerJeromin [Submitted to the original trac issue database at 9.45am, Monday, 18th April 2011]
Clicking on "data" on the website, the page asks the question:
loaded_an_area_with_num_features: "You have loaded an area which contains <num_features> features. In general, some browsers may not cope well with displaying this quantity of data. Generally, browsers work best at displaying less than 100 features at a time..."
This times are IMO over. Even IE8 has no real problem loading 1500 objects (3 year old laptop, even 4400 object do not crash) and all other browsers are even faster with their compiling JavaScript engines.
Please raise this limit.
Thanks
Holger
The text was updated successfully, but these errors were encountered:
Reporter: HolgerJeromin
[Submitted to the original trac issue database at 9.45am, Monday, 18th April 2011]
Clicking on "data" on the website, the page asks the question:
loaded_an_area_with_num_features: "You have loaded an area which contains <num_features> features. In general, some browsers may not cope well with displaying this quantity of data. Generally, browsers work best at displaying less than 100 features at a time..."
This times are IMO over. Even IE8 has no real problem loading 1500 objects (3 year old laptop, even 4400 object do not crash) and all other browsers are even faster with their compiling JavaScript engines.
Please raise this limit.
Thanks
Holger
The text was updated successfully, but these errors were encountered: