Latest Contributions by OttarViken_Valvåg

For what it's worth, the API's positioning logic for the Popup dijit is still not working satisfactorily for us in version 3.8. After some code digging, we determined that the issue for us is when the popup's content is large enough that there's no selection of anchor point for the popup that avoids the popup overflowing outside the map's boundaries. In this case, instead of making a best effort choice of anchor point, minimizing overflow, the API simply keeps the existing anchor point for the popup. It should be noted that the content's size is calculated from the dimensions of the Popup._positioner dom element, which appears to be the size of the largest content ever displayed in the popup. So if you're not currently displaying a large popup, you may still have the issue because you previously showed content that caused the _positioner to expand in size. Our solution was to override the Popup._setPosition function and add logic for the case when no anchor point avoids overflow. Here's what our added logic looks like (in the final else): if (roomToTheRight && roomAbove) {     horAnchor = "Left"; verAnchor = "bottom"; } else if (roomToTheRight && roomBelow) {     horAnchor = "Left"; verAnchor = "top"; } else if (roomToTheLeft && roomBelow) {     horAnchor = "Right"; verAnchor = "top"; } else if (roomToTheLeft && roomAbove) {     horAnchor = "Right"; verAnchor = "bottom"; } else {     // No room in any direcion, choose anchor that gives most room     var horCoverages = [];     horCoverages.push({ "anchor": "", "overflow": Math.max(0, (contentBox.w / 2) - (absoluteX - left)) + Math.max(0, (contentBox.w / 2) - (right - absoluteX + 1)) });     horCoverages.push({ "anchor": "Right", "overflow": Math.max(0, contentBox.w - (absoluteX - left)) });     horCoverages.push({ "anchor": "Left", "overflow": Math.max(0, contentBox.w - (right - absoluteX + 1)) });     var verCoverages = [];     verCoverages.push({ "anchor": "", "overflow": Math.max(0, (heightNeeded / 2) - (absoluteY - top)) + Math.max(0, (heightNeeded / 2) - (bottom - absoluteY + 1)) });     verCoverages.push({ "anchor": "bottom", "overflow": Math.max(0, heightNeeded - (absoluteY - top)) });     verCoverages.push({ "anchor": "top", "overflow": Math.max(0, heightNeeded - (bottom - absoluteY + 1)) });     var sortFunction = function (a, b) { return a.overflow > b.overflow; };     horCoverages.sort(sortFunction);     verCoverages.sort(sortFunction);     horAnchor = horCoverages[0].anchor;     verAnchor = verCoverages[0].anchor;     console.log("There's no room for the popup, chose most optimal anchoring " + verAnchor + horAnchor + "..."); } ... View more

My apologies, I need to retract the above. I can't reproduce my problem today using that procedure. ... View more

From the REST API documentation: Note: In the case of dynamic layers the layer list is ignored, it instead uses top or all (default) to identify the layers defined in dynamicLayers parameter. ... View more

That's great, thank you. ... View more

I've also found that the Locate Button does not work with non-mercator projections. The fairly obvious requirement of projecting the lat/long coordinate to the map's spatial reference doesn't seem to be implemented. I added the functionality to the LocateButton by overriding the private _setPosition method using version 3.8 of the API. Since it's a private method the fix could break with updates of the API though. Hopefully ESRI can incorporate this functionality in future versions of the API, it's literally 3 extra lines of code. require([     "dojo/_base/lang",     "esri/dijit/LocateButton",     "dojo/Deferred",     "esri/config",     "esri/geometry/Point",     "esri/SpatialReference" ], function (     lang,     LocateButton,     Deferred,     esriConfig,     Point,     SpatialReference ) {     lang.extend(LocateButton, {         _setPosition: function (location) {             var deferred = new Deferred;             if (location && location.coords) {                 var point = null;                 var scale = this.get("scale") || location.coords.accuracy || 5E4;                 if (point = new Point([location.coords.longitude, location.coords.latitude], new SpatialReference({ wkid: 4326 }))) {                     esriConfig.defaults.geometryService.project([point], this.map.spatialReference).then(lang.hitch(this, function (projectedPoints) {                         point = projectedPoints[0];                         var event = this._createEvent(point, scale, location);                         if (this.get("setScale")) this.get("map").setScale(scale);                         if (this.get("centerAt")) {                             this.get("map").centerAt(point).then(lang.hitch(this, function () {                                 deferred.resolve(event);                             }), lang.hitch(this, function (err) {                                 if (!err) err = Error("LocateButton::Could not center map.");                                 deferred.reject(err);                             }));                         }                         else {                             deferred.resolve(event);                         }                     }), lang.hitch(this, function (err) {                         if (!err) err = Error("LocateButton::Could not project point to map's spatial reference.");                         deferred.reject(err);                     }));                 }                 else {                     var err = Error("LocateButton::Invalid point");                     deferred.reject(err)                 }             }             else {                 var err = Error("LocateButton::Invalid position");                 deferred.reject(err);             }             return deferred.promise;         }     }); }); ... View more

It would be nice to have a better workaround for this in 10.1. Increasing the cleanup time of the output directory won't really help. Is it possible to configure http headers returned by arcgis server to tell the browsers not to cache the output images? ... View more

Thanks for nailing this bug for me! ... View more

Well it seems this was caused by missing language files for network analyst directions. Apprarently, if you're running a non-english locale you need to add a language file for your own locale even if you just want english directions? I didn't bother researching the full issue here since I did have language files that I wanted to install anyway, but this really should have been working out of the box even on a non-english locale. (I added language files to C:\Program Files\ArcGIS\Server\NetworkAnalyst\Directions to fix my issue.) ... View more

My apologies, I posted that being logged in as the wrong user, the above was actually posted by me. I'm going to repost this issue in the ArcGIS Server forum though. ... View more

In case it wasn't clear, the reason you returnStateAverage function doesn't return anything is that the return statement marked in red doesn't return from that function - it returns from the function marked in blue. function returnStateAverage(geography, indicator){     var stateVal;     var myURL = "stateURL";     queryTask = new esri.tasks.QueryTask(myURL);     query = new esri.tasks.Query();     query.returnGeometry = false;     query.outFields = ["*"];     query.where = "State_name='" + geography + "'";     queryTask.execute(query, function(fSet) {         var features = fSet.features; dojo.forEach(features, function(feature) { stateVal = feature.attributes[indicator]; return stateVal; });     }); } When I say "cleanest" I mean that it's the recommended practice when dealing with asynchronous methods. Recommended reading: http://dojotoolkit.org/documentation/tutorials/1.6/deferreds/ ... View more

That's because your returnStateAverage function doesn't actually return any value. You only have a return statement in your anonymous function passed to the forEach() method. Furthermore, all the logic following your returnStateAverage call needs to be moved to the result handler of your queryTask.execute call in the returnStateAverage function, since the queryTask.execute method works asynchronously (more formally, it returnes a dojo.Deferred object). The cleanest implementation would probably be to let your returnStateAverage function return a Deferred object. ... View more