Latest Contributions by ReneRubalcava

Ah, sorry. That won't work in 4.13. That was introduced at 4.23 I think. Before that, we didn't have that option in the IdentifyParameters like in 3x. In recent 4x version, the sublayers need to come from a MapImageLayer as they need a layer source. https://codepen.io/odoe/pen/qBYbOyG?editors=1000 ... View more

The JSAPI isn't open-source, so we don't provide the unminified code anywhere. We only have custom layer extensibility for Tiled layers, not FeatureLayers. We also have request interceptors, where you can modify the response before the layers use it, but no guarantee we don't use the service defined fields for other parts of the drawing and query stuff, you might be able to do some stuff here, but you're just adding to query time here too by pulling in new data requests. https://developers.arcgis.com/javascript/latest/api-reference/esri-config.html#RequestInterceptor If you have Enterprise portal, you can do this via a SOE. Doing this on the client is probably going to require a custom worker one way or another ... View more

It's not a module you can import, but is available in our namespace if you need to type something for it. let handle: __esri.WatchHandle; You get the namespace typings automatically when you install @arcgis/core. ... View more

The snippet is incorrect and will be updated in next release.   require([ "esri/rest/geometryService", "esri/rest/support/ProjectParameters" ], function(geometryService, ProjectParameters) { const params = new ProjectParameters({ geometries: [point], outSpatialReference: outSpatialReference, transformation: transformation }); geometryService.project(url, params).then( ... ); });   This can also be written as: import { project } from "@arcgis/core/rest/geometryService"; import ProjectParameters from "@arcgis/core/rest/support/ProjectParameters"; const params = new ProjectParameters({ geometries: [point], outSpatialReference: outSpatialReference, transformation: transformation }); project(url, params).then( ... ); The snippet assumes you are using ESM, which should only import the project method.   ... View more

If you want to join external data to data from a FeatureLayer, it's going to require a few steps. Create a new client-side FeatureLayer with the fields from source FL and external data, and matching geometry to source FeatureLayer Query all the features from your source FeatureLayer. This could be troublesome if you have a large amount of data, so you might need to paginate your requests. Iterate over your features and add new attributes to your features based on a common field. Use FeatureLayer applyEdits to add these features to your client-side FeatureLayer. I wrote a blog post very similar to this workflow, but doing a spatial join based on geometry. In your case it would be based on a common field and matching value. https://odoe.net/blog/spatial-joins Also, if you find that the join is slow due to the amount of data you have and it blocks interaction with your page, you could consider using a custom worker. We have a sample, using the spatial join with a worker, on github. https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-custom-workers ... View more

hitTest is right, you just need to access the results slightly differently as of 4.24. The documentation explains the 4.24 change and has some snippets. https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#hitTest view.on("click", async (e) => { const response = await view.hitTest(e); const result = response.results[0]; if (result.type === "graphic") { const graphic = result.graphic; } else if (result.type === "media") { const element = result.element; } else if (result.type === "route") { const networkFeature = result.networkFeature; } });   ... View more