ReachView 3 Beta

Hi everyone

for sure it s already has been discussed but i can not found it back.

I have a point GCP
Using the last update of reachview 3 the height says 78,280m while exporting the same project the height is 78,639m.
Just to avoid any mistake i set pole height 0m ad adapter 0m.
Even trying to subtract the gps module 0,065 (RS+) i don t find feedback.

thanks

1 Like

Good Morning, today i was on survey and noticed that my ReachView 3 was v4.12 Beta.
Until now there was no info about. So, whats new in this version?

1 Like

Quite an update for the Android app — 4.12 Beta is here for you to test!

@Nordstern Sorry for the full changelog being late this time!

Here is the list of new stuff:

  • We added support for a bunch of new vertical coordinate systems! This update includes CRSs for Austria, New Caledonia, Balearic Islands, Canary Islands, Ceuta, Alicante, and Slovakia.

    • GHA height and EVRF2000 Austria height (Austria)
    • NGNC08 height (New Caledonia)
    • Mallorca height , Menorca height , and Ibiza height (Balearic Islands)
    • Lanzarote height , Fuerteventura height , Gran Canaria height , Tenerife height , La Gomera height , La Palma height , and El Hierro height (Canary Islands)
    • Ceuta 2 height (Ceuta)
    • Alicante height (Alicante)
    • Baltic 1957 height , Baltic 1957 depth , and EVRF2007 height (Slovakia)
  • We changed the default base CRS for some coordinate systems used in New Caledonia, Slovakia, and Romania.

    • RGNC91-93 is now used as a base CRS for IGN56 Lifou, IGN53 Mare, ST84 Ile des Pins, NEA74 Noumea, IGN72 Grande Terre, and ST87 Ouvea (New Caledonia)
    • ETRS89 is now used as a base CRS for S-JTSK (Slovakia)
    • ETRS89 is now used as a base CRS for Pulkovo 1942(58) (Romania)

    Now, using CRSs that are based on these systems involves datum transformations with a horizontal grid or by transformation parameters.

  • The EPSG list was updated in accordance with the EPSG v9.8.12 and ESRI v10.8.1.

  • Serial and Bluetooth configurations are now editable in position streaming settings.

  • The correction output settings are here! At the moment, we have TCP and Serial wizards available, with others coming in the future updates.

  • Now, when you create or edit a project, NTRIP profile, or point, text fields won’t contain accidentally entered leading and trailing whitespaces or empty lines.

  • Minor visual updates.

12 Likes

It should be out in the near future, so stay tuned.

Awesome! So far it was already possible to connect the RS2 to the Collector and Survey123 app from Esri. Does this mean with the new Software I will be able to directly collect MSL (orthometric heights) rather then just HAE heights in Survey123?

Hi everyone!
New app version for iOS – 4.6 Beta is out for testing too!

Here’s what’s new:

  • Now, it is possible to edit TCP and LoRa configurations in correction input settings.

  • Added a delete point button to the point info bottom sheet so you can delete points without opening point editor.

  • After you edit the Serial configuration, it will be automatically selected as a correction input setting.

  • Fixed improper behavior of the settings screens when the connection with a receiver is lost.

As always, we are looking forward to hearing any feedback from you.

settings2 delete2

7 Likes

Hey Andrew,

We actually do have this geoid as an option. This geoid is tied to systems that have NAD83(2011) as a base coordinate system. In our app, these systems will be named like this:

NAD83(2011) / Some place or zone.

Please note that it means you will need to use a base station referenced in NAD83(2011) for the end results to be accurate.

Then choose the vertical datum to be NAVD88 and you should be good to go.

Do you have a link for setting the base as such? I tried to do this a month ago and it would be a big help!

1 Like

You may already know this but if you have not updated to iOs 14 that can cause issues. #StupidApple.

1 Like


Just 2 cosmetic issues on the latest app and firmware on the RS2.
The latitude shows “N” in the southern hemisphere instead of “S”
The sim card status shows no signal despite this session running on a Ntrip correction over 4G

5 Likes

Great job! yesterday i tested it with the vertical coordinate system for Austria (GHA heigth) at wellknown points. It works really fine!
I have one wish. would it be possible to define my favorite coordinate system that automatically ist set for a new project!?

8 Likes

Hello!
Yes, in future i will always use the EPSG: 31256 (Austria GK East) as CRS and vertical coordinate system for Austria (GHA heigth) EPSG: 5778.
This will be my standards for the future. Maybe that sometimes i will survey in WGS84.

1 Like

The easiest way would be to connect your base receiver to a different base (like a correction service) that is already referenced in NAD83 (2011) and average its position.

Also, if you have your coordinates in some other system, say WGS84, you have an option to convert them manually using some external software. We have plans to add this functionality to ReachView 3 in the future as well.

Thanks you for testing! It’s always nice to know we’ve successfully supported yet another country.

That’s a nice idea. We will actually have something for this in one of the future updates. Keep an eye out for the changelogs.

2 Likes

Hey Luke,

There’s actually a minus before the coordinates. It’s just the format we show coordinates in.

I’ve created an issue for the team to check this out, thanks.

Do I need to change the base coordinate type to XYZ?

1 Like

I have now a geoid GEOTIF (*.tif) file for my area to deal with dhhn2016 heigts. Is there a way for me to somehow import this to reachview 3?

Gratulation for ara AUSTRIA!
Today I tested ReacVIew 3 Beta with emlid RS2 and APOS (Austiran Corretion Service with NTRIP) in area Tirol where you use EPSG: 31254 (Austria GK West) as CRS and vertical coordinate system for Austria (GHA heigth) EPSG: 5778. In XY I got with the BEV GIS GRID an error about 2-3 cm and in height 10cm (can be corrected in antenna offset) which is very good. Point was near house, so there could also be an error of 1-2 cm.

Whishes for further functions:

  • use of 7 parameter to make the best fitting in local coordinate system
  • more possibilities for attributes
  • support of WMS or WMTS (so we can get Geoland or other orthoimages as basemap too)
  • support of WFS-T or ArcGIS Online Web Feature Services

But you are in a very good way to make emlid doing very well!

Peter Hartl
Hartl Consulting

4 Likes

Localization…

Hello Michael,
what do you mean with Localization…