Latest Contributions by AndrewMurdoch1

I changed the data so we only use 1 set of ~15 800 features and use the attributes to show the time values.  Using this method I have ~70 attributes, but I can use "valueExpressions" to change the render setting, giving me almost instance response and feed back because I don't have to regrab the data, I only have to apply a new render setting. I've been extended this idea out, over the last several days, so I have a Unique Value Renderer with ~170+ settings in it, and then change the fields / "valueExpression" to change the view, which has been game changer. If anyone else is running into this problem, try to flatten the data out and use attributes instead of duplicating features if you can get away with it 🙂 Thanks for the suggestion, I was actually logging to update my progress, but you said exactly what I did, and it worked like a charm. Cheers ... View more

Thanks for the suggestion but it's still a choppy mess, no matter how I breakdown the queries.  Using pagination the year change code is now: if (changes.year.currentValue) { const useDefinitionExpression = false; if (useDefinitionExpression) { this._view.map.layers.forEach((layer) => { if (layer.type === 'feature') { layer.definitionExpression = 'Year = ' + this._year; } }) } else { const featureBreak = 10; this._view.when(() => { this._view.map.layers.forEach((layer) => { if (layer.type === 'feature') { this.queryFeatureCount(layer).then((featureCount: number) => { const runQueryCode = true; if (runQueryCode) { const featureGroup = featureCount / featureBreak; const featureSteps = []; for (let i = 0; i <= featureCount; i += featureGroup) { featureSteps.push({ start: Number(i.toFixed(0)), end: Number((i + featureGroup - 1).toFixed(0)) }) } const runFeatureStepLoop = true; if (runFeatureStepLoop) { this._map.removeAll(); featureSteps.forEach((step) => { const query = { start: step.start, num: step.end, where: 'Year = ' + this._year, outFields: ["*"], returnGeometry: true, }; console.log('Query'); console.log(query); layer.queryFeatures(query).then((queryResult) => { try { console.log('Adding New Features'); this._map.addMany(queryResult?.features); } catch (error) { console.log(error); } }).catch((queryError) => { console.log('Error Querying Features'); console.log(queryError); }) }) // END_FOREACH: Feature Steps } } }); } }) }) } }   Using "featureBreak" I can control how many queries are generated, but no matter what I set that to I run into the same problem.  Right now that problem is a lot of shuddering and crashing. Apart from using this method, are there any considered best practices?  I'm thinking we might have to use 1 layer / year to make this effective, because nothing I try seems to work. Thanks 😀 ... View more

Thanks!  I'm going to try and build a version of this to load the data in parts, that might solve my issue. I'll let you know if it works 🙂 ... View more

That accomplished exactly what I'm looking for 🙂 - Thanks! ... View more

If you give me a few days I'll adapt my test repo to replicate the issue.  We're using Angular 12, and the test repo is also using Angular 12.  Every class break has a label uniqueValueInfo.push({ value: renderKey, label: renderKey, symbol: { type: renderType, color: mapData.attributes.colour, size: 12, width: 3, outline: { width: 4, color: mapData.attributes.colour, } } })   Render Key can never be null.  I'll see what I can get you mid next week. Thanks for your help 🙂 ... View more

Good Day I ran the test again, this time setting arcgis/core to 'next' instead of 4.21.2 in package.json, I still have the same problem: 4.21.2   Next: I also confirmed that the title on each Feature Layer is set to ''. Cheers ... View more

Yes, I'll run the test in a bit. ... View more

Good Day @Noah-Sager  - Thanks for the reply, the PictureMarker is resolved! The second issue is that Roads is showing up without a line in front of it.  The screen cap has Roads, and then under that (green line) Roads, which is correctly.  I don't know why 'Roads' with no green line shows up.  I'm assuming that's due to a title being generated for the Feature Layer, because if I generate multiple Feature Layers I can cause the same behaviour, for the Points or Polygon Layer. In the above example I have title: '' in the FeatureLayer code, which I thought should set the title to nothing. Hopefully that makes sense. Cheers ... View more