Latest Contributions by AndrewMurdoch1

Brilliant, that's what I figured was going on, that makes sense 🙂 — Thanks for the explanation. ... View more

Hey I've managed to get a Stream Layer stood up with a web socket that is handling 400 000 features at ~1 GB of memory.  What I don't understand, when I made 200 000 features using a “normal” Feature Layer it uses ~4 GB of memory, but fundamentally, what's really different?   I wrote the web socket server using GO, it's very basic, but once the features are streamed, shouldn't the memory even out?  I can't grasp how the Stream Layer is using 1/4 of the memory for twice the amount. Since I'm going to be asked why the memory is so drastically different, is it possible to get a clear explaination as to why? ... View more

Awesome, I'll take a look, thanks for the suggestion! ... View more

Good Day Thanks for the reply, I ended up calling goTo() to "zoom out", which allows the data to render properly.  Thanks ... View more

Good Afternoon Thanks for the suggestion, but I don't think that works with a dynamic renderer.  I found a way to get the view to zoom to the layer extent, but now when zooming in everything goes too far the other way and disappears. Thanks ... View more

Switching to using a in (1,2,3,4.....) Doesn't seem to work but does bypass the previous restriction.  The problem with using “in” is that the output doesn't seem to be SQL like.  Assuming “a in (1... 45 000)” returns 45 000 features, applying more filters and queries on top, makes it seem each of those 45 000 features has to apply the filter again, which cause performance to drop through the floor. Cheers ... View more

I found a workaround, if you ever run into this, but it requires a username / password. const param = { username: this.username, password: this.password } // @ts-ignore esriId.generateToken(serverInfo, param).then((tokenRes: any) => { esriId.registerToken({server: serverURL, token: tokenRes.token}); esriId.checkAppAccess(serverURL, appId).then((getCredRes) => { r(getCredRes); }).catch((error) => { console.log('Error - Checking App Access'); console.log(error); j(error); }) r(serverURL); }).catch((error) => { console.log('Error - Generating Token'); console.log(error); j(error); })   Then you'll be able to use the connection without getting stopped :). ... View more

Good Day I've had a lot of problems with the memory and Angular, so this is how we keep it in check: 1. Use a Store to keep the view / map, and use the RenderFactory to attach the view / map into and remove it from a container. 2. Make sure you're removing, freeing or deleting as many resources as possible, for instance here is some code from our ngOnDestroy() public ngOnDestroy(): void { this.esriSvc.removeMapViewContainer(this.mapViewEl); try { this._Attribution?.destroy(); this._Attribution = null; } catch (error) { console.log(error); } try { this._clickEvent?.remove(); this._clickEvent = null; this._BasemapGalleryWatcher?.remove(); this._BasemapGalleryWatcher = null } catch (error) { console.log(error); } try { this._sketchWidget?.destroy(); this._sketchWidget = null; this.sketchLayer?.destroy(); this.sketchLayer = null; } catch (error) { console.log(error); } try { this._view.map.layers.forEach((layer) => { layer.clear() layer.destroy() }) this._view.map.layers = null; } catch (error) { console.log(error); } try { this._view.ui.empty(); this._view.popup = null; } catch (error) { console.log(error); } try { this._map.removeAll(); } catch (error) { console.log(error); } try { this._widgets.forEach((widget) => { if (widget) { try { widget = null; } catch (error) { console.log(error); } } }) this._widgets = []; } catch (error) { console.log(error); } // // NOTE: This function resets every variable we allocate // this.destroyStuff(); }   3. Litsten to Andy, he's awesome and has helped me in the past. Using the method I described, I've been able to cycle between 10k maps with essentially 0 memory increase.  You can also look into using a global render setting, if that's applicable, and try to never destroy the map or remove and add it if you don't have to.  I've found in a lot of cases it's better to just hide it, then detach and add it back.  Although I know that can't always be avoided. ... View more