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.

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.

For landscapes created prior to September 2018: You may notice the blue boundary around the landscape does not perfectly match the edge of the landscape. This does not affect your data or use of the landscape in analyses, the boundary simply marks the approximate edge of your landscape.