Latest Contributions by PaulMcCord

I'm putting together a data collection workflow for our Parks Department that uses Survey 123. Data collection will include related records as one point may have many related surveys (example: a park bench that is visited once a month to record its condition). The Parks Dept wants a map-centric data collection workflow. I initially wanted to integrate Collector and Survey 123 so that data collectors could navigate to their points of interest with the Collector app and then tap on the point to open Survey 123. However, after speaking with Esri tech support, I was informed that the only way to be able to do this was to create the feature class in ArcGIS Pro first. I've decided against this since it doesn't seem scalable. In other words, if the Parks Dept has a 25 or 30 question form and the form is constantly being revised, I'm concerned that I'll run into data management or flexibility issues if I'm constantly publishing new feature classes from Pro. What would be ideal is if this could solely be done from Survey 123 (ie, publish a feature class when publishing my survey form), but Tech Support told me that I needed to create the feature class in Pro first if using related records in a Survey 123 form within Collector. I'd be happy to be told that I'm wrong, though. This is a long way of saying that I'm now trying to get a map-centric "feel" using solely Survey 123. I've enabled the Inbox setting on my form, which kind of gives it a map-centric feel, although I don't love it. Now I'm trying to pre-populate some of my survey fields if the record is selected from the Inbox. For example, if the bench is located in Park A, I want Park A to be pre-populated on the survey form in the "Park Name" field if the data collector has tapped on the bench point from the Inbox.  I knew how to do this when linking between Collector and Survey 123 by manipulating the URL scheme from Collector. Is there a way to do something similar if selecting an existing point from the Inbox map? ... View more

I'm using the Search tool to allow users to enter their address and be taken to their property of interest. This is for a parcel viewer application with over 800,000 records. Ideally, when the user enters their address in the Search, they will quickly be zoomed to their location of interest. However, right now it takes about 13 seconds for the Search to retrieve their address and zoom to the correct address. It's worth noting that all of the functionality is working (ie, the map eventually zooms to the location that was entered), it's just very slow. The parcel layer that is being searched is the same parcel layer that is displayed on the map (called parcelLyr in the below code). Below is the code for the search tool: //Create search tool to search addresses const searchTool = new Search({ view: myView, sources: [ { layer: parcelLyr searchFields: ["propstreet", "fullAdd2"], displayField: "fullAdd2", name: "LayerSearchSource", placeholder: "example: 500 Griswold", exactMatch: false, suggestionsEnabled: true, autoNavigate: false, resultGraphicEnabled: false, outFields: ["*"] } ], container: addressSearchBar, includeDefaultSources: false, resultGraphicEnabled: false, popupEnabled: false, locationEnabled: false, searchAllEnabled: false })‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Is there something I can do to ensure that the correct address is retrieved more quickly? Thanks, Paul ... View more