Latest Contributions by ShengdiZhang

When adding data via Arcade, the expression needs to return a FeatureSet rather than a single value. Also, since acreage is calculated for each record in the watershed, that calculation should be placed inside the first loop. However, this approach would require a nested loop. Even with filters applied to both the watershed and states layers, this still results in roughly 5,000 geometry calculations. This can make the initial load of the data very slow, and if network conditions are poor, the request may time out. I recommend publishing a new dataset with an additional field for the acreage values. That said, if you’d like to try the Arcade method, here’s a sample script for reference: var p = Portal("https://arcgis.com"); var states = FeatureSetByPortalItem(p, "774019f31f8549c39b5c72f149bbe74e", 0); var watershed = FeatureSetByPortalItem(p, "42f868d269784624b0a2df9757c34abb", 0); // Filter states and watershed to New England and New York states = Filter(states, "STATE_ABBR IN ('ME', 'NH', 'VT', 'MA', 'RI', 'CT', 'NY')") watershed = Filter(watershed, "states IN ('ME', 'NH', 'VT', 'MA', 'RI', 'CT', 'NY')"); var features = []; for (var ws in watershed) { var intersectArea = 0; for (var st in states) { intersectArea += AreaGeodetic(Intersection(st, ws), "acres"); } var acres = Round(intersectArea,2); Push(features, { attributes: { HUC10: ws.huc10, Acre: acres, } }); } // Define schema for output FeatureSet (no geometry, only attributes) var schema = { fields: [{ name: "HUC10", alias: "HUC10", type: "esriFieldTypeString" }, { name: "Acre", alias: "Acre", type: "esriFieldTypeDouble" }], geometryType: "", features: features }; return FeatureSet(schema); You can try to improve performance by only intersecting each watershed record with the matching state polygon. Thanks, Shengdi ... View more

Hi @dsinha , I just tested the app and everything is working fine on our end, as well as for others on the team. I noticed in your screenshot that the request is timing out. Since it’s working normally for others, it’s likely something specific to your environment — possibly a firewall, proxy, or security setting that's blocking the request. Other network activity might still work fine, so issues like this can be easy to overlook. If you have any security software or custom network configurations, it’s worth checking if they might be affecting this particular request. You could also try from a different network or device to help narrow it down. ... View more