Latest Contributions by derekswingley1

We might have a problem with how we're serializing your parameters. Try using JSON.stringify to convert your values for analysisLayer and nearLayer to strings. Something like: var _params = {   "analysisLayer": JSON.stringify({     "layerDefinition": {       "geometryType": "esriGeometryPoint",       "fields": [{         "name": "Id",         "type": "esriFieldTypeOID",         "alias": "Id"       }]     },     "featureSet": {       "geometryType": "esriGeometryPoint",       "spatialReference": {         "wkid": 4326       },       "features": [{         "geometry": {           "x": -95.00,           "y": 28.00         },         "attributes": {           "Id": 1         }       }]     }   }),   "nearLayer": JSON.stringify({     "layerDefinition": {       "geometryType": "esriGeometryPoint",       "fields": [{         "name": "Id",         "type": "esriFieldTypeOID",         "alias": "Id"       }]     },     "featureSet": {       "geometryType": "esriGeometryPoint",       "spatialReference": {         "wkid": 4326       },       "features": [{         "geometry": {           "x": -94.00,           "y": 28.00         },         "attributes": {           "Id": 1         }       }]     }   }),   "maxCount": 10,   "measurementType": "StraightLine",   //"searchCutoff": 44,   //"searchCutoffUnits": "Kilometers"   "f": "json" } ... View more

The REST API docs has a little more info:  http://resources.arcgis.com/en/help/arcgis-rest-api/index.html# Unfortunately, the link to ITopologicalOperator.Simplify Method gives a 403. I think it's supposed to link here:  http://resources.arcgis.com/en/help/arcobjects-cpp/componenthelp/index.html#//000w000003w0000000 The relevant stuff is in the description section: For Points, Simplify does nothing. A point has no constraints on the values of its coordinates. For Multipoints, Simplify snaps all X, Y, Z, and M coordinates to the grid of the associated spatial reference, then removes identical points. A point is identical to another point when the two have identical X and Y coordinates (after snapping), and when attributes for which it is aware are identical to the attributes for which the other point is aware. For example, if both points are Z aware, the Z coordinate values must be identical. For Polylines, Simplify has two variations: planar and non-planar. By default, polylines that are not M-aware are simplified in a planar manner: all overlapping segments are reduced to a single segment, and segments are split at intersection points. Output paths are created for connected sequences of segments. Input segment orientation is preserved where possible, but segments in the interior of a path will be reoriented if necessary. Polylines that are M-aware use non-planar simplification: 1. Overlaps and self-intersections are preserved, but zero length segments are removed, 2. Segment orientations are adjusted so that the 'to' point of segment I is identical to (considering vertex attributes) the 'from' point of Segment I+1, 3. New paths are created where segments are not connected, 4. Existing paths are merged where only two of them meet at a segment endpoint. For Polygons, Simplify identifies an interior and exterior for the polygon, then modifies the polygon structure to be consistent with that determination. The default methodology for identifying interior and exterior is: 1. Remove all dangling sequences of segments, 2. Identify the largest legal rings, add them to the output version of the polygon, then delete them from the working version, 3. Repeat. If this approach ends up removing too many segments for your application, consider using IPolygon4::SimplifyEx with the XOR parameter set to TRUE. At the end of Simplify, no rings will overlap, no self intersection will occur (except in certain circumstances) and, in general, an arbitrary point can always be classified unambiguously as either outside, on the boundary of, or inside the polygon. ... View more

Having analyzed the issue, I tend to agree. I've done an envelope around the complex geometry (A LOT of point) to simplify the geometry (to reduce the point count) and it's working well. Any other ideas on the issue? How are you retrieving your geometry? Feature layer? Query task? Feature layers, by default use maxAllowableOffset to request generalized geometries (see the "feature generalization" section). If you're using a query task, you can manually set the maxAllowableOffset on your instance of query according to the info in the aforelinked article. The one semi-common place where this breaks down is when you request a very large feature (for instance, Canada's national boundary) but are at a large scale. The geometry that comes back will be huge and cover the entire map and can potentially slow down older browsers (including IE9). ... View more

Check out "The abc???s of AMD" blog post from last fall. Another tool to be aware of is Sitepen's dojo-amd-converter. I haven't actually used it??? it came out about a month after we finished converting all JS API modules to AMD. ... View more