Latest Contributions by ThomasSolow

Both of your geometries are valid as far as the JS API is concerned.  I was able to create graphics from each one and add it to a map. I would take a look at server logs to get a more complete picture of what's going wrong here. ... View more

I'm not sure what's wrong here, but here's a simple sample that creates a feature layer in the client from an array of randomly generated graphics and symbolizes them with symbols that have callouts: https://codepen.io/solowt/pen/LOadjd?editors=1000#0  One thing to take a look at is verticalOffset.  If you're zoomed out and have a maxWorldLength of 200, it's quite possible you won't be able to notice the callouts.  It may be better to just use screenLength sometimes. ... View more

I've successfully used callouts with client-side graphics. Can you post a simple code sample? ... View more

The cursor is set from CSS. So setting the view container's style.cursor attribute to "wait" will do this. ie: var el; // the element containing your map (3.X) or view (4.X) el.style.cursor = "wait";‍‍ In the 4.X API, you should be able to get a reference to the surface element using view.surface.  From here, you can set the "data-cursor" attribute to change the cursor: view.surface.setAttribute("data-cursor", "wait"); // set to wait view.surface.setAttribute("data-cursor", "default"); // back to default‍‍‍ ... View more

Setting outSpatialReference somewhere might help you if you're trying to query a Feature Service. Another option is to pull in webMercatorUtils from esri/geometry/support/webMercatorUtils and use that module to convert between Web Mercator and WGS84 Latitude/Longitude. webMercatorUtils | API Reference | ArcGIS API for JavaScript 4.5  I would specifically look at the "webMercatorToGeographic" function, which will convert a geometry from Web Mercator to WGS84 longitude/latitude. ... View more

Robert's answer is a good client-side method. Another option is to do this on the backend with an IdentifyTask: IdentifyTask | API Reference | ArcGIS API for JavaScript 4.5 or just by querying a feature service with some geometry (a circle maybe). These are only possible if your data is contained in a feature service/map service. ... View more

This is definitely possible, though you may not be able to use layer events, I'm not sure. The approach I would take is to make sure both of your layers have a fullExtent set on them.  This property is part of the feature service. If this is set, you can set this up manually pretty easily, ie: on mouse move, check for intersection with neither, both, or one of the fullExtents on your data sets and then highlight them accordingly and fill in information in the side popup. In terms of merging two extents, you can do this using the geometry engine union function in order to merge two polygons or two extents however you like (I would guess two extents should normally be merged into a polygon, unless one totally contains the other). Here's simple example showing how to test for intersection with a feature layer's fullExtent on mouse-move and draw the fullExtent if the mouse is inside.   JS Bin - Collaborative JavaScript Debugging  It should be pretty simple to extend this so it works on however many layers you need and it merges the extents of all layers being intersected using geometryEngine.union. In terms of how you handle the side popup, I don't really know what that would involve, whether there's a pre-existing tool you're using or if it's something you've built yourselves. ... View more

I'm pretty clueless on what could be causing this. It seems to me that it's probably a JS API/client-side issue.  If I understand correctly, the problem is that your attributes are not being posted to the feature service at all, which suggests they're being stripped before your request is sent. One approach to figuring this out might be to manually send an applyEdits request without using esri/request.  The REST API documentation  describes how you can do this: ArcGIS REST API.  If you can successfully send an applyEdits request using XMLHTTPRequest/http library of your choice, then we can pretty sure this is an issue with the JS API. It's strange that this is an issue in your production environment but not during development.  Obvious things to check might be browser versions and using the same webserver to host your app in both environments, little things like that. ... View more

Which version of the API are you using and which coordinate system are you interested in seeing coordinates in?  I can provide a sample for this if I know the details. ... View more

view.on(...) returns a handle.  The handle has a remove method, which will remove the listener. so you could do something like: var handle = view.on("drag", ...); and then call handle.remove() when you're done with the listener. ... View more

If you can replicate the issue you're running into in a sample I'd be happy to to take a look at it and see if I can help. I'm not sure where to begin though.  I assume you're asking for a sample of this, from the docs: Pick a local origin position, approximately at the center of your data. Subtract the local origin position from all positional data (vertex data, uniforms, etc.) before passing it into WebGL. Also subtract the local origin from the translational part of the view transformation matrix. My feeling is that the first two bullets are fairly straightforward: pick a point at roughly the center of your data, transform it into rende coordinates, and subtract it from every vertex that you plan to use to create Three.js geometries. I'm not completely sure about the third bullet, but I guess that you're meant to subtract your local origin, in render coordinates, from elements 13, 14, and 15 (ie the last three elements) in the view transformation matrix, which is the output of externalRenderers.renderCoordinateTransformAt. ... View more