Latest Contributions by UndralBatsukh

Undral, we have noticed similar issues with the beta release. Imagery not rendering properly.  Also images being placed in the wrong location: Orthoimagery (bad rendering, ok location): https://maps.vcgi.vermont.gov/pub/View_VT_Imagery_COG_AWS.html  https://vt-opendata-pilot2.s3.us-east-2.amazonaws.com/LIDAR/0_7M/2014/HILSHD/COG/LOSSY/Elevation_HILSHD0p7M2014_EVT1239.tif  Lidar hillshade (ok rendering, bad location): https://maps.vcgi.vermont.gov/pub/View_VT_Hillshade_COG_AWS.html , https://vt-opendata-pilot2.s3.us-east-2.amazonaws.com/IMAGERY/VTORTHO/0_3M/CLRIR/2022/COG/LOSSY/VT_442221_20220505.tif  I also noticed that in the case of imagery its looking for a *.tif.aux.xml and for the hillshade its also looking for *.tif.vat.dbf...which returned a 404 error since we don't have those. Not sure if that is part of the "problem", but obviously those files shouldn't be necessary for the COGs to render properly (which they do in Pro and QGIS). Thanks for your effort to but COG support with the ArcGIS Javascript API. I will be really handy once its ready for prime time! Steve, VCGI ... View more

The COG file must have pyramids built to be displayed.  This is not specific to cog. If you create an enterprise tiled image service without pyramid, you will get same behavior. In any case, you can build pyramids with build pyramids geoprocessing tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/build-pyramids.htm   ... View more

Hi there,  You will likely to get more responses if you post your question on calcite community: https://community.esri.com/t5/calcite-design-system/ct-p/calcite-design-system   Calcite developer page lets you interact with the different aspects of the component on their page. Then you can get the updated the code from the page and use it in your app. For action bar you can use this page: https://developers.arcgis.com/calcite-design-system/components/action-bar/ You can change the word under translations. For example for the collapse you can change the following way:  <script> document.querySelector("calcite-action-bar").messageOverrides = { collapse: "Override message" }; </script>   This works with the latest version. I see that the codepen you provided is using beta version of the calcite. You may want to update your version so that the approach above works. If not you can ask the follow up question on the calcite community.  ... View more

Thanks! Both of these examples worked fine!😀 ... View more

Thanks for this.  The example helped to get me on the right track to figure out how to use the calcite css variables.  I was able to inspect the code in Chrome and figure out what was going on.   I ended up finding out how to use the :hover css selector which let me switch the color of the icon: #infoIcon:hover {         --calcite-ui-foreground-1: #f3f3f3;       } In the end, I stumbled across an example of creating an esri widget button class which worked better and already had similar styling to the other esri widgets out of the box.  Hopefully this helps someone else so I'll post some of my code below. //CSS for placement location #infoSWPapp { display: block; position: absolute; top: 170px; left: 15px; } //Add the button div to the UI in script section/file view.ui.add(["infoSWPapp"], "manual"); //set esri class for the div and use icon from esri icons in body section <div id="infoSWPapp" class="esri-component esri-widget--button esri-widget" role="button"> <span id="infoIconImage" class="esri-icon esri-icon-description"></span> </div> //JS code to open modal window when button is clicked <script> const modal = document.getElementById("example-modal"); const infoButton = document.getElementById("infoSWPapp"); infoButton.addEventListener("click", function() { modal.open = true; }); </script>   ... View more

Hi @UndralBatsukh thanks for your reply, the workaround worked perfectly, it causes the same effect as if I had used the clientside `applyEdits` function. I had tried emitting that event before posting here, but my mistake was not adding all the empty arrays to the event object, as soon as I added them it started working as expected. Thanks again. ... View more

Seems like you have an issue in the WKT text. The WKT is supported when projecting. For instance, there is two pp here: PPROJCS I removed this and was not able to project it. So I have used this WKT: https://spatialreference.org/ref/epsg/nad83-utm-zone-11n/esriwkt/ and projection happens as expected. This codepen shows a proof of concept in 4.26. https://codepen.io/U_B_U/pen/RwevmgB?editors=1000   ... View more

Certainly, and thank you.  Just brainstorming different solutions here.  The paging example is great.   ... View more

@UndralBatsukh This is a good suggestion and it will work for me, thanks! ... View more

Hi there,  This is my understanding of your question. I apologize if I did not understand the question. I think you are asking to run search when user clicks on features of a given feature layer and show a popupTemplate using results of the search. This codepen app shows a proof of concept for how it can be done: https://codepen.io/U_B_U/pen/oNaMVoe?editors=100 Essentially, you want to use MapView.hittest() to return a result only when user clicks on the featurelayer of your choice by setting includes parameter. If the hittest returns results then you can call search widget's search method using either attribute, geometry or long,lat. Once the search returns the result, then you can show the popup by calling view.popup.open() method. You can setup the action, content and title of the popup as needed.    Hope this helps, ... View more

@swiss_parks_network_nbernhard  It seemed more fitting to reply here rather than in the idea thread.  Basically, what I was saying there, was that you could create a Legend widget for each layer you want to display the symbology for.  You then add each widget instance to the page.  This is done by appending each widget's container node to an existing element on the page. I've made a crude example of this out of the Legend sample.  On that page, replace the contents of the second script tag with this code, and then click the Refresh label at the top right.   function addLegendForLayer(Legend, view, container, layer) { var childElement = document.createElement("DIV"); container.appendChild(childElement); const legend = new Legend({ view: view, layerInfos: [ { layer: layer, title: "NY Educational Attainment" } ], container: childElement }); } require(["esri/views/MapView", "esri/widgets/Legend", "esri/WebMap"], ( MapView, Legend, WebMap ) => { const webmap = new WebMap({ portalItem: { // autocasts as new PortalItem() id: "05e015c5f0314db9a487a9b46cb37eca" } }); const view = new MapView({ container: "viewDiv", map: webmap }); view.when(() => { var container = document.createElement("DIV"); container.style.backgroundColor = "#FFFFFF"; // Add widget to the bottom right corner of the view view.ui.add(container, "bottom-right"); addLegendForLayer(Legend, view, container, webmap.layers.getItemAt(0)); addLegendForLayer(Legend, view, container, webmap.layers.getItemAt(0)); }); });     This sample only had one layer, so for my example, I made two identical Legend widgets from the same layer.  But, the main thing is that you can see that both Legend elements are present on the page.  To the end user, this appears to be a single legend, but there's really multiple widgets there, one widget for each layer.  With this kind of workflow, it would be fairly easy to add logic for adding/inserting Legend widgets in a particular order to your liking. ... View more