WebAdmin

WebAdmin

The European Terrestrial Reference System 1989 (ETRS89), introduced in Europe as a geodetic reference system, is implemented in Romania (by the ODG of the ANCPI No. 212/2009) for the creation of a modern National Spatial Geodetic Network (RGNS) and the realization of pan-European cartographic products.
ETRS89 is defined according to the international standard ISO 19111, as composed of the ETRS89 geodetic datum, based on the GRS80 (Geodetic Reference System 1980) ellipsoid and the elliptical geodetic coordinate system.
• In Romania, two reference systems are officially used:
• The 1942 coordinate system (internationally known as "S-42"), based on the 1940 Krasovski ellipsoid, with the fundamental point at Pulkovo (Russia), together with the 1970 Stereographic projection;
• Reference system based on the reference 1910 Hayford ellipsoid, oriented on the fundamental astronomical point located inside the Military astronomical observatory in Bucharest, together with the 1930 stereographic projection – Bucharest secant plane.

The coordinates transformations used in Romania can be classified into two categories:
• Local coordinate transformations without a model of Helmert data distortion with 7 parameters or 4 parameters (standard deviation is around ± 0.10 m or less, depending on the distance between the joint points);
• Coordinate transformations with a data distortion model for which the standard deviation of the transformed coordinates is around ± 0.10-0.15 m, provided the existence of a sufficient number of joint points spread evenly across the entire country territory.

Weather
The GPS reference stations located in Baia Mare, Brăila, Cluj, Deva, Sibiu, Suceava and Timişoara are equipped with high-performance meteorological sensors of MET 3A-type, which accurately record, every 1 minute, temperature, pressure and the humidity of the place where this station is located.
The MET 3A-type weather sensor, produced by the american company Paroscientific Inc., has the following performances and features:
Performance:
-Pressure Accuracy ±0.08 hPa from 620 to 1100 hPa
-Temperature Accuracy ±0.1 deg C from -50 to +60 C
-Relative Humidity Accuracy ±2 Percent from 0 to 100 %RH at 25 deg C.
-Rapid Humidity Recovery Time after Saturation.
Features:
-Weatherproof Enclosure
-Fan Aspirated Probe System
-High Performance Pressure Port (Wind Insensitive)
-Bi-Directional RS-232 Serial Bus
-User Selectable Parameters Including Resolution, Update Rate
-Engineering Units, Sampling Commands etc. with Supplied Software
-LED Status Indicators (Power, Transmit, Receive)
-3 Year Long-term Stability Warranty
-Interfaces with GPS Receivers, Data Loggers and Computers
-Free zero adjustment
Example of a weather data file:

meteo

Necessary equipment for the use of ROMPOS® services
ROMPOS® DGNSS – Single-frequency receiver and direct internet access for connection to the ROMPOS®-DGNSS service server (mobile internet via GSM/GPRS); data format provided RTCM 2. x, 3. x
ROMPOS® RTK – Receiver with two (one * *) frequencies and direct internet access for connection to the ROMPOS®-RTK service server (mobile internet via GSM/GPRS); data format provided RTCM 2. x, 3. x
ROMPOS® GEO – Single or dual-frequency receiver whose satellite measurements will be connected in post-processing mode to the National Network of Reference GNSS Stations; data format provided: (V) RINEX G (M) V. 2.1 (1)

* - provided the possibility of internet access;
** - with certain limitations related to the distance from the reference station, no. of contacted satellites, the status of ionosphere etc.

The transfer of DGNSS/RTK differential corrections from the reference stations (network of reference stations) to the user can be done by various means, the most common being: transfer via radio waves, via GSM/GPRS mobile communication systems or via the internet. ROMPOS's DGNSS/RTK services are based on the transfer of data via the internet. This data is transmitted in a standardized RTCM (Radio Technical Commission for Maritime Services) format using the NTRIP (Networked Transport of RTCM via Internet Protocol) technology. NTRIP includes a standalone protocol based on HTTP – Hypertext Transfer Protocol and adapted to GNSS data transfer requirements. It allows the dissemination of differential corrections (in RTCM format) or other types of GNSS data, to stationary or moving users via the internet. NTRIP allows internet access via IP-based mobile networks (Internet Protocol), such as GSM, GPRS, EDGE or UMTS networks. The use of this technology is carried out by means of modules including: Ntrip Server (to transfer data from reference stations to central server), Ntrip Caster – for the administration and transfer of data from the central server (e.g. ROMPOS server) and Ntrip Client – to retrieve data (differential corrections) from the central server by users. The Ntrip Server and Ntrip Client modules are available free of charge from various software manufacturers, especially from the Federal Cartography and Geodesy Agency (BKG) in Germany (http://igs.bkg.bund.de), which was the promoter of this technology. These modules can be installed on various equipment such as: GNSS receivers, desktop computers, laptop, PDA, mobile phones, etc. The most practical variant is the one where the user has installed a Ntrip Client directly on the GNSS receiver, then, once this software is configured, using a GSM/GPRS modem, can connect and transfer data from the data server which runs a Ntrip Caster software to the GNSS receiver.

UPDATE 07.10.2019

Ca urmare a situației de forță majoră desfășurată în perioada 30 sep-3 oct 2019 abonamentele tuturor utilizatorilor au fost prelungite corespunzător cu 4 zile.

UPDATE 06.10.2019

Toate produsele RTK au revenit la soluții cu GLONASS, se poate folosi atât portul 2101 cât și 2105. 

04.10.2019

Descriere problemă.
S-a observat că roverele conectate la rețele de tip GNSS Spider nu obțin soluții fixe în descursul mai multor minute.
Problema se manifestă pentru orice produs de rețea și single-site RTK ce folosește NULLANTENNA și furnizează soluții GLONASS. Motivul pentru care roverul nu obține soluție fixă este că fluxul de date furnizat de GNSS Spider nu conține mesaje de observație după realizarea conexiunii. În cazul în care roverul stă conectat suficient, după câteva minute, GNSS Spider va începe să transmită mesajele cu observații și roverul va putea obține soluție fixă.
Fixarea ambiguităților în procesarea de rețea este conformă pentru toate constelațiile,
Cauze
Cauza acestei probleme se datorează faptului că, începând cu ziua de Sâmbătă, 29.09.2019, sateliții GLONASS transmit informații cu privire la almanah pentru satelitul R10, care nu sunt conforme cu documentația tehnică a constelației GLONASS (GLONASS ICD). Pentru satelitul GLONASS R10 este transmisă valoarea 7 pentru slot și publicată pe portalul de stare al constelației GLONASS (https://www.glonass-iac.ru/en/GLONASS/index.php) în timp ce ICD specifică valori între -7 și 6. Stațiile de referință GNSS Leica ce folosesc Measurement Engine (ME) v3 transmit această informație către GNSS Spider, unde nu sunt respinse în calculul NULLANTENA. Receptoarele care utilizează ME de generație nouă (ME4 sau OEM7) ex. Seriile GR/GM sau GRX1200+ și GRX1200+ GNSS, nu sunt afectate - firmware-ul deja filtrează informațiile greșite cu privire la almanah.
Soluții
1. Pe termen scurt au fost dezactivate observațiile GLONASS. Vă rugăm ca până la rezolvarea completă a problemei să utilizați doar portul 2101.
2. Pe termen mediu soluție este să nu se utilizeze efemeride de la receptoarele afectate. (Această soluție se va implementa de către administratorul ROMPOS în perioada 05-06.10.2019).
3. Pe termen lung se lucrează la un nou service pack pentru software.
Compensare caz de forță majoră
Având în vedere situația de forță majoră care a afectat furnizarea serviciilor ROMPOS, începând cu ziua de luni 7.10.2019 toate abonamentele active ale utilizatorilor de servicii ROMPOS vor fi prelungite corespunzător cu 4 zile.

The absolute differential positioning is a positioning technique that determines the position of a receiver, usually mobile, based on direct observations to satellites and some (differential) corrections transmitted (in real-time) from another fixed receiver called reference-receiver or base-receiver. A modern version allows the generation of these corrections based on a network of reference stations (receivers) such as the RN-GSP of the CNC. Pseudo-range (satellite-receiver distances) measured by the mobile receiver are corrected based on differential corrections obtained from the base-receiver, and then an absolute (punctual) positioning takes place. These differential corrections improve the accuracy of position determination.

The corrections submitted by the base-receiver can be Pseudo-Range-Corrections (PRC) and Rate of Range Corrections (RRC). These corrections can be determined using the pseudo-range defined on the basis of the codes transmitted by the satellites (DGNSS method -Differential GNSS) or on the basis of measurements performed using the carrier wave (RTK method - Real Time Kinematic). In addition, a specialized service based on a network of GNSS stations, can transmit further corrections, especially those due to the propagation of satellite signals through ionosphere and troposphere.

The Romanian Position Determination System - ROMPOS® is a project of the National Agency for Cadastre and Land Registration providing precise positioning in the european reference and coordinate system ETRS89 based on the national network of GNSS reference stations.

ROMPOS® is based on Global Navigation Satellite Systems – GNSS, including GPS, GLONASS and GALILEO (in the future), providing complementary data necessary to improve the accuracy of determining the position within several millimeters.

Covering the entire territory of Romania with a total of 74 GNSS reference stations, ROMPOS® is available at any time and for any location in Romania, provided the data signal coverage (internet) is present.

By using ROMPOS®, modern GNSS receivers work more efficiently, increasing labor productivity, reducing the costs.

With a single GNSS receiver and internet access via GSM/GPRS connections, the user can benefit of ROMPOS® services.

By integrating the ROMPOS System® in the similar european EUPOS® system, it ensures its interconnection with similar european systems, allowing for a uniform positioning even at the crossing of the border with neighbouring countries. ANCPI signed cross-border data exchange agreements with similar systems in Hungary, the Republic of Moldova and Ukraine. A significant number of users (geodesic and cadastre companies, authorized individuals in the geodetics domain, equipment manufacturers, etc.) utilize the real-time ROMPOS® services (DGNSS/RTK).

Real-time ROMPOS services can be easily accessed by following these 5 steps:

1. ANCPI user account and accessing the ROMPOS administration platform
2. Payment of services
3. Defining the rovers on the ROMPOS administration platform
4. Activating a ROMPOS service subscription
5. Rover configuration

Support Service
For the optimum and correct use of ROMPOS® services, CNC through the Support service, provides you with information and support regarding the services offered. The service is available via Live Chat and email.

The determination of the position refers to the acquirement of satellite observations (measurements) carried out in points of interest, coordinates (absolute or relative) of these points in a well-specified reference system. Satellite observations consist of various types of measurements performed between the satellite receiver located on the ground or near it and one or more satellites evolving on circumterrestrial orbits. The position determining methods are based on observations made using satellite signals broadcasted in the microwaves field. The emission flow of the satellite signal is usually continuous or can be pulses at regular intervals. The reception of these signals is done similarly.

Satellites play an active role by broadcasting signals that are received by specialized devices (receivers) that decode this signal. After decoding the signal from it, the information needed to determine the position of the receiver is extracted.
Global Navigation Satellite Systems (GNSS) are systems that allow high precision determination of position in a geocentric reference system at any point located on the earth surface, near or outside, using Earth's artificial satellites.
Currently the most well-known GNSS systems are NAVSTAR-GPS (USA) and GLONASS (Russia). There are no significant differences between the two GNSS systems in terms of operating principles and technology used. Each system includes three segments: the spatial segment (satellites), the control segment (Monitoring and control stations) and the user segment. GNSS satellites transmit time information, navigational information, and system status messages to users. The control segment is responsible for maintaining the satellite constellation, the attached time system and the determination of satellite orbit. Currently there are other countries intending to create GNSS systems (complementary).

NAVigation Satellites with Time and Ranging – Global Positioning System (NAVSTAR – GPS)

The GPS space segment comprises a number of 31 satellites positioned on 6 orbital planes angled at 55° at an altitude of 20230 km. The satellite revolution period is 11 hours and 56 minutes. An identical satellite constellation can be observed after a sidereal day 4 minutes earlier. The GPS constellation is composed of the GPS Block IIR-Replacement satellites (replacing the GPS Block II/IIA satellites from 1997), GPS Block IIR-M (modernized-introducing a new military signal-code M, on both carrier waves and C/A code on the second carrier wave called L2C), GPS Block IIF-Fallow On (introducing a new signal on a third frequency, L5) and GPS Block III (a new civilian signal, C/A code on the L1 carrier wave). The positioning accuracy for the civilian segment has improved from about 100m to 13m by suspending ITS (Selective Availability) technique. Major progress is expected by modernizing the spatial segment (the third L5 carrier wave, C/A code on the L2 carrier wave, etc.). The reference system used is WGS84 (World Geodetic System 1984).

GLObalnaya NAvigatsionnaya Sputnikovaya Sistema - GLObal NAvigation Satellite System (GLONASS)

The GLONASS space segment comprises a number of 27 satellites positioned on 3 orbital planes angled at 64.8° at an altitude of 19100 km. The satellite revolution period is 11 hours and 16 minutes. From the 27 designed satellites a total of 22 are operational. Each satellite has an atomic clock that generates a frequency from which the two carrier waves are formed. The signals transmitted are similar to the GPS system, including the C/A code on the L2 carrier. The precision level of the Russian GLONASS system is comparable to that of the NAVSTAR-GPS system. In Romania, the GLONASS system can be used, complementing the constellation of the GPS system. The reference system used is PZ90.

Galileo

European Union (EU) and the European Space Agency have developed the GNSS European system, named Galileo. The constellation of the Galileo system will consist of a number of 30 satellites positioned on 3 orbital planes angled at 56° at the altitude of 23616km. The revolution period of a satellite will be about 14.4 hours. In terms of positioning accuracy, availability and integrity, Galileo will be superior to the other systems. GALILEO will be interoperable with NAVSTAR-GPS and GLONASS. The reference and coordinate system used will be ETRS type (European Terrestrial Reference System). For positioning ROMPOS® uses the NAVSTAR-GPS and GLONASS global systems. When commissioning the new European system Galileo, ROMPOS® will also implement the use of this new GNSS system.

For accessing real-time ROMPOS products via NTRIP protocol, the following products are available:

1. “Network” type products = network of GNSS Stations
(generated using the principles of calculating differential corrections based on the network of GNSS reference stations): VRS (Ritual Reference Station), FKP (Flachen Korrektur Parameter), MAX (Master Auxiliary Concept)

Network products are transmitted in standardized RTCM format (version 3.1), excluding products which include CMR + characters.
The user (if he has the possibility through the software he owns), will first download the product list ("Mount points" in column 1) and then choose from this list the type of product you want to be purchased in real time. Note that for these types of products (network type), the user will necessarily have to transmit the coordinates of the station point (by NMEA-GGA type message). If the user is not able to automatically download the product list, then you will need to MANUALLY enter in the GNSS receiver the point of connection to the desired product, by writing in that menu the characters retrieved from column "RT Product Name".

2. “Nearest” type products = a reference station
(Generated using the principles of calculating differential corrections based on a single GNSS reference station)

“Single station” products are transmitted in a standardized RTCM format (3.1); The user (if he has the possibility through the software he owns), will first download the product list ("Mount points" in column 7) and then choose from this list the type of product you want to be purchased in real time. Note that for these types of products (“single station” type), the user needs to transmit the coordinates of the station point (by NMEA-GGA type message). If the user is not able to automatically download the product list, then you will need to MANUALLY enter in the GNSS receiver the connection point to the desired product, by writing in that menu the characters retrieved from column "RT Product Name".

3. Test products

In the list of ROMPOS-RTK products, at some point there may be products that are available for testing. The name of this product includes the word "Test", as users are warned that such a product will only be used for the purpose of verifying the generation and testing of product performance/quality. Such a product is NOT guaranteed and therefore will not be used for real applications.

 

RT product name Product type Site Message Type Protocol Port Authentication Null Antenna RTCM Version Satellite system Coordinate rate Correction rate Check maximum distance
Test_VRS_CMR+ Automatic cells - Virtual RS CMR+ NTRIP-Client ROMPOS-Proxy:2101 Ntrip Yes - G/R/-/-/- - 1s On
Test_iMAX_MSM4 Automatic cells - i-MAX RTCM 3.x (MSM4) NTRIP-Client ROMPOS-Proxy:2101 Ntrip Yes 3.x G/R/E/-/- 5s 1s On

Realtime products for port 2101.

RT Product Name Product Type Site Message Type Port RTCM Version Satellite system
Nearest_2.3 Nearest site - RTCM 2.x (Type 1;2;18;19) ROMPOS-Proxy:2101 2.3 G/R/-/-/-
Nearest_3.1 Nearest site - RTCM 3.x (Extended) ROMPOS-Proxy:2101 3.x G/R/-/-/-
Nearest_4G Nearest site - RTCM 3.x (MSM4) ROMPOS-Proxy:2101 3.x G/R/E/C/-
Nearest_CMR+ Nearest site - CMR+ ROMPOS-Proxy:2101 - G/R/-/-/-
RO_FKP_2.3 Automatic cells - FKP RTCM 2.x (Type 18;19) ROMPOS-Proxy:2101 2.3 G/R/-/-/-
RO_FKP_3.1 Automatic cells - FKP RTCM 3.x (Extended; 1034; 1035) ROMPOS-Proxy:2101 3.x G/R/-/-/-
RO_i_MAX_2.3 Automatic cells - i-MAX RTCM 2.x (Type 1;2;18;19) ROMPOS-Proxy:2101 2.3 G/R/-/-/-
RO_iMAX_3.1 Automatic cells - i-MAX RTCM 3.x (Extended) ROMPOS-Proxy:2101 3.x G/R/-/-/-
RO_MAX_3.1 Automatic cells - MAX RTCM 3.x (Extended;1015;1016) ROMPOS-Proxy:2101 3.x G/R/-/-/-
i-MAX_MSM5 Automatic cells - i-MAX RTCM 3.x (MSM5) ROMPOS-Proxy:2101 3.x G/R/E/C/-
RO_VRS_3.1 Automatic cells - Virtual RS RTCM 3.x (Extended) ROMPOS-Proxy:2101 3.x G/R/-/-/-
VRS_CMR+ Automatic cells   Virtual RS CMR+
ROMPOS-Proxy:2101 3.x G/R/-/-/-
RO_VRS_MSM5 Automatic cells - Virtual RS RTCM 3.x (MSM5) ROMPOS-Proxy:2101 3.x G/R/E/C/-

Realtime products for port 2105.

RT Product Name  Product Type Site  Message Type  Port  RTCM Version  Satellite system 
ABIU_3.1 Single site Alba Iulia  - ABIU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ABIU_4G_MSM5 Single site Alba Iulia  - ABIU RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ADJU_3.1 Single site Adjud - ADJU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ALXR_3.1 Single site Alexandria - ALXR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ALXR_4G_MSM5
Single site Alexandria - ALXR RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ARAD_3.1 Single site Arad - ARAD RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ARAD_4G_MSM5
Single site Arad - ARAD RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BACA_3.1 Single site Bacau - BACA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BACA_4G_MSM5 Single site Bacau - BACA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BAIA_3.1 Single site Baia Mare - BAIA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BAIA_4G_MSM5 Single site Baia Mare - BAIA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BAIS_3.1 Single site Bailesti - BAIS RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BAIS_4G_MSM5 Single site Bailesti - BAIS RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BEI2_3.1 Single site Beius - BEI2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BEI2_4G_MSM5
Single site Beius - BEI2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BG_LOVE_3.1 Single site Lovech BG - LOVE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BG_MONT_3.1 Single site Montana BG - MONT RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BG_RAZG_3.1 Single site Razgrad BG - RAZG RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/-/-/-/-
BG_SHUM_3.1 Single site Shumen BG - SHUM RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/-/-/-/-
BG_TARN_3.1 Single site VelikoTarnovo BG - TARN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BG_VARN_3.1 Single site Varna BG - VARN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BIST_3.1 Single site Bistrita - BIST RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BIST_4G_MSM5 Single site Bistrita - BIST RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BNLC_3.1 Single site Banloc - BNLC RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BNLC_4G_MSM5 Single site Banloc - BNLC RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BOTO_3.1 Single site Botosani - BOTO RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BRAI_3.1 Single site Braila - BRAI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BRAI_3G_MSM4 Single site Braila - BRAI RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
BRSO_3.1 Single site Brasov - BRSO RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BRSO_4G_MSM5 Single site Brasov - BRSO RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BRL1_3.1 Single site Barlad - BRL1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BRL1_4G_MSM5 Single site Barlad - BRL1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BUCR_3.1 Single site Bucuresti EXPO - BUCR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BUCU_3.1 Single site Bucuresti - BUCU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BUCU_4G_MSM5 Single site Bucuresti - BUCU RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
BUFT_3.1 Single site Buftea - BUFT RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
BUFT_3G_MSM4 Single site Buftea - BUFT RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
BUZ2_3.1 Single site Buzau - BUZ2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CALR_3.1 Single site Calarasi - CALR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CAM1_3.1 Single site Campeni - CAM1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CAM1_4G_MSM5 Single site Campeni - CAM1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
CIUC_3.1 Single site Miercurea Ciuc - CIUC RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CIUC_4G_MSM5
Single site Miercurea Ciuc - CIUC RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
CLU2_3.1 Single site Cluj Napoca - CLU2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CLU2_4G_MSM5 Single site Cluj Napoca - CLU2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
CORA_3.1 Single site Corabia - CORA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CORA_4G_MSM5 Single site Corabia - CORA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
COST_3.1 Single site Constanta - COST RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
COST_3G_MSM4 Single site Constanta - COST RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
CRAI_3.1 Single site Craiova - CRAI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
CRAI_4G_MSM5 Single site Craiova - CRAI RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
CRNV_3.1 Single site Cernavoda - CRNV RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DEJ2_3.1 Single site Dej - DEJ2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DEJ2_4G_MSM5 Single site Dej - DEJ2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
DEVA_3.1 Single site Deva - DEVA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DEVA_4G_MSM5 Single site Deva - DEVA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
DORO_3.1 Single site Dorohoi - DORO RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DRMN_3.1 Single site Darmanesti - DRMN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DRT2_3.1 Single site Drobeta Severin - DRT2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
DRT2_4G_MSM5 Single site Drobeta Severin - DRT2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
FAGA_3.1 Single site Fagaras - FAGA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
FAGA_4G_MSM5 Single site Fagaras - FAGA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
FAGE_3.1 Single site Faget - FAGE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
FAGE_4G_MSM5 Single site Faget - FAGE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
FAUR_3.1 Single site Faurei - FAUR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
FAUR_3G_MSM4 Single site Faurei - FAUR RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
FOCS_3.1 Single site Focsani - FOCS RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
GHE1_3.1 Single site Gheorgheni - GHE1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
GHE1_4G_MSM5 Single site Gheorgheni - GHE1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
GIUR_3.1 Single site Giurgiu - GIUR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
GIUR_4G_MSM5 Single site Giurgiu - GIUR RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
GURA_3.1 Single site Gurahont - GURA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
GURA_4G_MSM5 Single site Gurahont - GURA RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
HAR1_3.1 Single site Harsova 1 - HAR1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HAR1_4G_MSM5 Single site Harsova 1 - HAR1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
HORE_3.1 Single site Horezu - HORE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HORE_4G_MSM5 Single site Horezu - HORE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
HU_DEBR_3.1 Single site Debrecen - DEBR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HU_DEBR_3G_MSM4 Single site Debrecen - DEBR RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
HU_GYUL_3.1 Single site Gyula - GYUL RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HU_MSZE_3.1 Single site Szeged - MSZE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HU_MSZE_3G_MSM4 Single site Szeged - MSZE RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
HU_VASA_3.1 Single site Vásárosnamény - VASA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HUED_3.1 Single site Huedin - HUED RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
HUED_4G_MSM5 Single site Huedin - HUED RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
IASI_3.1 Single site Iasi - IASI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
INFP_3.1 Single site INFP - INFP RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
INFP_4G_MSM5
Single site INFP - INFP RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
INSU_3.1 Single site Insuratei - INSU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ISTR_3.1 Single site Istria - ISTR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
LEHL_3.1 Single site Lehliu Gara - LEHL RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MD_COMR_3.1 Single site Comrat - COMR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MD_EDIN_3.1 Single site Edinet - EDIN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MD_FALE_3.1 Single site Falesti - FALE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MD_LEOV_3.1 Single site Leova - LEOV RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MD_NISP_3.1 Single site Nisporeni - NISP RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MEDS_3.1 Single site Medias - MEDS RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MEDS_4G_MSM5
Single site Medias - MEDS RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
MIZI_3.1 Single site Mizil - MIZI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MIZI_4G_MSM5 Single site Mizil - MIZI RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
MNGL_3.1 Single site Mangalia - MNGL RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MOL2_3.1 Single site Moldova Noua - MOL2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MOL2_4G_MSM5
Single site Moldova Noua - MOL2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
MURE_3.1 Single site Targu Mures - MURE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
MURE_4G_MSM5
Single site Targu Mures - MURE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
NEHU_3.1 Single site Nehoiu - NEHU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ODO1_3.1 Single site Odorheiul Secuie - ODO1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ODO1_4G_MSM5
Single site Odorheiul Secuie - ODO1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ORAD_3.1 Single site Oradea - ORAD RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ORAD_4G_MSM5 Single site Oradea - ORAD RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
PASC_3.1 Single site Pascani - PASC RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PET2_3.1 Single site Petrosani - PET2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PET2_4G_MSM5 Single site Petrosani - PET2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
PITE_3.1 Single site Pitesti - PITE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PITE_4G_MSM5
Single site Pitesti - PITE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
PLOI_3.1 Single site Ploiesti - PLOI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PLOI_4G_MSM5
Single site Ploiesti - PLOI RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
PTNT_3.1 Single site Piatra Neamt - PTNT RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PTNT_4G_MSM5 Single site Piatra Neamt - PTNT RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
PTRS_3.1 Single site Petresti - PTRS RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
PTRS_4G_MSM5 Single site Petresti - PTRS RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
RESI_3.1 Single site Resita - RESI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
RESI_4G_MSM5
Single site Resita - RESI RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SATU_3.1 Single site Satu Mare - SATU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SATU_4G_MSM5
Single site Satu Mare - SATU RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SFGH_3.1 Single site Sfantu Gheorghe - SFGH RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SFGH_4G_MSM5 Single site Sfantu Gheorghe - SFGH RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SIB1_3.1 Single site Sibiu 1 - SIB1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SIB1_4G_MSM5 Single site Sibiu 1 - SIB1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SLOB_3.1 Single site Slobozia - SLOB RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SLOB_4G_MSM5 Single site Slobozia - SLOB RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SLTN_3.1 Single site Slatina - SLTN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SLTN_4G_MSM5
Single site Slatina - SLTN RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SUCE_3.1 Single site Suceava - SUCE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
SUCE_4G_MSM5 Single site Suceava - SUCE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
SULI_3.1 Single site Sulina - SULI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TAJO_3.1 Single site Tatarastii de Jos - TAJO RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TAJO_3G_MSM4 Single site Tatarastii de Jos - TAJO RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
TBUJ_3.1 Single site Targu Bujor - TBUJ RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TIM1_3.1 Single site Timisoara 1 - TIM1 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TIM1_4G_MSM5 Single site Timisoara 1 - TIM1 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
TJIU_3.1 Single site Targu Jiu - TJIU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TJIU_4G_MSM5
Single site Targu Jiu - TJIU RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
TLCA_3.1 Single site Tulcea - TLCA RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TLCA_3G_MSM4 Single site Tulcea - TLCA RTCM 3.x (MSM4) ROMPOS-Proxy:2105 3.x G/R/E/-/-
TRGV_3.1 Single site Targoviste - TRGV RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
TRGV_4G_MSM5 Single site Targoviste - TRGV RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
UA_HUST_3.1 Single site Khust UA - HUST RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
UA_RAHI_3.1 Single site Rakhiv UA - RAHI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
UA_VRHV_3.1 Single site Berehomet UA - BMRS RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
UA-CRNI_3.1 Single site Chernivsti UA - CRNI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/-/-/-/-
VAD2_3.1 Single site Valea Doftanei - VAD2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VAD2_4G_MSM5
Single site Valea Doftanei - VAD2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
VAMO_3.1 Single site Vatra Moldovitei - VAMO RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VAMO_4G_MSM5
Single site Vatra Moldovitei - VAMO RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
VASL_3.1 Single site Vaslui - VASL RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VATR_3.1 Single site Vatra Dornei - VATR RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VATR_4G_MSM5
Single site Vatra Dornei - VATR RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
VISE_3.1 Single site Viseu de Sus - VISE RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VISE_4G_MSM5
Single site Viseu de Sus - VISE RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
VLC2_3.1 Single site Ramnicu Valcea - VLC2 RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
VLC2_4G_MSM5
Single site Ramnicu Valcea - VLC2 RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ZALU_3.1 Single site Zalau - ZALU RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ZALU_4G_MSM5
Single site Zalau - ZALU RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ZERI_3.1 Single site Zerind - ZERI RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ZERI_4G_MSM5
Single site Zerind - ZERI RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-
ZIMN_3.1 Single site Zimnicea - ZIMN RTCM 3.x (Extended) ROMPOS-Proxy:2105 3.x G/R/-/-/-
ZIMN_4G_MSM5
Single site Zimnicea - ZIMN RTCM 3.x (MSM5) ROMPOS-Proxy:2105 3.x G/R/E/C/-

The Hour value is in GMT

Global RMS

RMS global

Residual Ionosphere (RTK): The estimated residual ionospheric error for a single base RTK user using data from the nearest site.

Residual Ionosphere (RTK): The estimated residual ionospheric error for a single base RTK user using data from the nearest site.

Residual Ionosphere (Network RTK): The estimated residual ionospheric error for a network RTK user.

Residual Ionosphere (Network RTK): The estimated residual ionospheric error for a network RTK user.

Residual Troposphere/Geometry (RTK): The estimated residual tropospheric and orbit error for a single base RTK user using data from the nearest site.

Residual Troposphere/Geometry (RTK): The estimated residual tropospheric and orbit error for a single base RTK user using data from the nearest site.

Residual Troposphere/Geometry (Network RTK): The estimated residual tropospheric and orbit error for a network RTK user.

Residual Troposphere/Geometry (Network RTK): The estimated residual tropospheric and orbit error for a network RTK user.

Page 3 of 6

Search

Contact

  • Schedule M-T : 8:00-16:30; F: 8:00-14:00
  • 1A Expozitiei Bvd., Sector 1, Bucharest
  • +40 21 224 39 67
  • office@rompos.ro
  • Fast contact