However, the features included in this dataset are not points anymore. They are polygons (can also see from the screenshot).
Even one polygon's shape data could be huge (it could cover an area larger than a state)
Our current approach (by limiting no. of features returned) to prevent data to big will not work as even one feature could be too big (without polygon simplification).
Possbile Solution
ArcGIS's own viewer can work because it requests ArcGIS API to return tile rather than JSON (which works similarly to tiles in a tiled map service layer).
One example request (before proper query parameter encoding for ease of reading) could be:
https://hub.arcgis.com/ is getting more popular. Its SaaS model means all their clients running on the latest version.
More and more datasets previously had to serve as map services might be served as ArcGIS feature services, which means we would encounter this issue more often.
ArcGIS feature server dataset causes browser freeze & crash
Related to: #3661
This ArcGIS feature server dataset: https://services1.arcgis.com/gtRkYQyUQLMTM1uS/ArcGIS/rest/services/_Biologically_Important_Areas_of_Regionally_Significant_Marine_Species/FeatureServer/0
Can't be rendered by the latest TerriaJs correctly and will freeze/crash the browser.
However, ArcGIS's own viewer can visualise it well:
https://www.arcgis.com/apps/mapviewer/index.html?url=https://services1.arcgis.com/gtRkYQyUQLMTM1uS/ArcGIS/rest/services/_Biologically_Important_Areas_of_Regionally_Significant_Marine_Species/FeatureServer/0&source=sd
Why?
Terriajs now access the traditional JSON API and request JSON output. e.g. :
https://services1.arcgis.com/gtRkYQyUQLMTM1uS/arcgis/rest/services/_Biologically_Import[…]tFields=*&outSR=4326&resultRecordCount=1000&resultOffset=0
However, the features included in this dataset are not points anymore. They are polygons (can also see from the screenshot). Even one polygon's shape data could be huge (it could cover an area larger than a state)
Our current approach (by limiting no. of features returned) to prevent data to big will not work as even one feature could be too big (without polygon simplification).
Possbile Solution
ArcGIS's own viewer can work because it requests ArcGIS API to return tile rather than JSON (which works similarly to tiles in a tiled map service layer).
One example request (before proper query parameter encoding for ease of reading) could be:
We have ticket #3661 detailing this approach.
Why we should re-look at implementing #3661
https://hub.arcgis.com/ is getting more popular. Its SaaS model means all their clients running on the latest version.
More and more datasets previously had to serve as map services might be served as ArcGIS feature services, which means we would encounter this issue more often.