Latest Contributions by bobcarr

‎11-22-2013

The module "dojo/dom-geometry" might be helpful. I was faced with a similar infoWindow scrollbar issue this week and it seems to be resolved after adding some code which incorporates that module. The variance in size for me was in height-only, as I was using NWS weather observation XML and which varies in content by station and observation time. The variance you describe seems to be in both dimensions, and probably much larger in magnitude. I create the div (and assign it an ID) in the function which processes the output from the XHR request, then include the dojo/dom-geometry module in the function tied to the mouse-over event. The dom-geometry module is used against the div id to obtain its dimensions, which you can then use to calculate/set a new infoWindow size. /* excerpt from function mkinfoWindowContent var infocontdiv = domConstruct.create("div"); infocontdiv.id = "wthrdiv"; infocontdiv.innerHTML = content; r9WthrApp.map.infoWindow.setContent(infocontdiv); /* excerpt from function which uses dojo/dom-geometry to determine height of content require(["dojo/_base/Deferred","dojo/dom","dojo/dom-geometry"], function(Deferred,dom,domGeom){ . . . var retdata = new Deferred(); retdata = getWthrXML(forestnum); //deferred retdata.then( function(xmldoc) { mkInfoWindowContent(xmldoc); (evt) ? r9WthrApp.map.infoWindow.show(evt.screenPoint,r9WthrApp.map.getInfoWindowAnchor(evt.screenPoint)) : null; var node = dom.byId("wthrdiv"); var coords = domGeom.position(node); var newht = coords.h + 50; //coords.h is height property r9WthrApp.map.infoWindow.resize(250,newht); } ); //end deferred then });

‎09-03-2013

Thank you for taking the time to review the code and suggest a fix. Moving the return call inside the inner function did not resolve the issue. Using a callback function and placing its call within the inner function has resolved the error and the dialog box now shows the content pane and tab container as it did prior to AMD implementation. Shown below are the changes made to the code. To use the callback, I modified the call to the getTextContent function. Old call to function var content = getTextContent(evt.graphic); wsDialog.setContent(content); dojo.style(wsDialog.domNode, "opacity", 1.0); dijit.popup.open({ popup: wsDialog, x:evt.pageX, y:evt.pageY }); New call to function getTextContent(evt.graphic,function() { wsDialog.setContent(lscapp.cp.domNode); dojo.style(wsDialog.domNode, "opacity", 1.0); dijit.popup.open({ popup: wsDialog, x:evt.pageX, y:evt.pageY }); }); Then modified the getTextContent Function function getTextContent(graphic,callback) { require (["dojox/xml/DomParser", "dojox/xml/parser", "dojo/date/locale", "dijit/layout/ContentPane", "dijit/layout/TabContainer"], function (DomParser,parser,locale, ContentPane,TabContainer) { ... /* content pane and tab container building code removed */ ... lscapp.cp.startup(); callback(); }); }

‎08-30-2013

Re-doing our web application to use the AMD style, I have one function which throws a type error on its first call. On subsequent calls, the content pane appears in the dialog box. Prior to implementing AMD (and setting "asynch:true"), the function always returned a content pane without error. The type error showing the variable 'lscapp.cp' as undefined is thrown from the last statement in the function shown below. I am thinking that dojo/Deferred might resolve this, but even after reading related posts here and at the Dojo site, I'm not sure how to get the appropriate return value passed to the calling function. function getTextContent(graphic) { require (["dojox/xml/DomParser", "dojox/xml/parser", "dojo/date/locale", "dijit/layout/ContentPane", "dijit/layout/TabContainer"], function (DomParser,parser,locale, ContentPane,TabContainer) { if(dijit.byId('wscontpane')){ dijit.byId('wscontpane').destroy(); } var partners = graphic.attributes.KNOWN_PARTNERS; var estCompDate; var estCost; if (!graphic.attributes.ESTIMATED_COMPLETION_DATE == '') { estCompDate = new Date(graphic.attributes.ESTIMATED_COMPLETION_DATE); estCompDate = locale.format(estCompDate, { selector: 'date', datePattern: 'MMMM d, y' }); } else { estCompDate = ''; } if (!graphic.attributes.ESSENTIAL_PROJECT_EST_COST == '') { estCost = '$' + dojo.number.format(graphic.attributes.ESSENTIAL_PROJECT_EST_COST) } else { estCost = ''; } var jsdom = DomParser.parse(partners); //console.debug(jsdom); var docNode = jsdom.documentElement; partners = ""; if (docNode) { var nodestoprocess = docNode.childNodes; for (var i = 0; i < nodestoprocess.length; i++) { partners += parser.textContent(docNode.childNodes.childNodes[0]) + " " ; } } lscapp.cp = new ContentPane({ id: 'wscontpane', isContainer:true, content:'' + graphic.attributes.FOREST_NAME + ' ' + '' + graphic.attributes.WATERSHED_NAME + '<hr>'}, dojo.create('div')); var tc = new TabContainer({ id:'wsTabCont', style: 'width:350px;height:264px;line-height:150%;' + 'font-family: Verdana,Arial,Helvetica,sans-serif;'}, dojo.create('div')); var pane1 = new ContentPane({ title:'Abstract', id:'wstab1', content:'Watershed Code: ' + graphic.attributes.WATERSHED_CODE + ' ' + 'Total Acres: ' + dojo.number.format(graphic.attributes.TOTAL_WATERSHED_AREA_ACRES, {places:0}) + ' ' + 'Forest Service Ownership: ' + graphic.attributes.FS_OWNERSHIP_PERCENT + '% ' + 'Condition - Forest Service Area: ' + graphic.attributes.WATERSHED_CONDITION_FS_AREA + ' ' + 'Year Identified: ' + graphic.attributes.YEAR_PRIORITY_IDENTIFIED + ' ' + 'Estimated Completion Date: ' + estCompDate + ' ' + 'Estimated Cost: ' + estCost }); dojo.addClass(pane1.domNode, "wstab"); var pane2 = new ContentPane({ title:'Conditions', id:'wstab2', content:'Aquatic Habitat: ' + graphic.attributes.AQUATIC_HABITAT_CONDITION + ' ' + 'Aquatic Biota: ' + graphic.attributes.AQUATIC_BIOTA_CONDITION + ' ' + 'Water Quality: ' + graphic.attributes.WATER_QUALITY_CONDITION + ' ' + 'Water Quantity: ' + graphic.attributes.WATER_QUANTITY_CONDITION + ' ' + 'Wetland Vegetation: ' + graphic.attributes.RIPARIAN_WETLAND_VEG_CONDITION + ' ' + 'Forest Cover: ' + graphic.attributes.FOREST_COVER_CONDITION + ' ' + 'Forest Health: ' + graphic.attributes.FOREST_HEALTH_CONDITION + ' ' + 'Soil: ' + graphic.attributes.SOIL_CONDITION + ' ' + 'Roads and Trails: ' + graphic.attributes.ROADS_AND_TRAILS_CONDITION }); dojo.addClass(pane2.domNode, "wstab"); var pane3 = new ContentPane({ title:'Justification', id:'wstab3', style:'line-height:125%; margin:10px', content: graphic.attributes.SELECTION_NARRATIVE }); dojo.addClass(pane3.domNode, "wstab"); var pane4 = new ContentPane({ title:'Partners', id:'wstab4', content: partners }); dojo.addClass(pane4.domNode, "wstab"); tc.addChild(pane1); tc.addChild(pane2); tc.addChild(pane3); tc.addChild(pane4); tc.startup(); lscapp.cp.addChild(tc); lscapp.cp.startup(); }); return lscapp.cp.domNode; }

‎07-16-2013

I'm trying to reverse engineer a JavaScript viewer that consumes a dynamic map service. I know it's getting tiles from a URL like this: http://domain/ArcGIS/rest/services/D_LEGENDLAYERS/MapServer/export?layers=show%3A0%2C10%2C22%2C53%2C63%2C73%2C125%2C96%2C108%2C83%2C93 The 'layers' parameter decoded is: show:0,10,22,53,63,73,125,96,108,83,93 If I wanted to rewrite the constructor for this layer, how would I pass it those IDs? I don't see anything like that in the options. Thank you! Robert Check the API documentation for the ImageParameters class. An example below uses layerIds 0 and 1. var layerParams = new esri.layers.ImageParameters(); var layerDefs = []; layerDefs[0] = "REGION='09'"; layerDefs[1] = "REGION='09'"; layerParams.layerDefinitions = layerDefs; layerParams.layerIds = [0,1]; layerParams.layerOption = esri.layers.ImageParameters.LAYER_OPTION_SHOW; layerParams.transparent = true; var FSRegions = new esri.layers.ArcGISDynamicMapServiceLayer ("http://apps.fs.fed.us/ArcN/rest/services/EDW/EDW_RegionBoundaries_02/MapServer", {"opacity":0.9, "imageParameters":layerParams });

‎05-14-2013

No solution yet. I will revisit this today, possibly replacing the tooltipDialog with another widget.

‎04-10-2013

Thanks, Steve. I had also found the css class for the connector, but would prefer to keep it and have it correctly positioned. Using it at other places in the map for tool and layer descriptions, the connector for the tooltip dialog is positioned correctly.

‎04-09-2013

This past week, implementing a tooltipDialog popup similar to the ArcGIS sample posted at: http://developers.arcgis.com/en/javascript/samples/fl_hover/, I am encountering the same sort of tooltip connector displacement shown in the sample, and unsure how to correct it. At the sample page, opening a tooltip dialog shows the tooltip connector rendered at the lower-left corner of the dialog, and not connected to the feature being displayed. Below is the code we are using for a similar tooltip dialog. wsDialog = new dijit.TooltipDialog({ id: "wsDialog", style: "width: 375px; font: normal normal normal 10pt Helvetica;z-index:100", onMouseLeave: function(){ dijit.popup.close(wsDialog); map.graphics.clear(); window.clearTimeout(timeOutAction); } }); wsDialog.startup(); dojo.connect(dijit.byId("wsDialog"),'onShow',function(){ dijit.byId("wscontpane").resize(); }); maphandles.push(dojo.connect(FL_fs_pr_ws,"onMouseOut",function() { window.clearTimeout(timeOutAction); })); //listen for when the onMouseOver event fires on the prioritywatershedsLayer //when fired, create a new graphic with the geometry from the event.graphic and add it to the maps graphics layer maphandles.push(dojo.connect(FL_fs_pr_ws, "onMouseOver", function(evt) { if (timeOutAction !== undefined) { // if timeOutAction is not null or undefined, clear it out. window.clearTimeout(timeOutAction); } timeOutAction = window.setTimeout(function () { map.graphics.clear(); var highlightGraphic = new esri.Graphic(evt.graphic.geometry,pr_ws_hiliteSymbol); map.graphics.add(highlightGraphic); var content = getTextContent(evt.graphic); wsDialog.setContent(content); dojo.style(wsDialog.domNode, "opacity", 0.85); dijit.popup.open({popup: wsDialog, x:evt.pageX,y:evt.pageY}); },500); })); Looking at the CSS, I saw no settings that seemed to affect connector placement. A screen capture showing tooltip connector displacement is attached. Thanks.

‎04-04-2013

Here's a code snippet showing how to use the old info window instead of the popup. Note that the sample points to esri.esri.dijit.InfoWindow at the next version of the api (3.5) we'll fix this so you just need to enter esri.dijit.InfoWindow. var map = new esri.Map("map", { basemap: "streets", center: [-98.215, 38.382], zoom: 7 }); var infoWindow = new esri.esri.dijit.InfoWindow({}, dojo.create("div", null, map.root)); infoWindow.startup(); map.setInfoWindow(infoWindow); Thank you for posting this snippet. Using this, our web map now displays the traditional infoWindow.

‎03-25-2013

From the 'What's New in Version 3.4 ', I read: The popup widget is now the default info window for the map. Most ArcGIS API for JavaScript users prefer the popup's look and feel and, after some refactoring some internal dependencies, using the popup as the default makes sense. Additional changes to the popup include: easier to place the popup in a container outside the map, better support for right-to-left content and several new config options to control paging controls and how features are highlighted Does having the popup as the 'default' mean that the previous info window provided by the esri.dijit.infowindow might still be available as an alternative? If so, is it set within the map constructor? Looking through the map constructor options for Version 3.4, I see only the infoWindowBase option whose implementation seems to require a custom module.

‎08-31-2012

I have posted a sample (http://jsfiddle.net/bob_carr/EB86S/) of the drawing errors which occur when using SNAPSHOT mode on services with scale-dependent layers. Besides drawing at all scales, the second layer does not respond to panning or zooming. The 'DOCTYPE' and CSS settings mentioned in other Forum posts about frozen panning are applied in this sample. In our application (internal - not available for viewing), SNAPSHOT mode is preferred, as we have only 14 features for possible display, and are using the graphics attributes to change symbology for sub-sets of the 14 feature based on a selection from a drop-down menu. We need to maintain this symbology through all zoom levels. Our work-around has been to request the service providers create another map service with no scale-dependency for the unit polygons. Would another possibility be to use ONDEMAND mode and pass the symbol settings from one layer to another when the zoom level triggers a layer change?

‎09-27-2011

Using the constructor to extend the TileMapServiceLayer (http://help.arcgis.com/en/webapi/javascript/arcgis/help/jshelp/inside_custom_layers.htm), and reversing the order of "row" and "col" in the arguments to the calling function, I believe the map is now returning the correct tiles. A sample is posted at: http://geologic.dyndns.org/new_nexrad.html Thanks, Derek, for reviewing my earlier post. function init() { initLayer(); var map = new esri.Map("map"); var startExtent = new esri.geometry.Extent({"xmin":-11301768,"ymin": 3962510, "xmax":-7052110,"ymax": 6422839,"spatialReference": new esri.SpatialReference({"wkid":102100})}); map.setExtent(startExtent); map.addLayer(new MesonetNexTiledMapServiceLayer()); } function initLayer(){ dojo.declare("MesonetNexTiledMapServiceLayer", esri.layers.TiledMapServiceLayer, { constructor: function() { this.spatialReference = new esri.SpatialReference({ wkid:102100 }); this.initialExtent = (this.fullExtent = new esri.geometry.Extent(-20037508.340000,-20037508.340000,20037508.340000,20037508.340000, this.spatialReference)); this.tileInfo = new esri.layers.TileInfo({ "rows" : 256, "cols" : 256, "dpi" : 96, "format" : "PNG24", "compressionQuality" : 0, "origin" : { "x" : -20037508.340000, "y" : 20037508.340000 }, "spatialReference" : { "wkid" : 102100 }, "lods" : [ {"level" : 0, "resolution" : 156543.033928, "scale" : 591657528}, {"level" : 1, "resolution" : 78271.51695000000472646207, "scale" : 295828764}, {"level" : 2, "resolution" : 39135.75847500000236323103, "scale" : 147914382}, {"level" : 3, "resolution" : 19567.87923750000118161552, "scale" : 73957191}, {"level" : 4, "resolution" : 9783.93961875000059080776, "scale" : 36978595}, {"level" : 5, "resolution" : 4891.96980937500029540388, "scale" : 18489298}, {"level" : 6, "resolution" : 2445.98490468750014770194, "scale" : 9244649}, {"level" : 7, "resolution" : 1222.99245234375007385097, "scale" : 4622324}, {"level" : 8, "resolution" : 611.49622617187503692548, "scale" : 2311162}, {"level" : 9, "resolution" : 305.74811308593751846274, "scale" : 1155581}, {"level" : 10, "resolution" : 152.87405654296875923137, "scale" : 577791}, {"level" : 11, "resolution" : 76.43702827148437961569, "scale" : 288895}, {"level" : 12, "resolution" : 38.21851413574218980784, "scale" : 144448}, {"level" : 13, "resolution" : 19.10925706787109490392, "scale" : 72224}, {"level" : 14, "resolution" : 9.55462853393554745196, "scale" : 36112}, {"level" : 15, "resolution" : 4.77731426696777372598, "scale" : 18056}, {"level" : 16, "resolution" : 2.38865713348388686299, "scale" : 9028}, {"level" : 17, "resolution" : 1.19432856674194343150, "scale" : 4514}, {"level" : 18, "resolution" : 0.59716428337097171575, "scale" : 2257}, {"level" : 19, "resolution" : 0.29858214168548585787, "scale" : 1128} ] }); this.loaded = true; this.onLoad(this); }, getTileUrl: function(level, col, row) { return "http://mesonet.agron.iastate.edu/cache/tile.py/1.0.0/nexrad-n0q-900913/" + level +"/" + row.toString() +"/" + col.toString() +".png?"; } }); }

‎09-23-2011

Using the WMTSLayer introduced at v2.4 to access tiles from Iowa Mesonet, tiles are appearing in the incorrect order. The testing configuration is shown below. I have reversed the sign for the y-origin of the tileset in the test page. The tileset info from the provider has the y-origin as y="-20037508.340000". When the negative value is used for the y-origin in the map configuration, tiles are returned only for Level 0. Zooming in on the test page shows tiles offset down and to the left. A test page is available at: http://geologic.dyndns.org/new_nexrad2.html function init() { var map = new esri.Map("map"); var startExtent = new esri.geometry.Extent({"xmin":-20037508.340000,"ymin": -20037508.340000, "xmax":20037508.340000,"ymax": 20037508.340000,"spatialReference": new esri.SpatialReference({"wkid":900913})}); map.setExtent(startExtent); var tileInfo = new esri.layers.TileInfo({ "height" : 256, "width" : 256, "dpi" : "90.71428571427429", "format" : "image/png", "compressionQuality" : 0, "origin" : { "x" : -20037508.340000, "y" : 20037508.340000 }, "spatialReference" : new esri.SpatialReference ({ "wkid" : 900913 }), "lods" : [ {"level": "0", "resolution" : 156543.033928, "scale" : 559082263.9508}, {"level": "1", "resolution" : 78271.51695000000472646207, "scale" : 279541131.9754}, {"level": "2", "resolution" : 39135.75847500000236323103, "scale" : 139770565.9877}, {"level": "3", "resolution" : 19567.87923750000118161552, "scale" : 69885282.9939}, {"level": "4", "resolution" : 9783.93961875000059080776, "scale" : 34942641.4969}, {"level": "5", "resolution" : 4891.96980937500029540388, "scale" : 17471320.7485}, {"level": "6", "resolution" : 2445.98490468750014770194, "scale" : 8735660.3742}, {"level": "7", "resolution" : 1222.99245234375007385097, "scale" : 4367830.1871}, {"level": "8", "resolution" : 611.49622617187503692548, "scale" : 2183915.0936}, {"level": "9", "resolution" : 305.74811308593751846274, "scale" : 1091957.5468}, {"level": "10", "resolution" : 152.87405654296875923137, "scale" : 545978.7734}, {"level": "11", "resolution" : 76.43702827148437961569, "scale" : 272989.3867}, {"level": "12", "resolution" : 38.21851413574218980784, "scale" : 136494.6933}, {"level": "13", "resolution" : 19.10925706787109490392, "scale" : 68247.3467}, {"level": "14", "resolution" : 9.55462853393554745196, "scale" : 34123.6733}, {"level": "15", "resolution" : 4.77731426696777372598, "scale" : 17061.8367}, {"level": "16", "resolution" : 2.38865713348388686299, "scale" : 8530.9183}, {"level": "17", "resolution" : 1.19432856674194343150, "scale" : 4265.4592}, {"level": "18", "resolution" : 0.59716428337097171575, "scale" : 2132.7296}, {"level": "19", "resolution" : 0.29858214168548585787, "scale" : 1066.3648} ] }); var tileExtent = new esri.geometry.Extent(-20037508.340000,-20037508.340000,20037508.340000,20037508.340000, new esri.SpatialReference({wkid: 900913})); var layerInfo = new esri.layers.WMTSLayerInfo({ tileInfo: tileInfo, fullExtent: tileExtent, initialExtent: tileExtent, identifier: "nexrad-n0q-900913", tileMatrixSet: "", format: "png", style: "" }); var resourceInfo = { version: "1.0.0", layerInfos: [layerInfo], copyright: "Mesonet" }; var options = { resourceInfo: resourceInfo, layerInfo: layerInfo, visible:true }; var wmtsLayer = new esri.layers.WMTSLayer("http://mesonet.agron.iastate.edu/cache/tile.py/1.0.0/", options); map.addLayer(wmtsLayer); } dojo.addOnLoad(init); Tileset information is available from Iowa Mesonet at: (http://mesonet.agron.iastate.edu/cache/tile.py/1.0.0/nexrad-n0q-900913/) Additional information about the Iowa Mesonet service is available at: http://mesonet.agron.iastate.edu/ogc/

‎09-12-2011

I had the same issue with the OpacitySlider after upgrading to v2.4 of the JavaScript API. Firefox was not affected. I believe it started with the 2.3 release. Adding a meta tag to the html code which specified IE-7 content for the page restored the expected behavior of the OpacitySlider. So far I have not seen any side effects. I believe it is necessary to place the meta tag above the doctype declaration. <meta http-equiv="x-ua-compatible" content="IE=7"> <!doctype html>

‎09-12-2011

I believe you need to use the innerHTML property to retrieve the value of the elements you are accessing. Change var myLat = document.getElementById("siteLat"); var myLong = document.getElementById("siteLong"); To var myLat = document.getElementById("siteLat").innerHTML; var myLong = document.getElementById("siteLong").innerHTML;

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by bobcarr

Re: How to resize infoWindow automatically based on the content?

Re: Help with ContentPane - AMD

Help with ContentPane - AMD

Re: ArcGISDynamicMapServiceLayer: option for visible layers?

Re: Tooltip Connector Placement - dijit.tooltipDialog

Re: Tooltip Connector Placement - dijit.tooltipDialog

Tooltip Connector Placement - dijit.tooltipDialog

Re: Info Window - Version 3.4 of the JavaScript API

Info Window - Version 3.4 of the JavaScript API

Re: 3.1 FeatureLayer bug?

Re: WMTS tiles images in wrong order

Re: WMTS tiles images in wrong order

Re: DynamicLayer.setOpacity seems to have a little issue in Internet Explorer 8.0

Re: How to fetch the lat/long values from a table in an HTML page