Latest Contributions by LefterisKoumis

I have an update @Sage_Wall and @LaurenBoyd. I used the suggested script and I realized that sometimes the reactiveUtils.watch is not triggered and sometimes it does. I don't what are reasons behind it. So, I modified to use the arcgisPropertyChange property. so instead of reactiveUtils.watch( () => arcgisFeatures.features, () => { checkIfFeaturesEmpty() }) I use this arcgisFeatures.addEventListener("arcgisPropertyChange", (event) => { if (arcgisFeatures.features.length>0) { checkIfFeaturesEmpty(); }

Thank you so much @Sage_Wall and @LaurenBoyd . It makes sense since the fetchFeatures makes calls to the server and we have to wait until it retrieves the feature info. I think this is a good example to add to the documentation since I noticed that there are not many examples of using mapimagelayers with the web components.

@Sage_Wall Are you suggesting to set the fetchFeatures to false and use the identify to collect the features from an mapimagelayer? If that's the case what is the use of the fetchFeatures? await arcgisFeatures.open({ location: mapPoint, features: [graphics] fetchFeatures: false }) For featurelayers we can use this and we don't need fetchFeatures. arcgisFeatures.open({ location: mapPoint, features: [graphics] });

I use this script to display the popup in the arcgis-features. I need to determine if the arcgis-features after it runs if it is empty or found features. If i click on a featurelayer , then the console states that the component is not empty. However, if i click on a mapimagelayer it states that the component is empty even though there is a feature inside the arcgis-features. Why? const hitTestResult = await arcgisMap.view.hitTest(screenPoint); const mapPoint = arcgisMap.view.toMap(screenPoint); await arcgisFeatures.open({ location: mapPoint, features: results.map(r => r.graphic), // Include any client-side features found fetchFeatures: true }).then((response) => { checkIfFeaturesEmpty() }) function checkIfFeaturesEmpty() { if (arcgisFeatures && arcgisFeatures.features) { if (arcgisFeatures.features.length === 0) { console.log('The <arcgis-features> component is empty.'); return true; } else { console.log('The <arcgis-features> component is not empty and contains ' + arcgisFeatures.features.length + ' features.'); return false; } } else { console.log('The <arcgis-features> element or its features property is not available yet.'); return null; } }

@Sage_Wall If you have a mapimagelayer, then it will still show "No feature hit" in the console. hittest works for featurelayers. How can you modify the script to show hit featureLayer/no feature hit if you are using a feature layer and a mapimagelayer.

Yes, thank you—I’m aware of that. My question, however, is about changing the “No layer” text. Since the application may have multiple layers added dynamically by the user, I’d prefer the message to prompt the user to click the layer stack icon and select a layer in order to populate the table.

When the layer-url property is not set at design time, <arcgis-feature-table> shows the layer list icon with the message “No layer”, even if users add layers later during runtime. Is there a way to replace this message with something like “Click the icon to display tables for available layers”? As it stands, users are not clearly informed that clicking the icon reveals the list of feature tables. @Sage_Wall @ReneRubalcava

In the past, I stayed away from building custom widgets in Experience Builder because layer selection had to be done at design time. I was recently informed that widgets can now dynamically work with any layers currently on the map. Since it’s been a while, I need to refresh my React skills—specifically, which React 19 component concepts should I focus on?

Thank you. I wasn’t aware of this, as it has been a while since I last reviewed ExB. It would be beneficial for application developers—especially those who are not familiar with React—to have a design-time option that allows layers to be added to the map at runtime.

One reason I was hesitant to adopt Experience Builder was its limited support for custom widgets that can work dynamically with whatever layers are currently on the map. The last time I evaluated it, a widget had to be configured at design time with specific layers, meaning you needed to know in advance which layers it would interact with. In the applications I work on, users can load any layers into the map at runtime and then use a custom widget to operate on some or all of those layers. So my question is: is this now possible in Experience Builder? I just use this to detect the layers during runtime arcgisMap.view.map.layers.map(async function (lyr) {

‎11-19-2025

I am using the example as posted here to calculate the geodetic length and area of a location. Wanted to use imperial units (ft and miles). So, I changed const geodesicLength = geodeticLengthOperator.execute(line, { units: "kilometers" }); const planarLength = lengthOperator.execute(line, { units: "kilometers" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { units: "square-kilometers" }); const planarArea = areaOperator.execute(polygon, { units: "square-kilometers" }); to: const geodesicLength = geodeticLengthOperator.execute(line, { units: "miles" }); const planarLength = lengthOperator.execute(line, { units: "feet" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { units: "square-miles" }); const planarArea = areaOperator.execute(polygon, { units: "square-feet" }); Then I noticed that the geodetic measurements were way off incorrect Then I changed the "units" to "unit" for geodetic measurements const geodesicLength = geodeticLengthOperator.execute(line, { unit: "miles" }); const planarLength = lengthOperator.execute(line, { units: "feet" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { unit: "square-miles" }); const planarArea = areaOperator.execute(polygon, { units: "square-feet" }); and now I get correct results!! I don't see anywhere in the documentation stating to use unit instead of units for geodetic measurements.

‎11-04-2025

I use the search component( arcgis js api 4.33), but the chrome dev tools flags it as depreciated! <arcgis-map basemap="streets-navigation-vector" id="my-map" center="-120.45, 37.183" zoom="6" popup-disabled> <arcgis-search position="top-left"></arcgis-search> <arcgis-zoom position="top-left"></arcgis-zoom> <arcgis-compass auto-destroy-disabled position="top-left"></arcgis-compass> <arcgis-scale-bar position="bottom-left" bar-style="line" unit="imperial"></arcgis-scale-bar> </arcgis-map> Chrome Dev Tools

‎10-29-2025

@ReneRubalcava It isn’t immediately clear to users that they need to click the stacked layers icon to select which layer to display in the table. As a possible enhancement—and to avoid showing an empty table—you could make it so that clicking the table icon (in the action bar) automatically opens the table with the first visible layer from the map. For instance, developers could collect all currently displayed layers into an array, and when the table icon is clicked, open the table using layer[0] or whichever layer the developer sets using a table-layer property.

‎10-23-2025

The feature table is not slotted into the map. I realized that the issue was a css setting for the arcgis-features where I had position:absolute. All good now. Thank you.

‎10-23-2025

if both arcgis-feature-table and arcgis-features web components are open, they will be overlapped. One way to address it is by CSS, to monitor if arcgis-features is open then you adjust the width of the table. I am wondering if there is a another way to do it, or should it be an enhancement request? @ReneRubalcava

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by LefterisKoumis

Re: arcgis-features and mapimagelayer

Re: arcgis-features and mapimagelayer

Re: arcgis-features and mapimagelayer

arcgis-features and mapimagelayer

Re: Using Components with hitTest: 'click' on Calcite Buttons registers as hitTest in underlying Map

Re: Feature Table web component

Feature Table web component

Learning Reactjs 19

Re: custom widget with layers on map

custom widget with layers on map

incorrect geodeticLengthOperator geodeticArea Operator measurements in imperial units.

arcgis-search mistaken as widget?

Re: arcgis-feature-table .layers Property

Re: co-existense of table and features web components.

co-existense of table and features web components.

Re: arcgis-features and mapimagelayer

Feature Table web component

Re: custom widget with layers on map

Re: access scale-bar value

AMD modules will go away?

GIS Jobs

Experience Builder Custom Widgets

Web AppBuilder Custom Widgets