Latest Contributions by MikeTschudi

Hi David, Progress has been stalled due to both technical challenges and time assignments, but I very much want to solve this one. Regards, Mike ... View more

Hi Jordan, LocatorNameFields is used to connect the locator service to the app, because a call to a locator service in turn spawns calls to multiple types of locator.  When a response comes back from the locator, it can contain a response from each of the subsidiary locators; FieldName is the name of the attribute field with the name of subsidiary locator that provided a response. E.g., here is a snippet of a response     "candidates": [{         "address": "971 Sylvan Cir, Naperville, IL, 60540",         "location": {             "x": -9810866.9852000009,             "y": 5126375.4676999971         },         "score": 100,         "attributes": {             "Loc_name": "US_RoofTop",             "Score": 100,             "Match_addr": "971 Sylvan Cir, Naperville, IL, 60540",             "House": "971",             "Side": "L",             "PreDir": "",             "PreType": "",             "StreetName": "Sylvan",                 :        :        : Note the attribute "Loc_name" tells you that this candidate address came from the "US_RoofTop" subsidiary locator. FieldValues holds the list of subsidiary locators whose results you want to display to your user.  In our try-it, e.g., the default address returns results from locators "US_RoofTop", "US_Streets", "US_StreetName", "US_Zipcode", and "US_CityState", but we only want to display results from "US_RoofTop" and "US_StreetName". LocatorFields holds the name of the field that the locator service defines to accept a single-line address input parameter (i.e., one that doesn't have to be parsed by the app into street, city, etc., parameters). Our try-it uses the TA_Address_NA_10 service, which names this field "SingleLine". The newer World Geocoding Service also uses this name. (See also the ArcGIS API for JavaScript documentation for esri.tasks.Locator.addressToLocations().) ... View more

Hi Jordan, Some things that you might try: Run the js\config.js file through a syntax checker such as JSLint. Check that the configuration for Trash Pickup and Recycling Pickup do *not* have a "distance" parameter--that parameter is used to tell the difference between polygonal and point feature layers; the app does a point-in-polygon test for the former and a buffered-distance search around the point for the latter. Try displaying just one field ("Field" tag only; leave out "ServiceAvailability" and "Links" tags) for each of the pick up layers to simplify the testing, and then adjust the content once that part passes. Turn on debugging display (F12 in Chrome, Firefox with Firebug, IE) to see if there are error messages displayed under the console tab or nonresponsive layers displayed under the network traffic tab Is your site reachable from outside your network? Regards, Mike ... View more

Hi Tiffany, We aimed for a streamlined popup that would be more effective across browsers and platforms, but had underestimated the importance of paging through overlapping features. We changed the template back to the earlier popup and the change will be part of the next AGOL release. No change will be necessary to your web apps. If you're hosting the app on your own server, or want to host it on your server to get the change sooner, you can get the modified template from the Esri GitHub site. Regards, Mike ... View more

Hi Chris, It helps that you've narrowed it down. At this point, I'd bring in Esri Support to help diagnose the GP service. Regards, Mike ... View more

Hi Rafael, Which version of Election Polling Places did you download? If it was 10.1, did you see the 10.1 setup instructions; if it was 10.2, which came out today, did you see the 10.2 setup instructions? The downloads do not come with services. You can point them to our try-it services to test the download, and then re-configure the apps to point to your services. As an example, the js/config.js file for the 10.2 version is attached. Regards, Mike ... View more

Hi Craig, It sounds to me, too, that the problem is related to the expiring token, but I can't reproduce it. The proxy program looks for a token in its cache; if it finds it, it uses it to save the roundtrip to the authentication server; if there isn't one (because the proxy.ashx program changed, or the token never existed, or the token expired), it creates a new token and caches it. The cache expiration is set to the same UTC time as the token's expiration time. I modified the proxy.ashx program to include some diagnostic headers and checked it into GitHub in the master branch. The diagnostics add headers to the response that the proxy.ashx program sends to the browser so that we can see some of the caching behavior. Since the diagnostics are optional, you'd set constant cShowAuthXHeaders to 'true' to turn on the headers. The approach that I'd try is to first clear the token cache. The proxy.ashx program will do this for you if you rename/remove the proxy.config file from the site, and then access the proxy.ashx program either by refreshing the gallery or by calling the proxy directly, as in http://<myServer>/<myGallerySite>/proxy.ashx You'll see a 500 internal server error, but it will also tell you that the cache was cleared. Next, restore the proxy.config file to the site and change the tokenDurationMinutes to something small, say 5 minutes or even 2 minutes. Refresh the gallery. Using Fiddler2 or Chrome's debugging Network tab or Firebug's Net tab, look for the network call http://<myServer>/<myGallerySite>/proxy.ashx?http://www.arcgis.com/sharing/search and look at its response headers. (It's a POST about 3/4 of the way down the network window in each of these three debuggers, after a large number of Dojo files.) The headers we've added (with sample values) are X-AuthExpiration: 7/30/2013 7:06 PM UTC X-FromCache: False X-UTCNow: 7/30/2013 7:04 PM UTC The first provides the expiration time of the token and the cached value of the token. The second indicates if the token came from the cache (true) or not. The third provides the current time in UTC for convenience. If you refresh the gallery again before the token expires, you'll get the same expiration time, but you'll see that the token this time came from the cache. X-AuthExpiration: 7/30/2013 7:06 PM UTC X-FromCache: True X-UTCNow: 7/30/2013 7:05 PM UTC One more refresh, but this time after the expiration of the token, yields X-AuthExpiration: 7/30/2013 7:09 PM UTC X-FromCache: False X-UTCNow: 7/30/2013 7:07 PM UTC This should be what you're seeing. If all is OK here, we can add more diagnostic headers. Regards, Mike ... View more

Hi Justin, The app displays that message when it finds no precincts at the address' point in the PrecinctLayer service or a webmap's precinct operational layer. And this stops the processing, so no route is generated. In order to make webmaps easier to use, the app makes the crucial assumption that polygonal layers that have a popup are tested for elected officials data; the layer without a popup is used for precinct boundaries. If you're using a webmap and all layers have a popup, I believe that this would prevent the app from identifying the precinct layer. Regards, Mike ... View more

Hi Chris, That message appears when the geoprocessing service that generates the PDF or CSV returns an "esriJobFailed" status. What happens when you run a test job submit from the geoprocessing service itself? Regards, Mike [ATTACH=CONFIG]26295[/ATTACH] ... View more

Hi Jason, My Government Services only supports polygons (for service areas) and points (for service locations) at this time. Please add it to the ArcGIS Ideas list for Local Government to give it some momentum. Regards, Mike ... View more

Hi Beckie, Thank you for the link--it helped me to see what I believe the problem to be. Please try your app without Bing Maps for the time being. One of our developers found that if the webmap uses a Bing basemap, our JavaScript API does not always provide the app with spatial reference information. He fixed that, and the fix will be in the version of the template coming out this week. Regards, Mike ... View more

Hi Nathan, Is your existing web map public?  I'm really curious about the results that you figured out.  The webmap doesn't store app information--it's the other way around--so I would like to understand how a new apps has trouble with this particular existing web map and figure out a solution. Thanks, Mike ... View more

Hi Craig, Your information was very helpful. It appears that the 2-character query is rejected by the server. Searching for '%1%' returns results: https://www.marioncountyfl.org/arcgis/rest/services/Dynamic/ParcelViewer/FeatureServer/0/query?f=json&where=UPPER(PARCELID)%20LIKE%20'%251%25'&returnGeometry=false&spatialRel=esriSpatialRelIntersects&outFields=OBJECTID%2CPARCELID&outSR=102100 Searching for '%12%' is rejected by the server: https://www.marioncountyfl.org/arcgis/rest/services/Dynamic/ParcelViewer/FeatureServer/0/query?f=json&where=UPPER(PARCELID)%20LIKE%20'%2512%25'&returnGeometry=false&spatialRel=esriSpatialRelIntersects&outFields=OBJECTID%2CPARCELID&outSR=102100 Because the app searches with a wildcard before and after the typed-in string and this type of search cannot use the server's indices, the newest version of the template--coming out Monday or very shortly afterwards--has a configurable option to not include the leading wildcard. If you try the two URLs above with the leading wildcard (%25) omitted, both return quickly with lots of results. In order to use this version when it arrives, the simplest method would be to you re-publish your webmap. The URL will change slightly--from s1.html to s2.html. Regards, Mike ... View more

Beckie, Nathan, Craig, Are your web maps or web apps public? I'd be happy to take a look at them. The only known restriction for the search is when a layer is nested in a webmap at a level lower than the top level. There's not enough information in the lower level to do the search, but we are interested in solving that. This restriction tends to be caught at the configuration stage, however. Are you using the software version hosted by AGOL (http://www.arcgis.com/apps/Solutions/s1.html?appid=...) or a downloaded version? We've had problems with the download zip getting corrupted: an old version taking the place of the correct version. Regards, Mike ... View more

Hi Allison, Using the 10.1.1 version of the app, I configured     BaseMapLayers: [{         Key: "topo",         ThumbnailSource: "images/parcelMap.png",         Name: "Topo",         MapURL: "http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer"     }],     // Initial map extent. Use comma (,) to separate values and dont delete the last comma.     DefaultExtent: "-8999921,5285755,-8686223,5560929", (Changed the basemap, which controls the extents within which valid addresses must exist and changed the default extent to the Toronto area.) and // ------------------------------------------------------------------------------------------------------------------------ // ADDRESS SEARCH SETTINGS // ------------------------------------------------------------------------------------------------------------------------ // Set Locator service URL. LocatorURL: "http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer", //Set locator name fields to search. LocatorNameFields: [{     FieldName: 'Loc_name',     FieldValues: ["CAN.PointAddress", "CAN.StreetAddress"] }], // Set Locator fields (fields to be used for searching). LocatorFields: "SingleLine", // Set default address to search. LocatorDefaultAddress: "12 Concorde Place Toronto ON M3C 3R8", (Configured the World/GeocodeServer because it's in General Availability--NA_10 is being retired at the end of this year.) and I can search for Toronto addresses. From the config snippet, it looks like you may be using a pre-10.2 version. In that version, I made the same basemap and default extent changes as above and changed the locator config to // ------------------------------------------------------------------------------------------------------------------------ // ADDRESS SEARCH SETTINGS // ------------------------------------------------------------------------------------------------------------------------ // Set Locator service URL. LocatorSettings: {     LocatorMarkupSymbolPath: "images/RedPushpin.png", // Set pushpin image path.     MarkupSymbolSize: {         width: 25,         height: 25     },     Locators: [{         DisplayText: "Search Address",         DefaultValue: "12 Concorde Place Toronto ON M3C 3R8", // Set default address to search.         LocatorParamaters: ["SingleLine"], // Set Locator fields (fields to be used for searching).         LocatorURL: "http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer",         CandidateFields: "Loc_name, Score, Match_addr",         DisplayField: "${Match_addr}",         AddressMatchScore: 80,         LocatorFieldName: 'Loc_name',         LocatorFieldValues: ["CAN.StreetName", "CAN.PointAddress", "CAN.StreetAddress"]     }] }, Regards, Mike ... View more