Latest Contributions by ThomasSolow

Which version of IE and Firefox?  I've used 4.4 and now 4.5 with firefox semi-regularly and it seems to work fine. If there's a particular thing that won't work could you post a sample? ... View more

The documentation for IdentifyTask in the 4.X SDK says: IdentifyTask is not supported if attempting to be used: in a 3D SceneView with dynamic layers That said, the JS API only provides a wrapper around the REST API here.  The real functionality to handle this stuff is on the server so there's no reason you can't write your own function to make an identify request (probably using esri/Request) which includes dynamicLayers.  The REST API documentation should be useful if you decide to do this. ... View more

It looks to me like the error is in the feature service.  If I go to the service page: Layer: All Offsite Locations (ID: 😎  scroll down to the bottom, query all features, I get this response: https://fmags.fm.utah.edu/arcgis/rest/services/mapservices/network_offsite_locations/MapServer/8/query?where=1%3D1&text=…  on that page, control-f and search for "nan" It seems that one of the features that has an invalid geometry, which the JS API is not handling correctly. I'm a little surprised in how the JS API handles this, it actually seems to render the invalid geometry in the upper lefthand corner of the view.  Regardless, I think if you fix the service this problem will go away. ... View more

You shouldn't need to set the spatialReference here. One issue is that in your example, the opacity of the symbol is 0, so you won't be able to see it.  The 4th element in the arrays you're passing in as colors decide opacity, try setting them to something else, like this: https://codepen.io/solowt/pen/qPPeye?editors=1000  In that example I'm still seeing an error.  I'll see if I can figure out what's going on. ... View more

Another workaround that seems to work is setting the layer's opacity to 1.0 but using a renderer to specify a symbol with opacity less than 1.0.  This doesn't seem to interfere with hitTest: https://codepen.io/solowt/pen/PJJLrw?editors=1000#0  I reported the issue and I'll post here if I learn when it's going to be fixed. ... View more

I'm not sure. You could use something like this for the time being: // evt: ClickEvent, view: MapView function getFeatures(evt, view){   const pxRatio = view.extent.width / view.width,         // number of pixels to check in         pixelBuffer = 6,         halfExtent = pxRatio * pixelBuffer,         clickExtent = new Extent({           xmin: evt.mapPoint.x - halfExtent,           xmax: evt.mapPoint.x + halfExtent,           ymin: evt.mapPoint.y - halfExtent,           ymax: evt.mapPoint.y + halfExtent,           spatialReference: view.extent.spatialReference         });                 let queries = view.layerViews.map(lv => {     let q = lv.layer.createQuery();                 q.geometry = clickExtent;     q.geometryType = "esriGeometryEnvelope";     q.outFields = null;     q.where = null;     return lv.queryFeatures(q);   }).toArray();             return Promise.all(queries).then(results => {     return [].concat.apply([], results);   }); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ example: JS Bin - Collaborative JavaScript Debugging  This won't work as well as hitTest.  If you rely on this, it may be better to stick with 4.4 for the time being. ... View more

Yeah, looks like a bug to me.  Seems that anything less than 1.0 opacity doesn't work with hitTest in a MapView. ... View more

As far as I know there shouldn't be any difference between windows or linux when it comes to this sort of thing.  I believe you can pull in the API using dojo.js or init.js, though init.js seems like the better choice. ... View more

Here's another sample showing how you might do this with d3 and a simple renderer: JS Bin - Collaborative JavaScript Debugging  ... View more

It's been a little while since I looked at d3.  Is a d3 object an SVG?  You can use a Picture Marker Symbol whose URL points to an SVG, you aren't just limited to passing in a path.  For example (click the map to add a graphic whose symbol is taken from an SVG): JS Bin - Collaborative JavaScript Debugging  The easiest way to do this sort of thing with a feature layer is to make your own SimpleRenderer and override the getSymbol method.  getSymbol takes a graphic as an argument and should return a symbol.  You can use d3 to create an SVG and then create a PictureMarkerSymbol from that SVG inside getSymbol. ... View more

I don't think there's anything wrong with your tiling scheme as it seems to work fine for your basemap and for elevation that isn't exaggerated.  I think the problem is definitely in the source code: BaseElevationLayer makes some assumptions about which kind of elevation layer it's modifying. I'd try something like this: load: function() {   this._elevation = new ElevationLayer({     spatialReference: tileInfo.spatialReference,     tileInfo: tileInfo,     fullExtent: fullExtent,     url: "http://rips-rasterdaten.lubw.bwl.de/arcgis/rest/services/Imageservices/DGM025_cache_3D/ImageServer"   });   this.addResolvingPromise(this._elevation.load()); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... elevLayer.on("layerview-create", function(event){   tileInfo = event.target.tileInfo;   fullExtent = event.target.fullExtent;   var secondElevLyr = new ExaggeratedElevationLayer({     tileInfo: tileInfo,     fullExtent: fullExtent,     spatialReference: tileInfo.spatialReference   });   map.ground.layers.add(secondElevLyr); }.bind(this));‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Setting tileInfo in the constructors might fix things, and it may be necessary to take full extent from the tiled service as well.  My feeling is that the layer is getting into a state where some properties are set for web mercator (due to that being hardcoded) and some are set for 31463. In principle this should definitely be doable.  The normal elevation layer is working, all we're really doing is using the normal layer and tweaking the values a bit. ... View more

Please post a sample or provide steps to reproduce.  My current understanding is that this bug will only occur when the layer loads, the layerView loads, but then the layer's controller fails to load.  So this shouldn't be an issue if the layer itself doesn't load. ... View more

Yes, you'll need to use .project to convert non-WGS84/Web Mercator geometries to WGS84 or Web Mercator if you're using an esri basemap. This will have a significant impact on performance as project is behind an HTTP request. Depending on your use case this might be a concern or not. If you're adding a static number of graphics to the view/a layer as part of your app then you could just project them all ahead of time and add the graphics with their projected geometries.  If users need the ability to add new graphics in your preferred spatial reference at run time, then you'll have to project them using the geometry service in order to add them. ... View more

Additionally, you can use GeometryService.project in order to go from your spatial reference of choice to Web Mercator or WGS84.  This sends an HTTP request to an Esri geometry service, so it's not done in the client. ... View more