|
POST
|
@PeteVittthat sounds like a configuration issue. See this doc on Working with Assets: https://developers.arcgis.com/javascript/latest/es-modules/#working-with-assets. You can also compare your code against our Angular example: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli.
... View more
10-20-2021
04:06 PM
|
0
|
2
|
4740
|
|
POST
|
Hi @LukeCalladine this sounds like a configuration issue with your module bundler. Do you have a github repo with a simple app that reproduces the issue? Or you can try to reproduce it with one of our sample apps: https://github.com/Esri/jsapi-resources/tree/master/esm-samples. Maybe comparing against our samples will provide some hints.
... View more
10-20-2021
07:44 AM
|
2
|
0
|
3249
|
|
POST
|
HI@arahman_mdmajid my recommendation is build a simple, vanilla JS app that reproduces the issue and then call tech support. If nothing changed in the web app, then this most likely is not a problem caused by the ArcGIS JS API.
... View more
10-15-2021
07:21 AM
|
1
|
0
|
4191
|
|
POST
|
@RaviKumarEkkuluriif you are using a FeatureLayer for clustering, then take a look at the code snippet example in the source property: https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#source. Also take a look at the API doc for point Geometry: https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html. One caveat with Angular and TypeScript is you have to explicitly declare all ArcGIS JS API classes because of a well-known limitation in TypeScript. You'll have to convert your JSON to an array of Graphics, and then add those Graphics to FeatureLayer.source. Here's an example of how it will work in the API: import FeatureLayer from '@arcgis/core/layers/FeatureLayer';
import Graphic from "@arcgis/core/Graphic";
import Point from "@arcgis/core/geometry/Point";
let point = new Point(
{
latitude: 100,
longitude: 30
});
let tempGraphic = new Graphic({
geometry: point,
attributes: {
ObjectID: 1,
DepArpt: "KATL",
MsgTime: Date.now(),
FltId: "UAL1"
}
});
let layer = new FeatureLayer({
source: [tempGraphic],
objectIdField: "ObjectID"
});
... View more
10-06-2021
08:50 AM
|
0
|
1
|
1503
|
|
POST
|
@ekkuluriravithere is an SDK Guide Topic covering cluster here: https://developers.arcgis.com/javascript/latest/sample-code/featurereduction-cluster/. My recommendation is get the functionality working in vanilla JS first and then migrate it to Angular. Also, here is our Angular CLI example: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli
... View more
10-04-2021
02:24 PM
|
0
|
3
|
1527
|
|
POST
|
HI @Alexandre-Notos, the API functionality is exactly the same and for the TypeScript code you'll need to swap out AMD module paths with ES modules paths and turn the commonjs require statements into import statements.
... View more
09-23-2021
10:02 AM
|
0
|
1
|
1559
|
|
POST
|
There are known issues with Angular CLI 12.2.x+, they made significant changes to how they do optimization. You'll need to stay at versions 12.0.0 - 12.1.x. So far 13.0.0-next fixes the bug. Reference: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli#known-issues
... View more
09-23-2021
07:17 AM
|
2
|
0
|
1656
|
|
POST
|
@ironmaskitocan you clarify if you are using AMD or ESM? One likely culprit is downleveling of async/await but we don't do that in our ESM build. Also, just to clarify: are you using the Spring/Java Enterprise framework? Just want to make sure we aren't talking about some other Spring. We are trying to figure out why there are babel-like asyncToGenerator calls in the Spring screenshot.
... View more
09-22-2021
09:26 AM
|
0
|
2
|
2247
|
|
POST
|
Hi@ironmaskito since the app works without Spring, it's reasonable to believe that Spring is causing the problem and not the ArcGIS JS API. I was also able to verify the NOAA WMS layer works okay in a vanilla JS app without a CORS browser extension or a proxy. My recommended next step in these situations is for you to compare HTTP headers and payload (attributes + data) between the app that's working and app that is not working. I'm not aware of any other definitive way to figure out how the HTTP requests/response is being affected. As an example, we've seen similar cases where the wrapper framework was triggering pre-flight, and that would cause the HTTP requests to fail.
... View more
09-21-2021
12:52 PM
|
0
|
4
|
2266
|
|
POST
|
Hi Chris, interesting indeed. The only other thing I can think of would be looking into your babel config. Here's what I have https://github.com/andygup/angular-jsapi-jest/blob/main/babel.config.js. Maybe double check what's correct for React.
... View more
09-21-2021
08:15 AM
|
0
|
0
|
5953
|
|
POST
|
I'm guessing you'll need to add a regex check to this line for @esri, following a pattern similar to what I did for @arcgis: https://github.com/andygup/angular-jsapi-jest/blob/main/jest.config.js#L4.
... View more
09-15-2021
11:53 AM
|
0
|
0
|
6014
|
|
POST
|
Hi @craragon77 okay, it's failing on calcite-components, did you add those recently? Those are not part of @arcgis/core. My best guess is you'll need to ignore those as well.
... View more
09-03-2021
07:38 AM
|
0
|
0
|
6060
|
|
POST
|
Okay, that's kind of what I figured, thanks for clarifying. It is odd that there are no 404, or even 504, errors when the app tries to retrieve the assets. One likely possibility is your assetsPath setting, the example above isn't what I would expect to see. Have you tried something like this: esriConfig.assetsPath = "./assets"; If that doesn't work, send us a snippet of how you are copying the assets, such as your npm script, etc.
... View more
09-03-2021
07:31 AM
|
0
|
1
|
2897
|
|
POST
|
Hi Kevin, I'm not sure I understand, we didn't have ES modules (@arcgis/core) at 4.17. Is there a reason why you want to host the assets locally? They'll automatically pull from CDN, here's some additional info: https://developers.arcgis.com/javascript/latest/es-modules/#working-with-assets
... View more
09-02-2021
08:36 AM
|
0
|
1
|
2952
|
|
POST
|
Hi @MichaelOakeson the widget actually uses the browser's geolocation API to get the current position. If there's an accuracy issue it is most likely related to the device and the browser implementation of the geolocation API, accuracy can also be affected by your cellular carrier, your WiFi settings and bluetooth settings. If you are testing and seeing a difference in location between the geolocation API and the widget's reported location then please open a support ticket so we can get a thorough evaluation of the issue.
... View more
09-01-2021
11:20 AM
|
0
|
8
|
3283
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 08-01-2025 06:20 AM | |
| 1 | 05-27-2025 12:39 PM | |
| 1 | 04-23-2025 06:56 AM | |
| 1 | 04-23-2025 07:09 AM | |
| 1 | 04-08-2025 09:05 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-05-2025
07:24 AM
|