Latest Contributions by mgeorge

Hi @Guy_srb! Are you envisioning say having an administrative boundaries layer, and then a point service with data, and performing the enrichment on the client? It's definitely something we talked about internally in the past, but it's not on our roadmap yet.  ... View more

@DamonDamon  Also would need to know the CPU model & discrete GPU model (if there is one). Safari, Chrome, and Firefox all have their own APIs that go from WebGL -> GPU driver instructions, so it's often the case that you'll see different behavior or different platforms due to either (1) bugs in the browser or (2) browser-specific workarounds for bugs in graphics drivers.  MapViewer Classic does not always use WebGL, and when it does, it's a very early version of the 4x engine. So I would also expect to see differences there when it comes to WebGL-related browser/driver-specific issues.  ... View more

Hi Damon, can you post your CPU/GPU & GPU driver version? You can go to window -> run -> "dxdiag" and then look under the system and display tabs.  There might not be much we can do here. We've found certain old intel iGPUs to have rendering bugs, that we test for when the map loads -- that's what that error is saying. When we encounter these bugs, we apply a workaround so that things can still render, but oftentimes performance is very bad -- not because of the workaround, but because the browser itself is also applying numerous workarounds for the bad drivers that do severely degrade performance. You can see what workarounds browsers are applying in chrome://gpu.  Also note that some vendors like Dell don't always update the intel drivers on laptops that might still technically be in the intel support window, but outside of Dell's own warranty. Because they require their intel drivers to be signed, there's no way to update to the fixed version of the drivers.   But for a machine on windows 7 (10+ years old?), unfortunately it's likely out of support by intel and doesn't have the fixes in their more recent driver releases.    ... View more

@RyanSutcliffe, just talked to the dev for the npm build. It should work the same way. You just need to include <script> window.dojoConfig = {   has: { "featurelayer-snapshot-enabled": 0 } } </script> before the API gets loaded.   ... View more

@RyanSutcliffe sorry for the slow response. It needs to be set on the main config, not the workers config. I'm not too familiar with how things are wired up for the npm build, let me see if I can find out ... View more

Sorry @RyanSutcliffe for the late rely. esriConfig should work the same as dojoConfig, they're aliases for one another. I would probably get in contact with support, they should be able to help setup a repro.  ... View more

Hi @SCS_ANST.  Thanks for the report! Yes, we're aware that some configurations have very slow count queries, and there's some alternative count querying APIs (for approx count) that we are looking at potentially exploring for 4.25.  Does your definitionExpression for the layer in question include that 1=1? I don't think the API should be generating that unless there is no definitionExpression set on the layer. Talking to the server folks, it sounds like that can degrade performance for dbs against mapserver.  ... View more

Hi @MattReames2, do you have a codepen or a repro that we can use to take a look? If not you can work with support and they can help to create something for us to take a look at.  ... View more

FYI, brought this up with the team ... View more

@james-rae the api does consider the the symbol size (including size impacting stuff like visual variables that are applied shader side), and should be precise. It just uses a large hittest radius to make it "easier to click," esp. for mobile where it's hard for users to be exactly click on something. We're thinking though that maybe we need to vary this for mobile / desktop, using a smaller radius on the latter.  ... View more

@LucasScharenbroich for the flag, just use esriConfig instead of dojoConfig.  ... View more

FYI @RyanSutcliffe, we talked with the server team, and apparently this happens on some backends where the count can unexpectedly take a very long time to return. They've added a different API we can use to get the approximate count, and we're evaluating whether we can move to that for 4.24 (not this next release, but the following one).  ... View more

I can check whether or not this is the case if I can see what's going on, but upgrading your server to something more recent might also help here. I know there were some PBF issues for earlier version of server... that's the only major difference in terms of querying for server that I can think of ATM.  ... View more

Another thing that you can also try is disabling PBF mode: Disable PBF (codepen.io) ... View more