Latest Contributions by AndyGup

Hi Robert, there is information on the build bundles here: https://github.com/Esri/jsapi-resources/tree/main/esm-samples#bundle-size-and-performance. ... View more

Hi @MichailMarinakis1 thanks for the questions, and we are glad everything worked like a charm. Correct, as you are discovering there isn't a one-size-fits-all solution to implementing custom applications built with modern JavaScript build tools, templates and frameworks. There are many excellent third-party choices, they all have their area of expertise and they iterate, constantly. Our recommendation is to prototype a variety of approaches and see what works best for you and your organization's unique requirements. Our goal for the JavaScript Maps SDK is to work with the widest number of these. That's what happened with arcgis-js-cli, over time the variety and advancements of modern choices for ESM developers made its' interpretation of project scaffolding obsolete. ... View more

Hi Bob, it's in the queue and we've done some of the groundwork for it. Unfortunately, we don't have an ETA at this time. ... View more

Hi@MajidH  there currently no plans to add official ESM (@arcgis/core) unit testing examples. Can you share a simple github repo, stackblitz or codesandbox? Then anyone on this thread can try to repro with all dependencies, configuration, usage patterns, etc. ... View more

@AriefAbuBakarthis is now fixed and will be available at 4.26. You can test it today by installing the latest 'next' build: npm i @arcgis/core@next   ... View more

I just double checked the code, the enableHighAccuracy property is set to true in the ArcGIS JS SDK by default at 4.25. But YMMV based on the items I mention above. ... View more

> I believe someone did put in a support ticket on this for me at our organization. Hi@ZacharyHart  I haven't seen a support ticket, you might want to double check on your end. We took a close look at the Locate Widget and confirmed it is using the browser's built-in W3C Geolocation API via the getCurrentPosition() method. Because the widget only acts as a pass-thru for the geolocation results, the points you are seeing are exactly what is provided by the browser's own API. The best way to get better geolocation capabilities are to either use the native device operating system APIs or build additional software functionality to help normalize the raw location results. TL;DR; Differences in geolocation could potentially be explained by variations in how the Geolocation API options (maximumAge, timeout, enableHighAccuracy) are configured on the widget via the geolocationOptions property. Generally speaking, the Geolocation API does a decent job for consumer-grade geolocation use cases. However, here are some examples of things that affect accuracy: * GPS variations - not all chips are the same, plus GPS satellite signal strength fluctuates and is affected by your surroundings (hills, mountains, buildings, power lines, trees, storm clouds, car roof, etc) * OS and browser variations in geolocation implementation * browser or device caching of geolocation data * nearby WiFi routers, cellular service trilateration since these signals also fluctuate continuously * Use of a VPN * Combinations of all of the above   ... View more

Hi @litch I'm unable to determine what's going on from the screen shots. Are all three screenshots taken using the iPhone 12 Pro simulator mode? That phone has a native resolution of 2532 x 1170 at 460ppi which can make UI elements look really small when running in simulation mode in a desktop browser. ... View more

Hi @GisNavy the native SDKs are your best approach to offline GIS workflows. Those SDKs have direct access to low-level device APIs to robustly support actions such as storing, sync/re-sync editing with feature services, as well complete support for restarting/reconstituting an app after offline device restarts and many other advanced capabilities. We don't have any plans for this type of functionality in the JavaScript SDK. ... View more

Update - this looks like a regression at 4.25, thanks for reporting. We've opened an issue to fix it. ... View more