Latest Contributions by AndrewMurdoch1

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

Has anyone seen this kind of behaviour? ... View more

After changing the timeout to 0, I'm no longer getting the cancelled request, but I'm getting lots of 500 / 504 errors. The 200 at the top had a 500 response inside it: I ran the same test several more times, and was able to get a response, and the only different I can see is that the successful one took 1.9 minutes, and all the failures took 1.0 minutes or 2.0+ minutes. This is the capture of the other responses, the top 200 was actually successful, the second was had a 500 response code it:   Thanks   ... View more

Thanks!  I'll try that 🙂 ... View more

I know this an old post, but I got it!   1. Look at https://github.com/epaitz/jsapi-angular-ngrx-ds2021 2. I took that code and made:  https://github.com/docmur/angular-core-esri (Look at master-a12) 3. When you allocate a map, store it's "settings" in a Store (map, view, feature layers, etc…) 4. When you recall the map, don't allocate a new feature layer, just remove and add the features to the existing layer(s) if you need to change the layer or features. 5.  That code is using a single map and view, then changing the features in the layer, but the same idea works for multiple maps. 6.  Don't try and destroy the map or view, or feature layer, you won't reclaim memory doing that. For some reason the featureLayer.destroy(), and map.removeAll() / map.layers.removeAll(), won't free the memory being held by the feature layer, which is why it continues to climb.  I've already rolled this code into our production application, and it works wonderfully!  We allocate 2 maps in total, and then just hold them in the Store, being recalled when we need them, then I use the feature layer to apply edits to do the main work. The multiple map variation has been able to run for 20+ hours with no issue and using ~35MB of memory from the Dev Console. This is the solution you're probably looking for 🙂 Cheers ... View more