Latest Contributions by BenFousek

Welcome to the forum pavan.adiga. A couple of things: 1) Dojo and the jsapi have moved to AMD style coding. In the interest of creating better apps and getting help here, you should switch as soon as possible. 2) Please wrap your code in code tags. Select your code and click the code button (# sign). 3) You identified the problem as inside your init function, but you didn't post it. 4) insertBefore is very general. This is a javascript method and a method found throughout the dojo (and jsapi) framework. Something in your code is trying to insert a dom node in a parent node doesn't exist. Identifying your issue is going to require posting more code. Hope this helps. ... View more

Thanks Roberto. That works. It's just curious that all other symbol types and their respective set methods work in that manner but these two don't. ... View more

Why is the layerName empty when you do an identify on a raster layer??  The layerId is populated correctly. Not 100% sure about this, but...I think it's because AGS is generating and returning a point independent of the raster for the result, unlike an identify on a point layer, which is returning an actual point. displayField is empty because it doesn't exist in a raster. layerName is empty because the point doesn't belong to the dataset so to speak. The layerId is populated simply to identify which layer the return point was generated from. The REST API could probably be enhanced to include layerName, but from my standpoint it's unnecessary. ... View more

The hatch patterns cannot be altered via the api because they are images. Only STYLE_SOLID will use the color provided. STYLE_SOLID and STYLE_NULL are the only "pure" esri/symbol/SimpleFillSymbol(s). All the other fill options like STYLE_BACKWARD_DIAGONAL, are actually esri/symbol/PictureFillSymbol(s), which use images that are included in the api http://js.arcgis.com/3.7/js/esri/images/symbol/sfs/vertical.png. The solution, work-around or what have you is to use esri/symbol/PictureFillSymbol with your own custom images. ... View more

Despite the map being display:none on load, set the map's width and height with css. Create the map with your init function, but don't add layers. Then use whatever function you're using to set the map's display to block to add the layers and graphics after the map's display has been changed. ... View more

Sure: var connects = []; function reset() {   dojo.forEach(connects, dojo.disconnect);   connects = []; }; //elsewhere reset(); var mapClick = dojo.connect(map, 'onClick', function(evt) {   dojo.disconnect(mapClick);     //do stuff }); connects.push(mapClick); And not to push AMD on you, but it's the way to go. 😉 ... View more

Create the map as you were and add the graphics after the map's display has been changed. ... View more

In general a map dislikes being hidden/display:none when loaded. One solution might be to load the map when the target dom node becomes visible. If your intent is some kind of loading screen you can use dojo/dom-construct destroy() to 'kill' the loading screen. This is what I use for full-page apps. [HTML]<!-- really doesn't matter where this goes: after opening body tag or right before closing body tag --> <div id="loading" style="position:absolute;top:0;right:0;bottom:0;left:0;z-index:9999;background:#FFF;">   <h1>Hold on a second...</h1>   <h2>your map is loading.</h2> </div>[/HTML] //at the end of the loading script //a short timeout just to give basemap tiles a couple seconds to finish loading setTimeout(function() {   domConstruct.destroy('loading'); }, 2000); I'm not sure if the Problem parsing d="Z" (in svg.js:64) has to do with the map being hidden initially or not. Based on the svg.js and the post you linked, I'd say this is being cased by a feature layer or graphics layer. I can see where loading a feature layer, and while the requests are in progress, the map's visibility or width/height changes might cause an rendering error. Are you loading a feature layer or adding graphics as part of you loading script, prior to and along with the map resize? If none of the above, share a little more on why the map div is hidden on load or the app's loading progression (map creation, layers added, etc). ... View more

The map on the client is a rectangle with dimensions in pixels. Most of the time as developers, and certainly for users, we think in terms of the coordinate system and its units, however in regard to displaying layers, graphics, info window, etc in the map, the api thinks in terms of pixels. So what we end with is a grid in pixels (integers) say 600 x 400 representing thousands, if not millions of map units, which are not integers. The values the api uses (10 -11 ) in web mercator and as shown in your fiddle are less than a nanometer. When the api creates a map, the spatial reference of the map is set by the first layer added to the map, unless otherwise specified. And if it's a tiled layer the map sets its levels of detail (LODS) based on the layer's LODS, unless otherwise specified. So when using the basemap option when creating the map, the map is set to web mercator and the standard web map LODS. When the map's LODS are set, the map will only use those specific LODS. Here's 2 standard web mercator LODS: { level: 14, resolution: 9.55462853563415, scale: 36111.909643 }, { level: 15, resolution: 4.77731426794937, scale: 18055.954822 } With the map's LODS set, any action which changes the extent will use the LODS to the nearest available scale: map.setScale(18000); console.log(map.getScale()); //returns 18055.954822 map.setScale(27082); console.log(map.getScale()); //returns 18055.954822 map.setScale(27084); console.log(map.getScale()); //returns 36111.909643 For level 14 we have a scale, for which an inch measured on the screen, theoretically represents 36111.909643 inches on the ground, just like a paper map. The resolution represents the number of meters per pixel. Here we have 14 decimal places, which is important when representing the projected data in our pixel grid. If we have 2 point graphics of a feature layer, and the map scale is 36111.909643, unless the points are more that 9.55462853563415 meters apart in both x and y coordinates, they will have the same x,y screen point. As you know using extent.expand() expands the extent by the factor provided. The map.setExtent method takes an extent as it's first argument and a boolean as an optional second argument telling the api whether or not to fit the extent in the map. The fit option really only comes into play when the map's LODS are set. If the LODS are not set, the resulting map extent will fit the extent in x or y, whichever is larger in the extent in map units. When expanding the map's extent in this case, no matter what the expand factor is or the map's dimensions in pixels, the resulting map extent and the extent should be the same. Although I suspect you may find some small differences beyond 4 or 5 decimal places none the less.  When the LODS are set, as shown above, the map is confined to the nearest scale. This is where the fit option comes into play. If set to true, and the nearest scale doesn't fit the extent in either the x or y, the map goes to the next LOD. In a web mercator map with standards LODS: if your map was square (400x400 pixels) and you expand by integers you should end up with a map extent which pretty closely matches the extent you set. ... View more

If you're initiating identify with map onClick you can use dojo/on once. on.once(map, 'click', function(evt) {   //do stuff }); To manage the event outside itself. var clickTheMap = on(map, 'click', function(evt) {   //remove event when fired (equivalent to on.once)   clickTheMap.remove();   clickTheMap = null;   //do stuff }); on(myCancelButton, 'click', function() {   if(clickTheMap) {     clickTheMap.remove();   } }); If you have a lot of map events consider a helper class to manage said events. Here's the relevant parts of mine. Keep in mind I just copy/pasted this as an example to illustrate to concept. Will probably take some adaptation to implement in your app. /* map event handling */ // primarily used for map 'click' events // however any on-style event can be added // does not support connect events eventAdd: function (event) {   this.eventOns.push(event); }, eventBegin: function () {   this.infoWindow.hide();   this.infoWindow.clearFeatures();   this.setMapCursor('default');   this.eventMouseEventsDisable();   arrayUtils.forEach(this.eventOns, function (o) {     o.remove();   });   this.eventOns = [];   if (this.drawToolbar._geometryType != null) {     this.drawToolbar.deactivate();   }   var s = esriBundle.toolbars.draw;   s.addPoint = 'Click to add a point';   s.freehand = 'Press down to start and let go to finish';   s.start = 'Click to start drawing';   s.resume = 'Click to continue drawing';   s.complete = 'Double-click to finish'; }, eventEnd: function () {   this.setMapCursor('default');   this.eventMouseEventsEnable();   this.toaster.hide(); }, eventReset: function () {   this.eventBegin();   this.eventEnd(); }, eventMouseEventsEnable: function () {   arrayUtils.forEach(this.graphicsLayerIds, function (layer) {     this.getLayer(layer).enableMouseEvents();   }, this); }, eventMouseEventsDisable: function () {   arrayUtils.forEach(this.graphicsLayerIds, function (layer) {     this.getLayer(layer).disableMouseEvents();   }, this); }, Used like this. this.map.eventBegin(); this.map.setMapCursor('crosshair'); this.map.drawToolbar.activate('point'); var o = on.once(this.map.drawToolbar, 'draw-end', lang.hitch(this, function (result) {   this.map.eventEnd();   //do stuff })); this.map.eventAdd(o); ... View more