TUPLOT External - Revision history

Emilie Nielsen at 01:57, 8 January 2026

2026-01-08T01:57:04Z

← Older revision		Revision as of 11:57, 8 January 2026
Line 21:		Line 21:

	The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (.int) that is written by ArcMap and read by TuPLOT. The .int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the .int file may not be deleted. If this occurs many times, a build up of .int files may occur in the same folder as the .tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired .int file using the <b>Set Interface File</b> button in the TuPLOT window, though generally this should not be required.		The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (.int) that is written by ArcMap and read by TuPLOT. The .int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the .int file may not be deleted. If this occurs many times, a build up of .int files may occur in the same folder as the .tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired .int file using the <b>Set Interface File</b> button in the TuPLOT window, though generally this should not be required.


			{{Tips Navigation
			\|uplink=[[ArcGIS_TUFLOW_Toolbar\| Back to ArcGIS TUFLOW Toolbar]]
			}}
			{{Tips Navigation
			\|uplink=[[ArcTUFLOW_Toolbox_and_Toolbar\| Back to ArcTUFLOW Toolbox and Toolbar]]
			}}

ElizaCollison at 14:46, 29 November 2023

2023-11-29T14:46:19Z

@@ Line 16: / Line 16: @@
 <br>
 [[File: TuPLOT_viewer.PNG]]
 =How it works=

ElizaCollison: /* How it works */

2023-11-29T14:45:54Z

How it works

← Older revision		Revision as of 00:45, 30 November 2023
Line 34:		Line 34:

	The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (.int) that is written by ArcMap and read by TuPLOT. The .int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the .int file may not be deleted. If this occurs many times, a build up of .int files may occur in the same folder as the .tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired .int file using the <b>Set Interface File</b> button in the TuPLOT window, though generally this should not be required.		The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (.int) that is written by ArcMap and read by TuPLOT. The .int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the .int file may not be deleted. If this occurs many times, a build up of .int files may occur in the same folder as the .tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired .int file using the <b>Set Interface File</b> button in the TuPLOT window, though generally this should not be required.

	The stand alone TuPLOT viewer is also planned to be made available in both QGIS and Mapinfo.

Ellis Symons: /* Planned Future Enhancements */

2018-03-02T00:52:06Z

Planned Future Enhancements

← Older revision		Revision as of 10:52, 2 March 2018
Line 19:		Line 19:
	=Planned Future Enhancements=		=Planned Future Enhancements=
	Planned future enhancements include:		Planned future enhancements include:
	*ArcTUFLOW toolbox tools added to Toolbar
	*Full functionality from the TUFLOW QGIS plugin		*Full functionality from the TUFLOW QGIS plugin
	**Secondary axis		**Secondary axis

Ellis Symons: /* About */

2018-03-02T00:31:27Z

About

← Older revision		Revision as of 10:31, 2 March 2018
Line 1:		Line 1:
	=About=		=About=
	TUPLOT external is a 1D and 2D time series result viewer. It looks to provide the functionality of ~~TUPLOT in~~ QGIS in an external program that can be called from other GIS platforms (e.g. ArcGIS).		TUPLOT external is a 1D and 2D time series result viewer. It looks to provide the functionality of the QGIS TUPLOT plugin in an external program that can be called from other GIS platforms (e.g. ArcGIS).

	=How to Use=		=How to Use=

Ellis Symons: /* How to Use */

2018-03-02T00:30:23Z

How to Use

← Older revision		Revision as of 10:30, 2 March 2018
Line 13:		Line 13:
	</ol>		</ol>
	<br>		<br>
	[[File: ~~ArcTUFLOW_toolbar_2017-11-AA-demo~~.~~png~~]]		[[File: ArcTUFLOW_ToolbarTUPLOT.PNG]]
	<br>		<br>
	[[File: TuPLOT_viewer.PNG]]		[[File: TuPLOT_viewer.PNG]]

Ellis Symons: Created page with "=About= TUPLOT external is a 1D and 2D time series result viewer. It looks to provide the functionality of TUPLOT in QGIS in an external program that can be called from other..."

2018-03-02T00:25:50Z

Created page with "=About= TUPLOT external is a 1D and 2D time series result viewer. It looks to provide the functionality of TUPLOT in QGIS in an external program that can be called from other..."

New page

=About=
TUPLOT external is a 1D and 2D time series result viewer. It looks to provide the functionality of TUPLOT in QGIS in an external program that can be called from other GIS platforms (e.g. ArcGIS).

=How to Use=
The toolbar and button functions are displayed below.
<ol>
<li> The TuPLOT viewer can be initiated by clicking the TuPLOT icon[[File: TuPLOT_icon.PNG]]
<li> This will prompt the user to select a TUFLOW Plot Control File (*.tpc)
<li> The next prompt will allow the user to automatically import the relevant GIS files associated with the *.tpc
<li> Use the dropdown box to select a PLOT layer (Points, Lines, Regions)
<li> Select layers you would like to view results for and click the TuPLOT icon again
<li> Each selection update requires the user to click the TuPLOT icon to update the graph
</ol>
 
[[File: ArcTUFLOW_toolbar_2017-11-AA-demo.png]]
 
[[File: TuPLOT_viewer.PNG]]

=Planned Future Enhancements=
Planned future enhancements include:
*ArcTUFLOW toolbox tools added to Toolbar
*Full functionality from the TUFLOW QGIS plugin
**Secondary axis
**ARR2016 functionality (pulling statistics from results)
*Opening multiple *.tpc files at once
*Exporting data from display
*Enhance viewer association with ArcGIS
**Exit with ArcGIS
**Minimise with ArcGIS
**Window always in front of ArcGIS but not always topmost
If you have any suggestions on additional functionality or improvement, or find a bug, please email a description to support@tuflow.com 

=How it works=
Using 'dockable windows' internally in ArcGIS to graph results requires the setup of a graph template for each graphed scenario (for example: a template for 1 result on the primary axis, a template for 2 results on primary axis, a template for 1 result on the primary axis and 1 result on the secondary axis... a template for n results on primary axis and n results on secondary axis). This would be time consuming to set up, and potentially impossible to capture all scenarios. The stand alone TuPLOT viewer uses a program external to ArcGIS for graphing and viewing 1D results and 2D time series results as a solution to this problem.

The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (*.int) that is written by ArcMap and read by TuPLOT. The *.int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the *.int file may not be deleted. If this occurs many times, a build up of *.int files may occur in the same folder as the *.tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired *.int file using the Set Interface File button in the TuPLOT window, though generally this should not be required.

The stand alone TuPLOT viewer is also planned to be made available in both QGIS and Mapinfo.