I assume those are world wide fire records. So I agree that it would be nice to limit the traced area to that part of the image exposed in the open drawing.
Yes, exactly. Without a checkbox to limit to window extents or a Make Image tool that creates a local image, you have to write a query that builds a table and image of only those tiles visible.
I doubt the Trace Areas process as launched will conclude because you are asking it to run Trace Areas on an image that is just over 1 exabyte (one million terabytes) in size,. To see the size of the image, open the VIIRS I Band 6 hour layer and switch to the Component panel of the Contents pane. It reports the image is 4,541,874,553,189 records, each of which records contains 256 * 256 * 4 bytes. Multiply all that out and you get over an exabyte.
Most of that worldwide image is invisible pixels, that is, empty space, which allows algorithmic short cuts to compute the trace once each and every one of those tiles is fetched from the forestry service server. But you still have to fetch all of them and the system still has to look at each byte, even if almost all of them do not have data that contributes to the trace.
What you are dealing with is a data structure aimed exclusively at viewing, the nature of WMS, and a major downside for those who want to use the data themselves as opposed to viewing a presentation of the data cobbled up by somebody else. Another way to approach this is to get the vector representation from the WFS server on the forestry service page (link, I believe in that same thread).
The problem there is that they don't give you the vectors for last six hours and such, it is just the vectors for the entire year. So you have to write a query to select out of what they give you only those records for detections for the last, say, day. That is non-trivial because they use a daft date format of ordinal days (incorrectly labeled "julian", which is a related but different thing), so you need to write a quick and dirty expression to construct an ordinal day from the current date, so you can grab what you want from what they present.
That's easy enough to do for any given year because you can permit your expression to ignore leap years and leap centuries, but for more general use it is best to use VBScript, which can do that for you. I don't recall if the VBScript method knows there are such things as leap centuries.
I get the feeling that whoever maintains that data wanted to be able to deal with dates using simple arithmetic on integers, maybe because whatever software they used could not deal with datetimes, so they stored the date as an ordinal date.
layer seems to disappear when the Bing Streets layer is on.
If you are referring to the Wildfires2 project I published, that has a Bing Hybrid (called Bing Streets + Satellite in the tab) layer as the bottom layer. The VIIRS I band layer has partial opacity so it might be difficult to see against the clutter in the Bing layer when zoomed far out. In the Layers panel set the opacity of the VIIRS layer to 100% to make it more visible. If you drag and drop the Bing Streets layer into the map, that is an opaque layer so you must take care to position the layer below the VIIRS layer if you want to see the VIIRS layer.
Thanks for the photo. That has to be nerve-wracking to see the smoke bear down anywhere near your community.