Latest Contributions by JohnGrayson

I would recommend against the use of the interceptor for this use case.  Just make sure you specify the parameters correctly and you can just extend the BaseTileLayer, which will help a lot as you try to use other parameters and options from these services.  Using the interceptor to ignore improperly formatted URL parameters might lead to other issues as you try other settings.  ... View more

...but that doesn't quite give us the final solution as those parameters still have undesired encoding of the '+' sign for spaces.  Here's a code pen showing how to configure the parameters correctly:  https://codepen.io/john-grayson/pen/ExEozep ... View more

I believe the issue is that the color_formula you're trying to use is already encoded.  Using decodeURIComponents produces the following parameter: gamma+RGB+2.7,+saturation+1.5,+sigmoidal+RGB+15+0.55 As shown in the previous example I would recommend you try to configure the base part of the url (before the ? char) and all the parameters separately so you have better control of the URL being requested. ... View more

Not sure if this helps as I'm not familiar enough with this service, but here's an example of how you can extend the BaseTileLayer to access the service and use custom parameters: https://codepen.io/john-grayson/pen/VwXWbjK   ... View more

Correct, the data you're trying to load seems to represent two distinct datasets and the way to configure each one is via the URL parameters and not as part of the base URL, so you will need two different layers.  It always helps is you have a simple CodePen or similar showing us what you're trying, that way we can better understand your issues. ... View more

The WebTileLayer supports the zxy format so something like this should work:  let customTileLayer = new WebTileLayer({ urlTemplate: "https://planetarycomputer.microsoft.com/api/data/v1/item/tiles/WebMercatorQuad/{z}/{x}/{y}@1x?collection=3dep-lidar-returns&item=VA_UpperMiddleNeckQL2_B2_2018-dsm-2m-1-2&assets=data&colormap_name=lidar-returns&nodata=-9999" }); However, the service is returning this error:  No item 'VA_UpperMiddleNeckQL2_B2_2018-dsm-2m-1-2' found in '3dep-lidar-returns' collection ...so the URL parameters are not correct. ... View more

Thank you for the explanation. ... View more

Why GraphicsLayer instead of FeatureLayer (with client-side Graphics)?  You get more functionality when using a FeatureLayer... is there a reason why you can't use a FeatureLayer as shown in the last part of the CodePen I shared above? ... View more

Negative extrusion values work ok if using a FeatureLayer ( https://codepen.io/john-grayson/pen/QWaQpXd )  I don't think negative extrusion values are allowed for GraphicsLayer, so you can use a FeatureLayer with client-side Graphics instead.  In the example above we use this technique to load the residential features, shown in green with a different offset. ... View more

Depending on how you're going to use it, you should be able to directly use the MapView.extent as the 'search/selecting/etc' geometry.  If you absolutely need the geometry as a Polygon then maybe check out the 'fromExtent()' static method. ... View more

Glad to hear you got it working.  There are many ways to model and display the 'difference' between two rasters; two common types I use are relative and absolute.  Displaying relative values show how much gain or loss is associated with each pixel. Displaying absolute difference will translate the results into three values: gain, loss, and no change. Depending on the source data and desired results you might want to add a Remap RF that narrows down the results into a well known set of values, then you could more easily match these values via a ColorMap RF.  I hope this helps. ... View more