{"id":9042,"date":"2024-04-11T17:50:39","date_gmt":"2024-04-11T17:50:39","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=9042"},"modified":"2024-04-12T17:25:38","modified_gmt":"2024-04-12T17:25:38","slug":"release-3_14_00-changes","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/release-3_14_00-changes\/","title":{"rendered":"Release 3_14_00 Changes"},"content":{"rendered":"

What is new in the SNIP<\/span> 3_14_00 release<\/strong> – released April 12th, 2024
\n(updating the prior release of 3_13 issued on November 29th, 2023)<\/p>\n

This is the next production release of SNIP<\/strong><\/span> following the Rev 3_13 release.\u00a0 This release contains both major and <\/em>minor<\/em> improvements in response to user requests.\u00a0 This release supports both 32-bit and 64-bit installations on all Windows Platforms from Windows 7 to the current editions.<\/p>\n

It is recommended that all Windows SNIP<\/strong><\/span> installations now update to using this release.<\/p>\n

Changes in this release include<\/strong><\/h2>\n

Map Displays, New OSM maps<\/strong><\/h3>\n

A new Map Display setup<\/a> dialog has been created to unify map settings when using both Google and OSM provided base maps. \u00a0The SNIP<\/strong><\/span> operator can select either a Google provided base map, or one provided by Open Street Maps (OSM) and MapTiler sources. Several rendering options can be set as well as the type of base map and the preferred language to be used on text labels.\u00a0 The colors, radius distance, and other aspects of drawn lines can also be set.\u00a0 \u00a0See this article<\/a> for more details.<\/p>\n

\"\"<\/a><\/p>\n

Considerable effort has been undertaken to add support for OSM maps in this release of SNIP<\/strong><\/span> and improve mapping in general.\u00a0 Better tool-tips now provide additional information about base and user (but only if the requestor has the administrative rights to see such details), see this article<\/a> for more details. \u00a0Google provided maps are still used for colorized thematic plots of prior User positions<\/a>, but OSM provided maps are used everywhere else (if that choice is selected).\u00a0 See the article above<\/a> for a summary of the pros and cons of each map provider and the various choices they support.<\/p>\n

The default Google map API revision has now been updated to use Rev 3.53\u00a0 This will need to be updated again mid year due to Google changes.\u00a0 You can learn more about the Google release process here<\/a>.<\/p>\n

Because OSM style maps will be new to our existing customer base, this release of SNIP<\/strong><\/span> has been hard-wired to always use the Google map style at startup as the default.\u00a0 To enable OSM maps. Simply check the box in the upper left marked \u201cSet Open Street Maps\u2026<\/strong>\u201d or press \u00a0the button marked \u201cRestore Defaults<\/strong>\u201d. \u00a0In future releases, SNIP<\/strong><\/span> will start with map style that you have selected as your preferred choice.<\/p>\n

In general, maps are now being sent to the local browser for display rather than the Document Viewer<\/a>.\u00a0 A side effect of this choice is faster rendering as well as well as lower processing loads on the Caster.<\/p>\n

NEAR Streams<\/strong><\/h3>\n

New logic implemented in the NMEA $GGA<\/a> processing for NEAR stream<\/a>s now overcomes some problems seen in some poorly designed NTRIP Client<\/a> devices. \u00a0These clients on occasion will stop tracking GNSS satellites and produce a $GGA sentences with a location of zero\/zero.\u00a0 This in turn causes the NEAR stream functions in SNIP<\/strong><\/span> to reevaluate the user location for a suitable base.\u00a0 Because there is no suitable base a few hundred km south of Ghana, the user would then be disconnected.\u00a0 In the new logic any transitory location jumps to zero\/zero are ignored and the prior base station assignment is not changed until a more reasonable location is presented.\u00a0 At that time the normal evaluation of the user location with respect to the base station assignment is resumed.<\/p>\n

Added a new entry to the weekly log files whenever an NTRIP Client connected to a NEAR stream changes to a new base, noting the new base assignment. \u00a0This follows the same message seen for this event in the console log<\/a>, but also adds a date and time stamp.<\/p>\n

IP Blocking Logic<\/strong><\/h3>\n

Corrected a bug present in SNIP<\/strong><\/span> Rev 3.13 where previously active temporary IP bans\/blocks<\/a> were not always being reloaded after an application restarted.<\/p>\n

Corrected a bug in support for editing the ranges<\/a> of banned\/blocked IPs where the final byte of the ending IP was mangled due to a parsing error.<\/p>\n

Implemented better memory management logic of the blocked IP cache.\u00a0 Any stale (not recently used) IPs are now purged after 3 days rather than once a week.<\/p>\n

Customer Accounts \/ User Accounts <\/strong><\/h3>\n

At every SNIP<\/strong><\/span> startup a full cross checking of all Customer Account<\/a> and User Accounts (CA\/UA) index assignments is now performed to detect and resolve any conflicts.\u00a0 Typically no operator action is required. \u00a0This resolves some issues where deployments had manually edited or entered data and\/or moved data from one SNIP<\/strong><\/span> installation to another.<\/p>\n

Secure Sockets, SSL Uses<\/strong><\/h3>\n

Added additional logic to report bad SSL connection attempts in the console log, both connections into<\/em> SNIP<\/strong><\/span> and from<\/em> SNIP<\/strong><\/span> to other remote servers (such as the IP reverse mapping<\/a> lookups).<\/p>\n

General use of SSL security protocols was updated from revision 1.1.1 to 3.x to follow current industry best practices.\u00a0 A few DDLs were updated due to this as well (the installer will install the correct DLLs which your machine needs).<\/p>\n

Push-In Reservations<\/strong><\/h3>\n

Extensive cross checks for assignment conflicts have now been added, this is run at startup (along with a similar check of user names and customer accounts) to detect and correct any problems.<\/p>\n

Every time a new Push-In reservation<\/a> is made, a summary of similar reservations is now sent to the console log.\u00a0 This provides an automatic means to see what other base stations a given user or user\u2019s email might also be associated with. \u00a0The logic in the dialog itself still prevents outright duplicate name assignments from occurring, but this provides a useful summary of similar names used on the caster.\u00a0 A typical result is shown below:<\/p>\n

Edited the PUSH-In reservation for: ImaFakekeBase<\/strong> Confirmation eMail sent to: Grigori Rasputin <imafake@gmail.com><\/strong> \r\nCross check results for ImaFakekeBase<\/strong> [User:Grigori Rasputin<\/strong>, eMail:imafake@gmail.com<\/strong>, Ph:, CA#:]\r\n\u00a0\u00a0No similar mountPt<\/strong> names were found.\r\n\u00a0\u00a0The following 2<\/strong> entries with similar Owner \/ User Names<\/strong>:\r\n\u00a0\u00a0\u00a0\u00a0KMNYDTrav, KadNUDwtc\r\n\u00a0\u00a0No similar User eMails<\/strong> were found.\r\n\u00a0\u00a0There are 3,032<\/strong> other entries with the same email domain.\r\n\u00a0\u00a0No similar User Phone<\/strong> numbers were found.\r\n\u00a0\u00a0No similar Reservation Passwords<\/strong> were found.<\/pre>\n
Web API<\/strong><\/h3>\n
Minor web page revisions were made to now show which Customer Account and Staff Account is connected on the heading sections of the web page itself.<\/p>\n
The Web interface<\/a> for use by customer accounts and customer staff accounts now respects any preset limits on the number of allowed User Accounts or Base Station Push-In reservations the account may create. \u00a0\u00a0Additional users or bases beyond the allowed limit cannot<\/strong> be created by the customer.\u00a0 The web page now also shows the current count and maximum allowed count when a limit has been set (the default setting is not to have any limit).<\/p>\n
Note<\/strong> T<\/span>hat this is the limit that the Customer<\/em><\/strong> may create, there is not such limit on the SNIP<\/strong><\/span> operator or admin staff who can always<\/strong> create additional User Accounts and Base Stations and assign these to the Customer account.\u00a0 \u00a0Some deployments may choose to manage all the user accounts associated with a customer account (not letting the customer manage anything); to do this they simply disable read-write<\/em> access by that customer in the Web API, and limit them to read-only<\/em> access.<\/p>\n
Changes made for Lite<\/em> Models of SNIP<\/span><\/strong><\/h3>\n
Lite models of SNIP<\/strong><\/span> can now request and see a report about all current Base Stations<\/strong>, and a report about all Base Stations and connected User Accounts<\/strong> (NTRIP Clients<\/a>), using the local browser on the host machine.<\/p>\n
Memory Leaks<\/strong><\/h3>\n
Many minor memory leaks were found and removed in this release. \u00a0While small in size, such things do accumulate with time and needed to be removed.\u00a0 These included leaks in<\/p>\n