Known Issues

Data and runs from IFTDSS 2.0 will not be available in IFTDSS versions 3.0 and later. This is because IFTDSS is built on an entirely new system relative to previous versions.

(Reported April 2017)

Shapes deleted in My Workspace may still be visible in Map Studio for some time after deletion. Shapes deleted in Workspace are permanently deleted by the system on a weekly basis and will no longer be visible within seven days.

(Reported February 2022)

This issue can occur if your IFTDSS session times out. You may also encounter it if you bookmarked a page in IFTDSS while logged in, such as https://iftdss.firenet.gov/#/home and attempt to access it while logged out.

To resolve the issue, start a new browser session and access IFTDSS via the home page at: https://iftdss.firenet.gov/landing_page/

(Reported 2023)

Delete the failed run and re-run the model. This is most often a failure in the fire modeling services that feed into IFTDSS.

(Reported August 2022)

This error most often occurs when attempting to access IFTDSS from outside of North America. However, it has been occasionally encountered by users in North America outside of the United States.

Solution:

Due to security policies, IFTDSS availability is limited to North American users. If you are experiencing issues accessing IFTDSS, please contact the IFTDSS Support Desk for assistance.

(Reported March 2023)

This error is encountered when using very long names with no spaces. For example, a landscape name consisting of several words separated by underscores rather than spaces. Such a name will still allow the report to be viewed in IFTDSS, but will lead to this error when the user attempts to download a pdf copy.

The solution is to break up names in IFTDSS with spaces rather than underscores to avoid encountering this browser error when downloading a pdf copy of the report.

(Reported May 2021)

For Exposure Analysis run failures resulting in the message: "gov.iftdss.exception.IFTDSSArcGISException: AGOL could not be reached for the following sub-HVRAs:..."

This error occurs when a data service supporting Mapped Values fails, thus leading to an Exposure Analysis failure as well. If you experience this error you may notify the Support Desk and try again later. Typically, the error only occurs for minute or two, so deleting the failed run and re-running a few minutes later will result in a completed run.

(Reported March 2020)

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 Shapefile Repair for details on how to repair and edit shapefiles.

(Reported April 2017)

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 issue on the ArcGIS server.

Fix: To remove the streaks, zoom in on the map and it will automatically re-draw the layer.

(Reported 2/22/18)

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.

(Reported 3/14/2018)

When a user views a very large Highly Valued Resource or Asset (HVRA) Set in Map Studio, the HVRA Set may appear grayed out in the Layer List until zooming in.

(Reported 29 July 2019)

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.

(Reported 7/18/20)

On some small screens and tablets Map Studio may appear slightly different compared to normal sized monitors, with the widgets along the bottom spanning the entire page, and the widgets in the top left and right in different locations. As a temporary work-around while we address this issue, you may reduce the size of the page via the zoom option in Chrome. From the top ribbon, click the Customize icon in the top right of your browser, and reduce the zoom until Map Studio displays correctly, typically 90% or 80%.

Minimum Travel Time Fire Spread (MTT) modeling will fail if the ignition is fully within a filled barrier, even if it is on burnable fuel in a “hole” in the barrier.

The fail message in the RHP will read:

If the barrier is not filled, the model will run.

(Reported December 2020)

This may appear when downloading MTT outputs and reviewing in ArcMap. When looking at the coordinate system for the outputs, it appears that they are not in the same projection. This is just a naming difference for the MTT Embers layer and MTT Major Flow Paths. All of the data are in the same projection and do not need to be re-projected.

Minimum Travel Time (MTT) Fire Spread Major Paths may not be visible if you are zoomed out too far. Zooming in should fix the issue. If you are unable to see Major Paths regardless of zoom level, please contact the IFTDSS Support Desk .

(Reported June 2023)

This failure can be encountered with any model type. It is caused when a momentary interruption in connection prevents the IFTDSS system from locating the landscape specified by the user.

To fix this error, delete the failed model run and run the model again. This will usually result in successful model completion. If the model still fails, you may submit a technical support ticket by navigating to "Help" in the top right of the navigation bar and following the prompts under the "Request Support" option.

(Reported January 2021)

In this case, delete the failed run and re-run the model. This error message appears when there is an issue with the fire modeling services that feed into IFTDSS.

(Reported August 2022)

Multipart shapes that lie in close proximity to a landscape may appear in drop-down menus for landscape tasks such as summarizing or modeling. While IFTDSS automatically filters these drop-down menus to show only shapes that intersect the landscape in question, these multipart shapes may be included if their extent intersects the landscape, regardless of whether the individual polygons that make up the shape do. In the example below, the multipart shape would appear in the drop-down because its extent, roughly indicated with a dotted line, intersects the landscape, even though neither polygon does. If a report were generated for the landscape using that multipart shape area of interest, the landscape features and/or model outputs would all be 0.

(Reported February 2019)

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.

(Reported April 2017)

Currently, the timestamps for models and resources created within in IFTDSS are in eastern time.

Note that IFTDSS and FTEM do not actively convert data to eastern time if it is imported. This has the potential to cause confusion, especially in FTEM, where fires from different sources may be brought into the system.

For example, a fire that is discovered on July 1 at 2100 eastern daylight time will have a discovery time in IRWIN of July 2, 0100 GMT. However, when this data is pulled into FTEM, the discovery day/time will remain July 2, 0100, it will not automatically be converted back to July 1 at 2100 eastern daylight time. In parts of FTEM where the time zone is not listed, this may cause confusion.

(Updated September 2021)

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 Spatial Extent of IFTDSS and LANDFIRE Data for more information.

(Reported April 2017)