Latest Contributions by DavidColey

Good to know.  Easy enough fix to apply in the api, where would one one change this in the WAB?  ... View more

I can confirm I get the same results: { "address": { "Street": "5504 ASHTON RD", "City": "NCTY", "ZIP": "34233", "Match_addr": "5504 ASHTON RD, NCTY, 34233" }, "location": { "x": -9179416.6356466208, "y": 3158060.4914356801, "spatialReference": { "wkid": 102100, "latestWkid": 3857 } } }‍ I can also confirm that this has been an issue in the api going back to at least 3.14 for the standard US Dual Range Addresses style address locator.  I had thought for sure I had posted about this earlier but alas the issue does not show up in anything I have posted.... ... View more

Right. So in my WABs here's what I get when I use the world geocode server with my local route NA service: I get the same results whether I use esri routing or my routing - notice the address ranges.  It's how my local streets locator is not defined / parameterized like esri's, you know? ... View more

Yeah something like that, there's no property changes to watch for or events.  I just found this in the .tsx for the widget: exportedFilesTitle: "esri-print__export-title",‍ maybe this is the class you need? ... View more

Sure thing glad to help ... View more

My apologies, I just checked and I did account for that in my 3.21 api.  Yes, I still do get that same behavior when I use my local streets locator service at 3.21, although I do not get a mix of lat/lon and WM coords.  I believe that's where using re-projected source layers helped.   But the only way I could ever get the interactive tool to display the addresses is to use the esri locator.  My workaround is to use the esri locator and my local NA service. Obviously that works but is not ideal.  ESRI needs to fix the library. ... View more

It looks to me like since you are trying to pass in value from your search input into the print title input, to me that says you need to force some kind of refresh or set some kind of event listener on the print widget as it's clearly not recognizing that it's title input contains text.  I'm not using jQuery so I can't really test that. ... View more

Hi Alex- I get the correct file name at 4.4 when I physically perform a copy-past from my search input to my print widgets title box and then click print  How are you trying to copy the value?  From like the "select-result" event? ... View more

Have you re-projected the routing and locator source layers to web mercator or are all in state plane?  ... View more

Sure.  As I recall we had difficulties with the logic for this type of "near me" workflow using queryFeature at 3.x which is why we went to the selectFeature method in the first place.  My goal above at 4.x isn't to necessarily highlight the intersecting features (but I do want to do that), but rather to pass the results into the popup. I think I have to find a way to clear the address info from the popup first before it can be reset with the returns from the queryFeauure array . . .  ... View more

Hi Kirsten, if I may we've been doing something similar since about 3.7: function showZones(evt) {     mapMain.graphics.clear();     if (evt.source.name == "Search by House Address" || evt.source.name == "Search by Street Address") {        qPoint = evt.result.feature.geometry;        var queryElemZones = new Query;        queryElemZones.geometry = qPoint;     var elemQuery = lyrElemZones.selectFeatures(queryElemZones,FeatureLayer.SELECTION_NEW);     mapMain.infoWindow.setFeatures([elemQuery]);     mapMain.infoWindow.show(qPoint);    elemQuery = lyrElemZones.selectFeatures(queryElemZones,FeatureLayer.SELECTION_SUBTRACT); }‍‍‍‍‍‍‍‍‍‍‍‍ This shows how we take the return geometry from an returned address and then use that to select the intersecting features, in this case a school zone.  Set the features in the infoWindow and show the window at the point return location. For 4.x, selectFeature method is not yet available for feature layer so the only option is to employ a queryFeatures method, something I'm still working on.  Here, we are using an address return point as an input to a buffer, then using the extent of the buffer to intersect and return features: function showResults(evt) {     app.activeView.graphics.clear;     console.log(app.search.sources);     if (app.search.sources.items[0].name == "Search by Address") {        console.log(app.search.sources);        var qPoint = evt.results[0].results[0].feature.geometry;        console.log(qPoint);        buffer = geometryEngine.geodesicBuffer(qPoint, [1], 9035, true);        var symbol = new SimpleFillSymbol({           color: [100,100,100,0.15],           style: "solid",           outline: { // autocasts as esri/symbols/SimpleLineSymbol              color: "white",              width: 0           }        });    graphicPoly = new Graphic({        geometry: buffer,        symbol: symbol,     });     app.activeView.graphics.add(graphicPoly); //geometry     var queryTran = new Query;     queryTran.geometry = buffer;     queryTran.spatialRelationship = "intersects";     //queryTran.where = ObjectID > 0 //Don't really need this since we're using the spatial relationship     var tranQuery = lyrMobBnds.queryFeatures(queryTran).then(function(tranResult) { //,    FeatureLayer.SELECTION_NEW);     console.log(tranResult); //Does get features! Can't seem to set the attributes in the popup though     if (tranResult && tranResult.features.length > 0) {        app.activeView.popup.open({        features: tranResult.features,        location: qPoint//result.geometry.centroid           });        }     });     } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ But I can't seem to figure out how to pass the results' return array and set that in my popup as opposed to the search result's return address.  I don't know if this will help you but maybe if there are more eyes on this some will have some ideas. ... View more

Hi all - so has anyone attempted this workflow / use case? ... View more

Ah just found it: search (query, item_type=None, sort_field=’avgRating’, sort_order=’desc’, max_items=10, outside_org=False) Thanks ... View more