Latest Contributions by ThomasSolow

In the 3.20 API I think you would access the map after the promise from arcgisUtils.createMap resolves, like this: JS Bin - Collaborative JavaScript Debugging  That example shows how you could access the layer as well, assuming you only have one layer.  If you want to edit the popup for that layer, you should play around with the infoTemplate property on the layer.  For more on how to add a graph instead of the attribute table, take a look here: Format info window content | Guide | ArcGIS API for JavaScript 3.20 Also, here: Customize popup | Guide | ArcGIS API for JavaScript 3.20  ... View more

As far as I know, there isn't any way to generate a polygon or extent from a point and an angle. ... View more

There's no reason you can't do this in the client. I would check out esri/graphicsUtils | API Reference | ArcGIS API for JavaScript 3.20  The graphicsExtent method will take an array of Graphics (features) and return an extent.  What you need to do is find out where your graphics are getting stored in the client. ... View more

It looks like setting graphic.visible works in 3D but not in 2D (4.3). For 2D, you should try deleting the graphic manually from the featuresView.graphics collection.  You can do this with  featuresView.graphics.remove(graphic) or  featuresView.graphics.removeMany([graphic1, graphic2,..]). If you plan on re-adding these later, you'll have to store them somewhere and re-add them to the layerView graphics collection later (use collection.add and .addMany). With this kind of functionality you're getting into GraphicsLayer-type stuff, so you might want to think about using a GraphicsLayer instead, as you initially mentioned.  I would say the main advantages of a FeatureLayer is that it has some built-in querying and has some nice methods to help you persist the layer on a back-end.  If you're not using these, then a GraphicsLayer may be better. ... View more

The queryFeatures method might be what you're looking for: FeatureLayer | API Reference | ArcGIS API for JavaScript 4.3  For client-side queries, you would call this on the layerView rather than on the layer itself.  To get ahold of the layerView, you can do something like: view.whenLayerView(layer).then(layerView => ...).  You could also search the view.layerViews collection for the item whose .layer property matches the layer you're looking for. In general, you can think of the layerView as the visual representation of the layer in question.  Each layer, once added to the map, has a corresponding layerView on the view. Last time I checked, layerView.queryFeatures is fairly limited in what kinds of spatial queries it supports.  I think it only supports extent geometries and the "intersects" spatial relationship.  You should be able to query by attributes though. If you prefer to write your own spatial queries, you have some options.  To access a list of all graphics loaded inside a layerView on the client, you can look in: layerView.featuresView.graphics (2D) or layerView.loadedGraphics (3D).  These will be collections (Collection | API Reference | ArcGIS API for JavaScript 4.3) which are basically evented arrays (you can convert them to arrays with collection.toArray()).  To do the actual spatial queries, the geometryEngine has a lot of helpful methods: geometryEngine | API Reference | ArcGIS API for JavaScript 4.3. As far as GraphicsLayer vs. FeatureLayer, I would consider using a GraphicsLayer if you want your layer to have features with different geometries and you're not concerned about persisting the layer on a back-end. ... View more

It should work if you host the image locally rather than getting it from another domain. Another possible workaround would be to encode the image in base64 and use a dataURI instead of a URL.  Using this, your url parameter would look something like: "data:image/svg+xml;base64,<svg xml string in base64 encoding>".  For a jpeg, it would look like: "data:image/jpeg;base64,<jpeg binary encoded in base64>". Note: due to another issue (possibly another bug) you can't have uft8 encoded svgs on 3D maps. You can encode strings in the browser with btoa or check google, I'm sure there's plenty of websites that will allow you to upload an image and give you back a base64 string. ... View more

I don't see any direct mention of WFS in the JS API issues, so all I know is "coming soon." ... View more

This appears to be a bug in the JS API.  Glancing at the API issues, this has been reported. I think the culprit is esriRequest, which is being used to fetch the image data. ... View more

I don't know the best way to do this in 3.XX, however the 4.XX API has a a symbolPreview module (esri/symbols/support/symbolPreview) with a renderPreviewHTML function, for example: symbolPreview.renderPreviewHTML(<symbol>,{       node: <HTMLElement>, //svg will be a child of this node       opacity: 1,       size: 10 }); This will resolve to an HTMLElement containing the SVG, so you can add it manually if you prefer instead of providing a node. ... View more

According to the functionality matrix, WMS and WFS are "coming soon."  WMS looks like it's slotted for 4.4, the next 4.XX release, which should land in a couple months.  I would treat that as an estimate, though. ... View more

Are you working 2D or 3D?  HitTest has some limitations in 3D and will not return graphics that are draped on the surface of the earth.  For this situation I've found that a spatial query, like Kelly mentioned, is your best bet. For 2D, I think the best option would be to perform a normal hitTest and then filter the results down to only graphics from layer(s) you're interested in.  Each returned graphic has a .layer property which you can compare to the layer(s) you're interested in. I'm surprised to hear that hitTest is giving you performance issues, my understanding is that hitTest doesn't do a spatial query, rather it just checks intersection between the user's click (a point on the screen) and the graphics in the view.  So it should be fast.  If you're running into speed issues you may have identified a bug. Additionally, you can perform a hitTest on a layerView for the specific layer you're interested in only.  Here's a JSbin demonstrating this: JS Bin - Collaborative JavaScript Debugging  Note: that works for 2D layerViews only and is not mentioned in the documentation. ... View more

You're welcome, glad I could be of help. ... View more