Latest Contributions by BryanMc

Attempting to use the API Identify operation with identifyParameters to identify on a map service. Goal is to have the results return to the popup with popup highlight graphic on the map. There are some bugs based on setting various identifyParameters not working as expected or sending lots of additional fetch requests (based on 4.25). The starting point was using the API Sample: Works: If set layerIds and returnGeometry false (don't set sublayers): Identify returns, popup shows and no highlight graphic [makes sense] Issue: If set layerIds and returnGeometry true (don't set sublayers): Identify returns (with geometry), popup shows but not highlight graphic [issue as should be able to see highlight graphic]. seems like a separate issue where the PopUp doesn't show the highlight graphic properly. Can replicate issue by sending a feature with graphic to the popup and it will not show the highlight graphic. Issue: If set sublayers (with or without layerIds): Identify returns, popup with highlight graphic - Seems good at first but it sends 2 additional fetch requests, a query request and map export request. The identify return graphic will show for split second but is then replaced by the extra query response graphic. Extra query/export requests shouldn't be needed/called and adding lots of chatter. If many features in popup, scrolling to next feature will continually call the additional query and export requests each time as well. Issue: Setting maxAllowableOffset and sublayers: The maxAllowableOffset is honored in the identify response, but then replaced by the extra query response graphic (and query result graphic doesn't honor the maxAllowableOffset). Extra query/export requests shouldn't be needed/called (also does this for each 'Next feature' in popup too). Issue: Setting sublayers with returnGeometry false: Still always does the extra 2 fetch requests (query/map export) and shows the popup with a graphic. The Identify response honors the returnGeometry setting but is ignored for the additional query request.   Hoping I'm just missing something here, any thoughts on workarounds would be appreciated. I did attempt writing an esriRequest to the map service rest identify endpoint. Everything works except the showing of the graphic highlight in the popup (same as #2). ... View more

Starting with the 4.25 release, the MapView container property must reference an ID of a DIV element. This aligns with the documentation for the container property (HTMLDivElement) for 4.25 and even historical help versions. However, in previous versions (4.24) this wasn't enforced allowing developers to use other element types: SPAN, MAIN, P, etc. An error message: [esri.views.MapView]" "#container" "element with id 'viewDiv' not found will be in the console. Is it possible to update the error message to be more specific in this scenario, or list a breaking change in the what's new for 4.25 section (recognizing it was listed as a HTMLDivElement requirement historically but not enforced)? ... View more

Wondering if it's possible to cancel a search within the search widget (ArcGIS JavaScript API 4.24) based on the text in the search widget text area before it is sent to an online source? I'm able to trap the search when it starts, but there isn't an event to cancel/abort from yet. I don't want to use the 'search-complete' event since it's already too late at that point.    searchWidget.on("search-start", function (event) { if (searchWidget.searchTerm == "my search term") { //Cancel the search } });   The goal is to interrogate the search string for a specific value and cancel the search to perform a different action.  TLDR: Would like to listen for a local coordinate input x,y using a regex. If matches the pattern, don't send a search, just pan/zoom the map (since map is in a local coordinate system as well). I've also looked at reactiveUltils, but can't seem to figure out how to cancel the search. ... View more

We created a new ArcGIS Story Map and published. This works on Desktop with Edge, Firefox, and Chrome just fine, but not working at all on iOS (both Chrome and Safari). Getting the error "Hmm... there seems to be an issue". iOS version is the latest as time of writing (iOS 15.3.1), and the Story isn't very complex. Public Link: https://arcg.is/1OyzvG0 We read some of the recent related posts (updating iOS, or related to some parts not showing, or complex stories). Our story is pretty simple, latest iOS, and the entire Story map doesn't load in any way. Tried both private mode and regular within iOS browsers, clearing cache, etc. No luck as of yet. Same issue in Android OS as well. ... View more

Some previous posts have starting discussing LiDAR data in Ontario, Canada using the PCS: NAD83 CSRS v7 (epoch 2010). This is related, but more specifically about how ArcMap handles some of these projections and their differences. Hoping Melita Kennedy‌ is watching this thread We are using both ArcMap 10.6x with some partner agencies using 10.3x. We noticed that the new GCS for NAD83CSRS v7 (8255) is available in ArcGIS 10.6x and Pro, so we've created a new custom PCS using this GCS reference. This creates our PCS projection file - all is well so far. Our questions are when looking at the details of the new PRJ and the related GCS PRJ files... 1. In looking at the details of the GCS for "NAD83(CSRS)v7" and comparing to another version such as "NAD83(CSRS)v3", there is no real difference in the details (beyond names). Is there something that makes these (all 7 versions of this GCS) different? Possibly an underlying DLL that has the additional "Reference Epoch Coordinate Transformation" values stored - as this is the only difference notice b/w the GCS's when digging into the EPSG site (wayyy deeper than I truly understand). Example: v7 uses the epoch reference EPSG:1198, while v3 uses EPSG:1194. But this detail isn't in the prj and not sure if this has any impact, or how the software can tell the difference. Or is this something that only matters if transformation from one to another - realizing these transformation aren't out there? 2. Based on the above, will this custom PCS.PRJ work with ArcMap 10.3 since GCS 8255 and possibly underlying reference datum/epoch values not being available in older versions of the software? Phew, I really hope that made sense. I thank everyone who even read this far -  and any insights you may have. ... View more