The following are known issues for IFTDSS:
Data and runs from IFTDSS 2.0 will not be available in this version of IFTDSS. This is because IFTDSSis built on an entirely new system relative to previous versions.
On some runs, FlamMap did not fully complete the modeling run, resulting in partially complete modeling outputs. This is easily seen in Map Studio when a modeling output resembles the one pictured below. The bottom of portion of the map populated with -1 for all output values.
Status: This was patched on 3/15/18, but if you find an old report with this issue or encounter a similar bug, please send a support ticket to the Support desk.
In the Develop Treatment Alternative task, on the "compare" step, horizontal "streaking" sometimes appears in the Landscape Change layer for large landscapes. These streaks do not reflect raster changes, they are introduced due to a re-sampling issues on the ArcGIS server.
Fix: To remove the streaks, zoom in on the map and it will automatically re-draw the layer.
When uploading shapefiles with multiple adjoining polygons, IFTDSS will automatically join the polygons into a single dataset; this process may create erroneous gaps or vertices where these polygons once touched. Visit the Shapefile Repair Topic for details on how to repair and edit shapefiles.
In some cases the location may be mapped incorrectly due to Internet Service Provider differences. Sometimes you may be mapped to the physical location of your ISP's servers, sometimes close to your actual location but off by a bit, sometimes nowhere near where you actually are! In short, when GPS is not present and the browser has to rely on your internet connection to determine your location, you are more likely to see the wrong location on the map. This is a known issue that the IFTDSS team is working on, we appreciate your patience while we work through this bug! We are working on eliminating many known bugs, but in the end we are not likely to be able to guarantee that it will work every time on every device and browser.
When navigating back and forth within IFTDSS, use the application's navigation bar, buttons, and breadcrumbs do so. Avoid using your browsers "back" and "forward" buttons.
For security purposes, access to Operational Layers is limited to federal government employees. In the future, we will be working to streamline access to non-federal partners.
Currently we have received feedback that the MTBS Burn Severity Reference layer is not displaying, and work is underway resolve the issue (as of 6/7/17).
Currently, the timezone used when IFTDSS timestamps an output is eastern time.
If you're using IFTDSS landscape extents to download additional data from the LANDFIRE Data Distribution site, you'll have to re-clip the landfire files to match the IFTDSS if you need them to match exactly to the same extent. See the Spatial Extent of IFTDSS and LANDFIRE Data Topic for more information.
The error message you encountered appears within Developing Treatment Alternatives Run Model tab, when you attempt to assign a run name that is already used elsewhere within your IFTDSS account. To alleviate this error, use a new name for your run.