As time passes, I realize what kind of device I need in the field. In a few words, it must be a sum of the devices that we discussed day by day: GNSS receiver, computer, router, display (for the moment, something different from a phone).
Soon a compute card will be released (
http://www.intel.com/content/www/us/en/compute-card/intel-compute-card.html) and I ask myself if a GNSS receiver could integrate certified Javad software via a compute card slot - Net View & Modem could be a good example.
Now, I will argue that Net View & Modem is a good start and there is a lot of room for useful functions and even for point collecting routines. I saw that it support multiple windows, and this is an excellent adaptation for a 7" display (and not only).
On the other side it is very frustrating as long as we have fix solution in Net View & Modem and the ability to log NMEA files with positions, to not have a "Store points" routine with Javad statistics, Map interface with country specific coordinate systems and useful CAD functions. In 2017, this things must be the minimal standard. But very good improvements at Spectrum screen.
About the statistics, there are a lot of examples, techniques and routines in Windows 10 that helps to see things from another perspective. So if we consider 10 clusters (each cluster = 5 groups of 5 epochs with verify and reset at every 5 epochs), we could distribute them in real-time, along an offsetted circle with a known diameter (ex: 1m); and around the clock; total 250 epochs;
This looks like phase 1 in LS; we could add phase 2 around the circle without reset for smoothing the solution; in the end, the circle probably will act like a geometric constraint. The above clusters reflect a real field situation with my Triumph-1 receiver, min 3/4 RTK engines, no automatic mode.
Just playing with Windows 10..
