ArcticWeb 2.8.2

New

• Name changed from ArcticWeb to Arctic

Bugfixes

• Error when saving GreenPos reports
• Scrollbar not present for accordion panels

Other

• Removed old unused files

ArcticWeb 2.8.1

Bug fix

ArcticWeb version 2.8 Voyage Risk Management Tool now ready for community testing

    Release notes - Maritime-Web - Version ArcticWeb v2.8

The Voyage Risk Management Tool is now stable and ready for community testing. The tool is primarily targeted at vessels operating in remote areas and intended as a support for fulfilling tasks required by a vessel operators Polar Water Operating Manual. (PWOM). It is primarily based on the work of Captain Leif Skog and his thoughts on Risk Management. Instructions on how to use it can be found in the ArcticWeb user manual.

Epic

• [MARWEB-262] - pre-fill risk scores using available data
• [MARWEB-264] - Enable workflow where the entire route is assessed
• [MARWEB-301] - Make historical assessments reports accessible

Bug

• [MARWEB-563] - Ensure that UTC is used in VRMT

Task

• [MARWEB-263] - pre-fill the time of year factor when making a risk assessment
• [MARWEB-265] - Route start and end locations are automatically added as assessment locations
• [MARWEB-281] - Indicate whether a risk factor is assessed manually, automatically or historically in the assessment editor
• [MARWEB-284] - When a risk factor is automatically assessed indicate the data source if applicable
• [MARWEB-520] - Don't allow assessment if current position on route isn't an assessment location
• [MARWEB-521] - Fit view to see active route
• [MARWEB-529] - Present a link to the schedule editor if no route is defined
• [MARWEB-559] - Don't allow assessment point at start and end of route to be deleted
• [MARWEB-560] - Verify that routes have positive velocity between waypoints
• [MARWEB-561] - Timeout on Pouch Couch sync
• [MARWEB-562] - Attatch listeners to Pouch Couch sync and log errors
• [MARWEB-564] - Show historical assessments for all the routes of a vessel
• [MARWEB-565] - Choose the berth on assessing a berth location
• [MARWEB-566] - Make sure that the ETag servlet filter works on all html and js files

ArcticWeb v2.7 upgrade to OL4 and Angularjs 1.6.4

    Release notes - Maritime-Web - Version ArcticWeb v2.7

ArcticWeb version 2.7 has been released. This release is mainly a technical upgrade to improve stability and performance. The map handling should be a lot smoother now.

The Voyage Risk Management Tool feature has been improved but is not yet ready to go into real production and is therefore still located in the Beta Features tab.

A layer chooser is introduced allowing the user to enable/disable the various map data layers.

Some work has been done to improve the caching strategy and hopefully there will be no more problems due to stale cache. If you experience problems during login or otherwise then please clear all your browser cache and reload ArcticWeb. When a new release of ArcticWeb is released all the cached files need to reloaded and since there are quite a lot of files the first load may take some time so please be patient.

Epic

• [MARWEB-166] - VRMT prototype in ArcticWeb
• [MARWEB-186] - VRMT with manual assesment capabilities
• [MARWEB-481] - Improve performance of ArcticWeb by using Openlayers 4
• [MARWEB-514] - Integrate VRMT with main app
• [MARWEB-544] - Upgrade ArcticWeb to use the latest version of AngularJs
• [MARWEB-552] - Add SAR and VRMT chapters to the usermanual

Bug

• [MARWEB-539] - PouchDb sync failure when adding new effort allocatio SRU
• [MARWEB-541] - Vessel clusters doesn't look right
• [MARWEB-542] - Expected vessel position calculation is wrong when bearing is GC
• [MARWEB-543] - Cluster handling of vessels seems to be wrong
• [MARWEB-551] - The layer switcher doesn't always register the layers
• [MARWEB-556] - Error parsing weather report from DMI

Task

• [MARWEB-167] - Create a VRMT mockup page in ArcticWeb using Open layers 3
• [MARWEB-175] - Make timeline prototype
• [MARWEB-187] - Make risk assesment model and display assesments
• [MARWEB-188] - Display risk assesment locations on map
• [MARWEB-189] - Create risk assesment editor
• [MARWEB-205] - enable creation of assesment locations by clicking the route
• [MARWEB-206] - Activate location on left panel when clicked on map
• [MARWEB-208] - Make a risk assessment for a location by clicking that location on the map
• [MARWEB-210] - Scroll to assessment location on the map when chosen in the sidebar
• [MARWEB-211] - Support configuration of assessment factors
• [MARWEB-212] - Make the color of assessment location correspond to the latest assessment
• [MARWEB-221] - Allow the user to choose another route than the active
• [MARWEB-222] - Allow user to make risk assessment on current vessel location
• [MARWEB-223] - Allow user to delete assessment location
• [MARWEB-243] - Change project structure in accordance with googles suggestion
• [MARWEB-259] - loose coupling
• [MARWEB-266] - Change "Latest assessments" to support the new workflow
• [MARWEB-270] - Use only locations from current position and forward when initializing new assessments
• [MARWEB-279] - When initializing a new assessment create and include the vessels current position
• [MARWEB-280] - Make the assessment locations more visible on the map
• [MARWEB-282] - Add a note field to the assessment editor
• [MARWEB-283] - Make it impossible to save an assessment unless all route locations have been assessed
• [MARWEB-285] - Mark the expected vessel position on the map at any given time
• [MARWEB-286] - Make it easier to type in and read positions
• [MARWEB-287] - Display route location names on the map instead of id
• [MARWEB-288] - Display start time of the active assessment on the "assess" view
• [MARWEB-289] - Display planned departure time for the active route
• [MARWEB-290] - Adjust location eta when route is updated
• [MARWEB-303] - Snap to route when adding an assessment location
• [MARWEB-304] - Changes to a schedule must be reflected on next route load in VRMT
• [MARWEB-312] - Don't add vessel position as assessment location when the vessel hasn't begun the route yet
• [MARWEB-313] - Show progress when assessing
• [MARWEB-317] - Use ship icon when marking expected position
• [MARWEB-318] - text color on expected vessel position should be black
• [MARWEB-319] - It should be possible to view the entire globe
• [MARWEB-320] - rotate the vessel expected position icon to point along the route
• [MARWEB-321] - Add default name when creating current position assessment locations
• [MARWEB-322] - Synchronize assessment data to the server
• [MARWEB-323] - Add coordinates to the expected vessel position label
• [MARWEB-324] - Automatically discard assessment if it hasn't been completed in 30 minuttes
• [MARWEB-332] - Don't allow the user to start a new assessment on a historical route
• [MARWEB-335] - Show the list of finished assessments in the "Log of measures and reports" panel
• [MARWEB-336] - Show assessment details when clicking the "details" button
• [MARWEB-484] - Upgrade the Ice feature
• [MARWEB-485] - Upgrade the Maritime Safety (NW-NM) feature
• [MARWEB-486] - Upgrade the Weather feature
• [MARWEB-487] - ...

Bugfix

    Release Notes - Maritime-Web - Version ArcticWeb v2.6.10

Bug

• [MARWEB-357] - embryo.vrmt.Route doesn't calculate "isOnRoute" correctly
• [MARWEB-510] - Change login doesn't work from the administrator console

Performance optimization (vessel), appcache and bug fixes

    Release Notes - Maritime-Web - Version ArcticWeb v2.6.9

Bug

• [MARWEB-498] - Datepicker should hide if the user clicks outside the calender
• [MARWEB-501] - DMI Weatherforecast parser can't handle single digit hours
• [MARWEB-508] - Fail if NW/NM message doesn't have area

Task

• [MARWEB-482] - Upgrade the vessel feature
• [MARWEB-503] - Allow the user to change password when logged in
• [MARWEB-504] - Handle deprecated appcache cache
• [MARWEB-506] - Allow an administrator to reset a users password
• [MARWEB-507] - Update contact information in the ArcticWeb user manual

ArcticWeb release 2.6.8

This release does only include backend improvements.

• DMI grudseng parser updated to handle new dialects
• Reading of forecasts from ftp is now handled by a dedicated job

ArcticWeb release 2.6.7

Release Notes - Maritime-Web - Version ArcticWeb v.2.6.7

Overview

We have released ArcticWeb 2.6.7. The ArcticWeb menu now contains a BETA tab enabling users to get a preview of new features in the making. Right now we are working on performance improvements and a new tool to support voyage risk management based on the work done by Captain Leif Skog. Feedback is most welcome.

Following the latest release several users experienced problems login in to ArcticWeb. The reason in most cases being due to old browser cache. This version introduces a simple version check allowing the application to signal the user if there is a version mismatch between browser and server.

The full list of improvements and error fixes can be seen here: https://github.com/maritime-web/ArcticWeb/releases/tag/v2.6.7.1

Feedback in form of improvement suggestions and error reporting is as always most welcome. You may send it to me at [email protected] or to Rasmus Madsen Jensen at [email protected]

Bug

• [MARWEB-495] - When deleting a user with sailor role the vessel is not deleted

Task

• [MARWEB-41] - ForecastJob should only download newer files #1
• [MARWEB-47] - Health status for ForecastIn
• [MARWEB-195] - Deploy Forecast-In to production (test, then prod)
• [MARWEB-483] - Adjust the menu to include the upgraded features with a beta label
• [MARWEB-494] - Match build timestamp on client and server to notify user if mismatch
• [MARWEB-496] - Improve the release procedure for ArcticWeb
• [MARWEB-497] - Make it easy to copy all user email from the admin page

NW-NM data from Niord replacing MSI

v2.6.6

Version upgraded to 2.6.6 MARWEB-470 fixed dead links

ArcticWeb 2.6.5

This release contains a bug fix related to reassigning a search and rescue operation to a new coordinator

• #103 Coordinator not set correctly for allocations and patterns when reassigning operation to new coordinator