Wish List - Revision history

Per.Engberg at 12:57, 2 January 2018

2018-01-02T12:57:23Z

← Older revision		Revision as of 12:57, 2 January 2018
Line 3:		Line 3:
	== High Priority ==		== High Priority ==
	*Ability to [[AtoN Ranges\|display the nominal ragne of an AtoN]] in the IWRAP model (enables analysis of AtoN effectiveness when compared to the density plot).		*Ability to [[AtoN Ranges\|display the nominal ragne of an AtoN]] in the IWRAP model (enables analysis of AtoN effectiveness when compared to the density plot).
	*For simulation purposes - Introduce a high speed replay of traffic situation using data from the AIS data base
	*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)		*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)
	*Add UNIX timestamps as one of the timestamp options
	*ToYear multiplication factor should be derived from the relevant part of the AIS dataset only. i.e. one could import a dataset covering a very large area, but ones model will only be in one corner of the area. The ToYear factor should only be based on the data from a rectangle enclosing the model (all the legs of the model)		*ToYear multiplication factor should be derived from the relevant part of the AIS dataset only. i.e. one could import a dataset covering a very large area, but ones model will only be in one corner of the area. The ToYear factor should only be based on the data from a rectangle enclosing the model (all the legs of the model)
	*Solve the Frequent Ferry Problem (number of vessels on a leg compared to number of passages)
	*Make it possible to select certain parts of the AIS dataaset for an analysis (graphically)
	*Legends on density plot
	*Display leg length when it is being drawn
	*One dialog box for all transparency controls		*One dialog box for all transparency controls
	*Enhance seasonal variation analysis - Indicate sailed distance as function of time in a dataset.		*Enhance seasonal variation analysis - Indicate sailed distance as function of time in a dataset.
	*AIS Stream recording facility to gather data for IWRAP analysis.
	*Near miss detection based on		*Near miss detection based on
	*Auto detect need for splitting legs up due to SOG and/or lateral distribution variation		*Auto detect need for splitting legs up due to SOG and/or lateral distribution variation
	*Intelligent naming of Legs and Traffic Distributions utilising the knowledge of north/southbound and west/eastbound.		*Intelligent naming of Legs and Traffic Distributions utilising the knowledge of north/southbound and west/eastbound.
	*Wind and Current "Roses" for each leg
	*Colour scheme for polygons. The blue scale should be reversed making the deepest polygon the most dark blue shade.
	*Colour Scheme for polygons. Transparency shoud be set to 50% as default.		*Colour Scheme for polygons. Transparency shoud be set to 50% as default.
	*Colour coding of results should be normalized, i.e. On legs the result should be divided by the length of the leg on polygons, perhaps be divided by the total length of all polygons?		*Colour coding of results should be normalized, i.e. On legs the result should be divided by the length of the leg on polygons, perhaps be divided by the total length of all polygons?
Line 24:		Line 15:
	*When switching between raster maps, the scale changes. Better to keep the scale of the last map used.		*When switching between raster maps, the scale changes. Better to keep the scale of the last map used.
	*Absolute chart scale.		*Absolute chart scale.
	*Possible to display the location of historical groundings and collisions including text details of incident.
	*Causation reduction factor change overview.		*Causation reduction factor change overview.
	*Model modification report, e.g. list causation changes.		*Model modification report, e.g. list causation changes.
Line 59:		Line 49:
	*Remove waypoints, combine legs (Done)		*Remove waypoints, combine legs (Done)
	*Important: END Points - There is a grounding contribution from end points of a leg structure.... grounding calc should end at leg points that are not connected to other legs. (Done I think / OFE)		*Important: END Points - There is a grounding contribution from end points of a leg structure.... grounding calc should end at leg points that are not connected to other legs. (Done I think / OFE)
			*Add UNIX timestamps as one of the timestamp options
			*Legends on density plot
			*Wind and Current "Roses" for each leg
			*AIS Stream recording facility to gather data for IWRAP analysis.
			*For simulation purposes - Introduce a high speed replay of traffic situation using data from the AIS data base
			*Solve the Frequent Ferry Problem (number of vessels on a leg compared to number of passages)
			*Make it possible to select certain parts of the AIS dataaset for an analysis (graphically)
			*Display leg length when it is being drawn
			*Possible to display the location of historical groundings and collisions including text details of incident.
			*Colour scheme for polygons. The blue scale should be reversed making the deepest polygon the most dark blue shade.

Oferiks at 17:07, 30 November 2013

2013-11-30T17:07:09Z

← Older revision		Revision as of 17:07, 30 November 2013
Line 2:		Line 2:

	== High Priority ==		== High Priority ==
			*Ability to [[AtoN Ranges\|display the nominal ragne of an AtoN]] in the IWRAP model (enables analysis of AtoN effectiveness when compared to the density plot).
	*For simulation purposes - Introduce a high speed replay of traffic situation using data from the AIS data base		*For simulation purposes - Introduce a high speed replay of traffic situation using data from the AIS data base
	*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)		*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)

Oferiks at 14:02, 4 September 2013

2013-09-04T14:02:45Z

← Older revision		Revision as of 14:02, 4 September 2013
Line 2:		Line 2:

	== High Priority ==		== High Priority ==
			*For simulation purposes - Introduce a high speed replay of traffic situation using data from the AIS data base
	*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)		*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)
	*Add UNIX timestamps as one of the timestamp options		*Add UNIX timestamps as one of the timestamp options

Oferiks at 05:11, 9 November 2012

2012-11-09T05:11:33Z

← Older revision		Revision as of 05:11, 9 November 2012
Line 1:		Line 1:
	Items to be considered for the further development of IWRAP.		Items to be considered for the further development of IWRAP as updated at the Sydney Risk Management 2012 Seminar.

	~~Updated~~ at the Sydney Risk Management 2012 Seminar.

	== High Priority ==		== High Priority ==

Oferiks at 04:38, 9 November 2012

2012-11-09T04:38:09Z

← Older revision		Revision as of 04:38, 9 November 2012
Line 1:		Line 1:
			Items to be considered for the further development of IWRAP.

			Updated at the Sydney Risk Management 2012 Seminar.

	== High Priority ==		== High Priority ==

Oferiks at 04:32, 9 November 2012

2012-11-09T04:32:32Z

← Older revision		Revision as of 04:32, 9 November 2012
Line 1:		Line 1:
	~~== List of Wishes for future development of IWRAP ==~~

	~~Topics raised at the [[IWRAP Training Seminar February 2010]]~~



	~~== Topics raised at the IWRAP Training Seminar in SYdney 2012 ==~~

			== High Priority ==
	*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)		*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)
	*Add UNIX timestamps as ~~an option~~		*Add UNIX timestamps as one of the timestamp options
	*ToYear multiplication factor should be derived from the relevant part of the AIS dataset only. i.e. one could import a dataset covering a very large area, but ones model will only be in one corner of the area. The ToYear factor should only be based on the data from a rectangle enclosing the model (all the legs of the model)		*ToYear multiplication factor should be derived from the relevant part of the AIS dataset only. i.e. one could import a dataset covering a very large area, but ones model will only be in one corner of the area. The ToYear factor should only be based on the data from a rectangle enclosing the model (all the legs of the model)
	*Solve the Frequent Ferry Problem (number of vessels on a leg compared to number of passages)		*Solve the Frequent Ferry Problem (number of vessels on a leg compared to number of passages)
Line 26:		Line 20:
	*Using Raster Charts, the identity of the current map is not displayed anywhere. One solution could be to mark the map in use in the list of maps in the map menu item.		*Using Raster Charts, the identity of the current map is not displayed anywhere. One solution could be to mark the map in use in the list of maps in the map menu item.
	*When switching between raster maps, the scale changes. Better to keep the scale of the last map used.		*When switching between raster maps, the scale changes. Better to keep the scale of the last map used.

	~~== High Priority ==~~
	*Absolute chart scale.		*Absolute chart scale.
	*Possible to display the location of historical groundings and collisions including text details of incident.		*Possible to display the location of historical groundings and collisions including text details of incident.
Line 34:		Line 26:
	*Plugin framework, causation factor, display overlay and more.		*Plugin framework, causation factor, display overlay and more.
	*Automatic report generator		*Automatic report generator

			See also topics raised at the [[IWRAP Training Seminar February 2010]]

	== Medium priority ==		== Medium priority ==
Line 61:		Line 55:
	*Split and join leg (Done)		*Split and join leg (Done)
	*Remove waypoints, combine legs (Done)		*Remove waypoints, combine legs (Done)
			*Important: END Points - There is a grounding contribution from end points of a leg structure.... grounding calc should end at leg points that are not connected to other legs. (Done I think / OFE)

Oferiks: /* Topics raised at the IWRAP Training Seminar in SYdney 2012 */

2012-11-09T04:27:57Z

Topics raised at the IWRAP Training Seminar in SYdney 2012

← Older revision		Revision as of 04:27, 9 November 2012
Line 19:		Line 19:
	*Near miss detection based on		*Near miss detection based on
	*Auto detect need for splitting legs up due to SOG and/or lateral distribution variation		*Auto detect need for splitting legs up due to SOG and/or lateral distribution variation
			*Intelligent naming of Legs and Traffic Distributions utilising the knowledge of north/southbound and west/eastbound.
			*Wind and Current "Roses" for each leg
			*Colour scheme for polygons. The blue scale should be reversed making the deepest polygon the most dark blue shade.
			*Colour Scheme for polygons. Transparency shoud be set to 50% as default.
			*Colour coding of results should be normalized, i.e. On legs the result should be divided by the length of the leg on polygons, perhaps be divided by the total length of all polygons?
			*Using Raster Charts, the identity of the current map is not displayed anywhere. One solution could be to mark the map in use in the list of maps in the map menu item.
			*When switching between raster maps, the scale changes. Better to keep the scale of the last map used.

	== High Priority ==		== High Priority ==

Oferiks: /* Older */

2012-11-09T04:16:33Z

Older

@@ Line 20: / Line 20: @@
 *Auto detect need for splitting legs up due to SOG and/or lateral distribution variation
-== Older ==
+== High Priority ==
-The following items have been identified as possible developments of the free version of IWRAP Mk2:
+== Medium priority ==
-*Different Lateral Distributions for different Vessel types or Draft Classes (Challenge due to very many distributions)
+== Wishes that have been fulfilled ==
-*Possible to display the location of historical groundings and collisions (high priority)
+*The lateral distributions should be displayed/represented as heading vectors. This will enable the analyst to determine if a leg should be divided into more than one leg. If a distribution contains a large spread of headings, the leg should be divided into two or even several shorter legs, or possibly even a set of crossing legs.(Done OFE/2012)
 *Possibility to define different area traffic to different parts of the model (Done)
 *Ease polygon digitalization, polygon edit like Google Earth (Done OFE 2012)
 *Ground polygon list (Done OFE/2012)
 *Labelling of polygons ''(DONE OFE/DEC2009'')
 *Ground polygon color definition per depth ''(DONE OFE/DEC2009)''
 *Enable display of partial results (done)
 *Development tool - Migrate to Qt 4.5 (Done)
 *Split and join leg (Done)
 *Remove waypoints, combine legs (Done)

Oferiks: /* List of Wishes for future development of IWRAP */

2012-11-09T03:36:46Z

List of Wishes for future development of IWRAP

← Older revision		Revision as of 03:36, 9 November 2012
Line 2:		Line 2:

	Topics raised at the [[IWRAP Training Seminar February 2010]]		Topics raised at the [[IWRAP Training Seminar February 2010]]



			== Topics raised at the IWRAP Training Seminar in SYdney 2012 ==

			*Normalized result (Grounding frequency pr. sailed nm (i.e. Sum of length of all legs multiplied with number of passages)
			*Add UNIX timestamps as an option
			*ToYear multiplication factor should be derived from the relevant part of the AIS dataset only. i.e. one could import a dataset covering a very large area, but ones model will only be in one corner of the area. The ToYear factor should only be based on the data from a rectangle enclosing the model (all the legs of the model)
			*Solve the Frequent Ferry Problem (number of vessels on a leg compared to number of passages)
			*Make it possible to select certain parts of the AIS dataaset for an analysis (graphically)
			*Legends on density plot
			*Display leg length when it is being drawn
			*One dialog box for all transparency controls
			*Enhance seasonal variation analysis - Indicate sailed distance as function of time in a dataset.
			*AIS Stream recording facility to gather data for IWRAP analysis.
			*Near miss detection based on
			*Auto detect need for splitting legs up due to SOG and/or lateral distribution variation

			== Older ==

	The following items have been identified as possible developments of the free version of IWRAP Mk2:		The following items have been identified as possible developments of the free version of IWRAP Mk2:

Oferiks at 03:07, 9 November 2012

2012-11-09T03:07:13Z

← Older revision		Revision as of 03:07, 9 November 2012
Line 8:		Line 8:
	'''Enhanced modelling/analysis capabilities'''		'''Enhanced modelling/analysis capabilities'''

	*Different Lateral Distributions for different Vessel types or Draft Classes		*Different Lateral Distributions for different Vessel types or Draft Classes (Challenge due to very many distributions)
	*Possible to display the location of historical groundings and collisions		*Possible to display the location of historical groundings and collisions (high priority)
	*Possibility to define different area traffic to different parts of the model		*Possibility to define different area traffic to different parts of the model (Done)
	*The lateral distributions should be displayed/represented as heading vectors. This will enable the analyst to determine if a leg should be divided into more than one leg. If a distribution contains a large spread of headings, the leg should be divided into two or even several shorter legs, or possibly even a set of crossing legs.(~~By Omar~~/~~Erik 2. May 2010~~)		*The lateral distributions should be displayed/represented as heading vectors. This will enable the analyst to determine if a leg should be divided into more than one leg. If a distribution contains a large spread of headings, the leg should be divided into two or even several shorter legs, or possibly even a set of crossing legs.(Done OFE/2012)


	'''Polygon Improvements'''		'''Polygon Improvements'''

	*Ease polygon digitalization, polygon edit like Google Earth		*Ease polygon digitalization, polygon edit like Google Earth (Done OFE 2012)
	*Ground polygon list		*Ground polygon list (Done OFE/2012)
	*Labelling of polygons ''(DONE OFE/DEC2009'')		*Labelling of polygons ''(DONE OFE/DEC2009'')
	*Ground polygon color definition per depth ''(DONE OFE/DEC2009)''		*Ground polygon color definition per depth ''(DONE OFE/DEC2009)''
	*Store ground polygons in separate files		*Store ground polygons in separate files (in order to be shared between several models) (low priority)


	'''Result view enhancement'''		'''Result view enhancement'''
	*Graphical illustration of differences between 2 jobs		*Graphical illustration of differences between 2 jobs (parked)
	*Absolute chart scale		*Absolute chart scale (high priority)
	*Enable display of partial results		*Enable display of partial results (done)
	*Ranked list of collisions and groundings results, enable jump to leg, ground, waypoint in geographic result view		*Ranked list of collisions and groundings results, enable jump to leg, ground, waypoint in geographic result view (High Priority)


	'''General Improvements'''		'''General Improvements'''
	*Development tool - Migrate to Qt 4.5		*Development tool - Migrate to Qt 4.5 (Done)
	*Split and join leg		*Split and join leg (Done)
	*Remove waypoints, combine legs		*Remove waypoints, combine legs (Done)
	*Causation reduction factor change overview		*Causation reduction factor change overview (High Priority)
	*Model modification report, e.g. list causation changes		*Model modification report, e.g. list causation changes (High priority)
	*Reduction factor schemes		*Reduction factor schemes (???)
	*Plugin framework, causation factor, display overlay		*Plugin framework, causation factor, display overlay (High Priority)
	*More information to manual about how to choose the value of ''mean time between checks'' when analyzing different sea areas		*More information to manual about how to choose the value of ''mean time between checks'' when analyzing different sea areas
	*Should be possible to modify ''mean time between checks'' for each leg individually (OFE/05DEC2009)		*Should be possible to modify ''mean time between checks'' for each leg individually (OFE/05DEC2009)
	*Possibility to calculate with monthly traffic volumes (without multiplying volumes by 12 and then dividing results by 12)		*Possibility to calculate with monthly traffic volumes (without multiplying volumes by 12 and then dividing results by 12) (Parked)
	*Change job names or add comments to jobs after they have been completed		*Change job names or add comments to jobs after they have been completed
	*Overwrite decimal zeros when keyboarding speeds and frequency adjustment factors in Traffic Volume Distribution Editor		*Overwrite decimal zeros when keyboarding speeds and frequency adjustment factors in Traffic Volume Distribution Editor (done)
	*Calculate overtaking and head-on collision frequencies per length unit of leg, not per leg (so that longer legs would not look riskier than shorter legs)		*Calculate overtaking and head-on collision frequencies per length unit of leg, not per leg (so that longer legs would not look riskier than shorter legs)