The New ReachView 3 is out

[geohawk]

From my (or a developer’s) perspective, I’d say maximum value would be enabling custom lists created by the user.
There are simply too many standards across different domains to have a single master list of codes.
So, a user-managed list would be optimum, with the ability to put in custom codes on the fly (sometimes we encounter strange things for which there are no codes… )

Thanks for considering, this is great!

[wizprod (Christian Grüner)]

Well, you would still need an interface to understand and project all the different systems, so by no means not an easy or simple task.

[tisijola (Tomisona Isijola)]

Like in the Autodesk Products.

[geohawk]

Not sure what you mean when you refer to systems being projected.
We’re referring to columns in tables of data, where one column is simply a short code ('CODE"= 4 chars usually) and the next column is a simple plaintext DESC (Brief written description of the CODE)

This has nothing to do with coordinate systems or projections.
As all coordinates are tuples, these two columns are simply an addendum to the existing database… (with CODE being inserted prior to DESC and DESC remaining as it currently is)

Examples:
Ellipsoidal system: PLLHCD
Projected system: PENZCD
ECEF systems: PXYZCD

Hope that helps

[sridhar11089]

please add features like area calculation ,point to point distance ,offset ,intersection

[EBE111057 (Bryan Enfinger)]

You forgot “traverse to point”, in case you’re trying to determine a location for a point or reproduce a deed bearing and distance point

[svetlana.nikolenko]

Hi @geohawk, @tisijola,

Now, I’m totally sure I understood your request right Thanks for the discussion!

[svetlana.nikolenko]

Hi @sridhar11089,

Thanks for the requests! They are noted.

[geohawk]

Excellent @svetlana.nikolenko
Thank you

[geohawk]

@sridhar11089 @svetlana.nikolenko
If I were to prioritize some of those features, I would personally order them as:

1. Inverse
2. Point to Line (Stakeout Distance) - [requires line support… creation or import]
3. Dividing Line [requires line support… creation or import]
4. Grid to Ground Distance
5. Average Value of Points
6. Line extension (or “offset point”)

The rest are useful, but too advanced for the state of development in my personal opinion.

[Doppler_Uav]

Hi all,

I think it would be interesting and useful, if possible, to be able to add some kind of “time mark” (as in ReachM+/M2 for mapping), where you can have the start and end time of each point measured in Reachview3.

And that when post-processing with the RTKlib you have an “event.pos” file with the PPK points.

In this way, we would always have the possibility of post-processing the points, in case the RTK fails or if we have doubts with any point.

I have been using “PPK point extractor” for Reachview 2 but would be great if Reachview 3 had something similar without using an external program.

PPK point extractor software

Hi, guys! I have something sweet for you. I started to work on a software, that will help us all to deal with PPK process. Everyone, who is doing PPK with Emlid knows, that it is pain to export points from POS files. When you have over 100 points, you feel like a zombie, while using Time Interval function in RTKLib. I have a more comfortable solution for you. First of all, for those, who are not familiar with the problem. When you are surveying something with Survey tool and planning to do PPK…

[hh1 (Heinrich Hiemesch)]

Hi Svetlana,

thanks for ReachView 3. I’ve used the Beta before and was already very content, esp. with the ability to select the coordinate system and the height. I tried today the new not beta and was disappointed because when selecting the coordinate system for me in Bavaria, Germany, which is ETRS89 UTM Nord 32 or 33, the height system DHHN2016 is gone. It was previously available in the beta.
Having the right coordinate system and the height will save a lot of time for post processing which is obsolete then!
TIA for correcting this as soon as possible.

Heinrich

[hh1 (Heinrich Hiemesch)]

Having looked around my measurements I dicovered that DHHN2016 was gone between the 8. and 10. December - if this information is helpful. When creating a new project the settings of the last one are copied to the new one and at the 10. December the height system wasn’t copied.

Heinrich

[step]

Please insert the blue bubble again into the stakeout tools as you approach the point. Thanks

[ntripcevich (Nico Tripcevich)]

Hello thank you for the many new features in Reachview3. This feature is described
"Autoconnect to the only Reach in the network
If only one receiver is found, the app will connect to it automatically. This comes handy when working with the Wi-Fi hotspot created by Reach."
Is this feature working? I imagine it scans the entire local network for appropriate devices.
I connect our system to a variety of personal and business wifi networks and RV3 will not locate it on the host Wifi network. I have to find it by looking at connected device IP#s.
Steps taken:

1. access ReachRS2 at 192.168.42.1 and sign it into the wifi network using credentials
2. Sign Android phone running Reachview3 into same network with same credentials
3. In Reachview3 look for ReachRS2 on network. No luck.
   I find my ReachRS2 consistently if i use my phone hotspot. If i have admin access to 192.168.1.1 I can see it in the list of Connected Devices and access it over the IP# and use Reachview2 on the device.
   Are there router security settings that are known to interfere with Reachview3 locating the device on the local network?

[canoyar]

This is great work by the development team. Really takes it to the next level. I believe most of these have been said, but wanted to list some suggestions for the next update.

• Easy Description input
• Linework corresponding to Descriptions and specific special codes. (similar to SurvCE)
• Inverse, and other COGO commands
• Manually entry of points for stakeout. (it helps adding points on the fly in the field)

On a side note I just ordered another unit and have become a sole RS2 user. This updated was a big selling point for it. Keep it up.

[canoyar]

Function to stakeout a line based on 2 points would be useful as well.

[egor.fedorov]

Hello Heinrich,

Unfortunately, we’ve had to remove the DHHN2016 height datum due to licensing issues. We are currently in contact with BKG to bring it back. Bringing back support for German heights is one of our priorities right now.

[egor.fedorov]

Definitely on our list, thanks.

[egor.fedorov]

Hi Nico,

Some routers have a special option that forbids zeroconf (mDNS) scans in the LAN by default. If you have access to the router’s admin interface, could you try and look for it?