Latest Contributions by AndyGup

Hi @RussellMGreen unfortunately we don't currently have a way to export interfaces and other types. You will still need to use the __esri namespace for gaining access to most items that are not classes. We do have an issue open for improving this in the future. ... View more

Hi @GIS_Weasel  we are going to clarify the deprecation wording and sync that up with any SDK documentation pages. The good news is only the custom widget sample, itself, is being deprecated. You can continue to use Vite, you can extend the capabilities of the 4.x esri/widgets/Widget class, and you can continue to use the SDK's viewModels. Note that the React and Vue samples are using Vite, and so are the downloadable ESM-based SDK samples. Our goal is for the SDK to be compatible with all the major frameworks and module bundlers. With regards to migrating custom 3.x content to 4.x, building custom UI within frameworks such as React, Angular or Vue is best done using their respective UI patterns and practices. Of course, you can also continue to use 4.x OOB SDK widgets within the MapView/SceneView. And, you can also incorporate the Calcite Design System: https://developers.arcgis.com/calcite-design-system/.   ... View more

Hi @Lzy, for an overview of our ESM bundle size and performance here's a link: https://github.com/Esri/jsapi-resources/tree/main/esm-samples#bundle-size-and-performance. If you require further assistance, please provide a simple, reproducible sample using github, stackblitz, or codesandbox.  We recommend using our ESM examples as a starting point for building a test sample: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-vue. ... View more

Hi @RazvanVxMt  take a look at this discussion: https://github.com/Esri/jsapi-resources/issues/437#issuecomment-1235628447. It's about React, but the concept for managing the View and just removing the container is the same for Angular or any other framework. If you still need further assistance, you'll need to provide a simple, working github repo, codesandbox or stackblitz example. ... View more

@agauch  the download has been fixed. Give it another try and let us know if there are any more issues. ... View more

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