Latest Contributions by HeathClark

‎01-16-2024

@TanuHoque - As this issue has been outstanding for over 10 years... is there a definitive schedule to get this bug fixed?

‎10-22-2020

Does the current SDK for iOS support Swift Package Manager? If not, when will that support be included?

‎06-12-2014

If you place different geometry types into the BufferParameters.geometries array and try to generate buffers the endpoint will crash with an error: {"error":{"code":400,"message":"Unable to complete operation.","details":["Syntax error in JSON geometry representation"]}} Sample of the JSON created and passed to the endpoint based on a geometries array of one point and one simple polygon: {"geometryType":"esriGeometryPoint","geometries":[{"x":-12427133.174075715,"y":4914218.049149509,"spatialReference":{"wkid":102100,"latestWkid":3857}},{"rings":[[[-12427133.533385498,4914218.287572771],[-12427130.686178004,4914216.83072361],[-12427132.68162872,4914212.900465214],[-12427135.178522844,4914214.178059309],[-12427135.528835386,4914214.357313236],[-12427133.533385498,4914218.287572771]],[[-12427131.223425483,4914216.655518652],[-12427133.358863894,4914217.74822116],[-12427134.991457105,4914214.532518585],[-12427132.856019203,4914213.439816782],[-12427131.223425483,4914216.655518652]]],"spatialReference":{"wkid":102100,"latestWkid":3857}}]} The obvious problem is in the geometryType declaration. Is this intended behavior? Nothing in the documentation states that you can't mix geometry types in the BufferParameters.geometries array.

‎06-12-2014

in short, read the documentation! Can't believe I missed that one.

‎06-12-2014

I keep getting a error when trying to buffer geometries using the 3.9compact build. The error is: TypeError: h.join is not a function in the http://js.arcgis.com/3.9compact/js/esri/tasks/BufferParameters.js file. Sample Code: function BufferPoint(evt) { var params = new esri.tasks.BufferParameters(); params.distances = BufferDistance; //params.inSpatialReference = new esri.SpatialReference({ wkid: '102100' }); params.bufferSpatialReference = new esri.SpatialReference({ wkid: '102100' }); params.outSpatialReference = new esri.SpatialReference({ wkid: '102100' }); params.unit = BufferUnits; params.unionResults = true; params.geometries = [evt.mapPoint]; console.log('0' + ": feature's geometry: " + params.geometries[0].type); var GeoService = new esri.tasks.GeometryService('[server]/arcgis/rest/services/Utilities/Geometry/GeometryServer'); GeoService.buffer(params, bufferResults); }; Where the BufferPointmethod is linked to an OnClick event. The console log shows 0: feature's geometry: point Any ideas?

‎11-25-2013

+1 to this. I had to rename the .container class in Bootstrap, which I'm sure will bite me when they update Bootstrap and I forget about it 😉 For what its worth: I just added [HTML]#map_div_container, #map_div_root { max-width:10000000px; }[/HTML] to my template/default .css file. Simple solution without messing with Bootstrap. dh

‎11-06-2013

While there may be other cases, the use of the class 'container' in such a generic form is causing conflicts when trying to incorporate Bootstrap styling into an ESRI map based site. ex. within a map-display / map class : <div id="map_div_root" class="container".....<div id="map_div_container" class="container">.. the generic use of "container" generates a side effect of a max-width of the map being set by Bootstrap. While this can be overcome with some basic css, would using an esri- prefix within js.api generated objects all but eliminate current and future css conflicts? Some of the more popular "add-ons" are revising their naming conventions to avoid such conflicts (Font Awesome is a great example as they just changed their icon- prefix to fa-). Just an idea/suggestion.

‎10-17-2013

in case you didn't solve this, or for the next person to come across this thread: replace var outSR = new esri.SpatialReference({wkid: 102709}); with var outSR = new esri.SpatialReference(102709); works for me, and I solved another issue I was having by looking at your posted code.

‎04-18-2013

I am overlaying a dynamic service (WKID:3566) on the National Geographic basemap and would like to auto-zoom to the extents of the dynamic service. If the dynamic service was in WGS84 and not State Plane, the esri.geometry.geographicToWebMercator() function would get me the correct extent. However, since the dynamic service is in STP, I need other ideas. Some examples of mixing the traditional "basemaps" with real-world data in local systems (STP) and how to manage Query/Find results whose geometry spatialreference is based on the underlying service (STP) would be helpful and may guide my solution. Maybe it isn't possible, be nice to know before I spend another day hacking code that ultimately doesn't yield a good result.

‎11-18-2011

After discussing with a few other people, the purpose of providing an extent, height, width and dpi is so that the map service can determine the current map scale. Once the scale is known, the map service can exclude layers based on their scale dependency settings. The map service is not doing a spatial intersection based on the extent that's provided to exclude layers from the identify operation. Glad you were able to come up with a solution to get your identify time down to something relatively reasonable. For future reference, when you have hundreds of layers you need to serve, the Esri recommendation is to use multiple map services with the number of layers in a map service to something smaller, say...less than 100. Preferably less than 50. Thanks for "documentation" on what the identifyParameter.mapExtent is really doing. Could that explanation be included in the Class: IdentifyParameters API Reference? What is currently in the documentation is not clear on that point (hence this thread).

‎11-18-2011

Code adjusted to work for me, just not the ESRI way. I dropped the query time from average of 10seconds to less than 2 seconds. I wrote code to dynamically populate the layerIds based on information stored in a database (populated thru the SOAP interface for a custom TOC tool). What I learned, and will presume is correct unless others have input: 1- setting identify.parameters.mapExtent=map.extent DOES NOT limit the identify task to those sublayers within the current extent.

‎11-17-2011

Query time: 34 seconds the first time you run an Identify in a new session. 10-12 seconds thereafter, regardless of x,y clicked on the map. Regardless of the pros/cons of the 800 layer service, I would still like some more details on what the identify.parameters.mapExtent setting is really doing. By the description given it would sound like that process would limit or populate the layerIds to on those visible in the extent.

‎11-17-2011

Am I missing something? If I set the IdentifyParameters.mapExtent wouldn't that limit the bounds of the identify task? Do I also need to explicitly set height/width/dpi properties to limit the task to visible layers in the current extent? identifyparameters.mapExtent descirption reads The values for mapExtent, height, width, and dpi are used to determine the layers visible in the current extent. They are also used to calculate the search distance on the map based on the tolerance in screen pixels. Does that mean layers within the service (specified in the identify.task.url) or layers (Dynamic, Tiled, or otherwise) on the map?

‎11-16-2011

I have a service with almost 800 layers (group layers and data layers) and my identify queries are slow. I was looking for a way to get a list of layers to put into the identify parameters layerIds setting to speed things up. setting identify parameter mapExtent doesn't help either. FYI - I know thats a large number of layers for one service, however, short answer - it's not going to change.

‎11-16-2011

Is there a way to get the layerIds of a Dynamic service that are only within a particular map.extent?

Online Status	Offline
Date Last Visited	‎01-16-2024 08:38 PM

My Ideas

Latest Contributions by HeathClark

Re: Is there a work-around for BUG-000149858 (join name and destination table name contain a percentage symbol after creating a join)?

Swift Package Manager

Buffering in 3.9compact - Mixing input Geometry types

Re: Buffering in 3.9compact

Buffering in 3.9compact

Re: CSS Naming conflicts within API

CSS Naming conflicts within API

Re: Project extent driving me insane

Zoom to Dynamic Service (Projected State Plane) extents overlayed on NatGeo Basemap

Re: Layers in Extent

Re: Layers in Extent

Re: Layers in Extent

Re: Layers in Extent

Re: Layers in Extent

Layers in Extent

Swift Package Manager

Re: Project extent driving me insane