LP1
LP1
LP1
Prepared for:
Prepared by:
NAME UITM NO
Group:
RCAP1203G
TABLE OF CONTENT
1.0 Introduction
2.0 Members
4.0 Methodology
GNSS Static
5.1 Convert all coordinate from each task to MRT68, Cassini Old , RSO Old and
New RSO and New Cassini using GDTS software
5.2 For each task, compare and explain the difference of the coordinate as follows:
-MRT68 vs GDM2000 (by assuming 1sec~30m)
-RSO old vs RSO new
-Cassini Old vs Cassini new
5.3 Compare the result between task 1 and task 2 in terms of coordinate in GDM2000,
New Cassini, New RSO
5.4 Result
5.0 Conclusion
Appendix
ACKNOLEDGEMENT
First and foremost we would like to thank the Almighty God for giving us the
strength. We are really grateful because we managed to complete out fieldwork task
within the time given by our lecturer, Dr. Muhammad Faiz. This task cannot be
completed without the effort and co-operation from our group members which consist
of Muhamad Hazim, Nurqistina Allisya, Samantha, Abdul Lokman Hakim and Haikal
Ikhwan.
Last but not least we would like to express our sincere gratitude to the Geomatic
Department for enabling us to use the tools to complete our task
1.0 INTRODUCTION
Static in the context of Global Navigation Satellite Systems (GNSS) refers to a surveying
technique where high-precision location and other parameter data are obtained by keeping the
GNSS receiver motionless for a considerable amount of time, often several hours or more.
This method works well for capturing long-term events such as groundwater depletion,
tectonic deformation, and slowly shifting landforms. Static GNSS survey data may be utilised
to provide high-resolution, high-accuracy measurements in standard reference frames.
It also involves keeping the receiver immobile for a sizable amount of time. High-
precision tridimensional coordinates are computed using this approach in traverse stations,
yielding millimeter-level ground position coordinates in both the horizontal and vertical
components. Fine measurement and time-series data are resolved using static GNSS
techniques in order to record phenomena like tectonic deformation, earthquakes, groundwater
depletion, and slowly changing landforms.
1.2 OBJECTIVE
1
2.0 MEMBERS
THE TEAM
2
3.0 EQUIUPMENT AND SOFTWARE
Equipment Explanation
GNSS Receiver The core component that receives signals
from satellite constellations (such as GPS,
GLONASS, Galileo, or BeiDou) to
determine precise positions in three-
dimensional space (latitude, longitude, and
altitude).
3
Tripod Stand Supports the GNSS receiver and provides
stability during the survey. Tripods are
essential for stationary or static surveys.
4
Measuring Tape This typically use for measuring height of
our instrument such as South base and the
Topcon gnss receiver that we used
5
ToRinex To convert any data sth to any format that
available in it so the data can be process
later
6
4.0 METHODOLOGY
i. Identify Location
Every field observation was carried out at UiTM Perlis. For GNSS observations, we
have defined five CPs that are outlined in practical circulars. We have made advantage of the
CRM list that our instructors across UiTM Perlis have established. We also adhere to the
requirements for creating a CP, which state that the JUPEM CRM must be built as a
foundation and that the CRMs we select for the CP must be more than 200 metres apart. The
5 CPs we observed are CP37 which is close to the Netball Court UiTM Perlis, CP54 which is
in front of the Nursery Center UiTM Perlis, CP13 and CP14 which are close to the
intersection of Kesinai Complex and the last CP which is CP5 which is near Laman Satria in
the UiTM Perlis Parade Ground. We have established the CRM GPS JUPEM, CP-R01821, as
a base. The 5 CPs we have created are surrounding the base.
7
ii. Fieldwork
We needed three weeks to finish this work's observation portion. Install the GNSS
equipment on the known control point (site) and the new control point (rover) first. At
JUPEM Pillar, we use SOUTH as the base and TOPCON GR5 as the rover. Next, conduct a
GNSS observation using the fast static positioning method, with a log interval of one second
and an observation session lasting at least twenty minutes (during our observations, an
observation session always lasted more than twenty minutes). Additionally, we must
guarantee that during an observation session with GDOP less than six (6) and at least 90%
sky visibility, the Receiver must track a minimum of five (5) satellites. To make it easier to
refer to when doing data processing, we must make sure that all observation information such
as antenna height, height type, start and stop times of the observation, approximate positions,
etc is recorded in a log sheet. Till the observation is finished, repeat the process on the
remaining 4 points. Prior to the rover commencing its observation, make sure the base is
prepared. Once the observation is complete, notify the base. Lastly, download the information
we gathered from the GNSS receiver during the observation. We use the same data that we
get from MYRTKNET for CORS data.
Process the data using all the software that has been given to student. The process will
be shown in the TBC processing data.
iv. Report
8
4.1.3 Data Processing
2. Before entering the data in TBC, the data for South Africa must be converted to
RINEX format using the Rinex converter, and the data for Topcon GR5 must be
converted using tps2rin.
3. To begin processing, open TBC and create a new project using a blank template.
9
4. Select the coordinate system from the project settings, then click on Change to modify
the projection.
5. Choose the coordinate system group for the Kedah and Perlis zone and the Malaysian
Casini Geocentric.
10
6. Click "Finish" after selecting "Geoid model" for "No geoid model."
7. After that, Select Baseline Processing, select Satellites, and adjust the Elevation Mask
to 15 degrees.
8. Once the project setup is complete, we can enter the converted data.
11
9. To make things easier, we computed the slant height to vertical height during
observation beforehand. The formula on the figure is used to find the vertical height
for TOPCON GR5, and the formula for SOUTH (the height we collected during
observation – 0.1247) is used.
12
10. In the TBC, start with the basic data. Choose the bottom antenna, then modify the
manufacturer to SOUTH and the mounting method to bottom of antenna. The most
crucial thing to do is adjust the height that we previously calculated. The base will
then appear after selecting the receiver at the bottom and changing the manufacturer
to SOUTH. Click OK.
13
11. In TBC, enter the rover data. Proceed in the same manner as before, but substitute
TOPCON for the manufacturer, ensure that the bottom-mounted antenna method is
used, and adjust the calculated height. Once you click OK, a baseline-displaying rover
will appear.
12. To add coordinates, right-click on the base after entering the rover and base data.
14
13. Click the question mark to select control quality, change the coordinate type to local,
and add the coordinate base (latitude=6°26'46.31281", longitude=100°16'38.01427",
and height= 10.074). A tiny triangle will then appear on the base.
14. Choose Process Baselines after selecting every baseline and clicking the survey next
to it.
15
15. The processing result will show, and we won't need to update if the problem has been
resolved or if there isn't a red flag next to CP.
16. Finally, by selecting Baseline Processing Report, we can see the report.
17. We employ the same step from 10 to 16 for the CORS processing of the data.
However, the base coordinates for Arau must be obtained from MYRTKNET.
16
5.0 RESULT AND ANALYSIS
KNOWN STATION
CP14
CP57
17
CP5
18
CORS ARAU
CP14
COORDINATE
LATITUDE LONGITUDE HEIGHT (m)
SYSTEM
GDM2000 6°26'56.97166"N 100°16'48.05956"E 18.146
MRT68 6°26'58.57639"N 100°16’52.65570”E 32.600
CP57
COORDINATE
LATITUDE LONGITUDE HEIGHT (m)
SYSTEM
GDM2000 6° 26' 44.99889" 100° 16' 37.25153" 7.999
MRT68 6° 26' 46.60279" 100° 16' 41.84621" 22.457
19
CP5
COORDINATE
LATITUDE LONGITUDE HEIGHT (m)
SYSTEM
GDM2000 6°27’ 05.17035”N 100°16'30.74573"E 1.767
MRT68 6°27’06.77575” N 100°16’35.33963” E 16.246
20
5.2 ANALYSIS RESULT
KNOWN POINT :
ΔNorthing = 0.003 m
ΔElevation = 0.008 m
ΔNorthing = 0.002 m
ΔElevation = 0.007 m
ΔNorthing = 0.003 m
ΔElevation = 0.008 m
21
CORS ARAU :
COORDINATE
HEIGHT
SYSTEM LATITUDE LONGITUDE
(M)
(GDM2000)
22
5.3 COMPARE AND EXPLAIN THE DIFFERENCE
23
CP57 (CORS ARAU) :
GDM 2000
6° 26' 44.99889" 100° 16' 37.25153" 7.999
MRT 68
6° 26' 46.60279" 100° 16' 41.84621" 22.457
Differences 49.508 140.778 14.458
24
5.3.2 RSO OLD VS RSO NEW
COORDINATE
NORTH (m) EAST (m)
SYSTEM
25
CP57 (CORS ARAU) :
COORDINATE
NORTH (m) EAST (m)
SYSTEM
COORDINATE
NORTH (m) EAST (m)
SYSTEM
26
5.3.3 CASSINI OLD VS CASSINI NEW
DIFFERENCE 0 -81701.158
COORDINATE
NORTH (m) EAST (m)
SYSTEM
27
CP57 (KNOWN POINT) :
COORDINATE
NORTH (m) EAST(m)
SYSTEM
28
CP5 (KNOWN POINT)
DIFFERENCE 0 140.885
COORDINATE
NORTH (m) EAST (m)
SYSTEM
29
5.4 RESULT
30
6.0 CONCLUSION
At the end of this sitework, we all have know how the procedure of GNSS sitework. We
also know how to setup the equipment correctly. From this sitework, we know how to
convert all the data we get form the sitework to all the coordinate system such ast MRT68,
Cassini old and new, RSO old and now. We also can use TBC (Trimble Business Centre)
more faster and correctly to convert all of the data we got from the sitework.
During the processing process, we found that one of our data was missing. We have tried
to find it, but we can’t get it. That is the reason why we only have 4 CP in the TBC. We
admit our wrongdoings and our clumsiness during this sitework.
During converting our data to GDM2000, Cassini old and new, RSO Old and new, we
also found that only 3 data was fixed which is CP14, CP5 and CP54. We found this problem
happened because our base and our CP was not in the same time and date. We tried our best
to fixed the non fixed line but unfortunatelly we failed. Again, we admit our wrongdoings
during all the process.
31
APPENDIX
32
REFERENCE
(1) Unit 3: Static GPS/GNSS Methods - High Precision Positioning with ....
https://serc.carleton.edu/getsi/teaching_materials/high-precision/unit3.html.
(2) Static GPS Control Surveying | GEOG 862: GPS and GNSS for Geospatial ....
https://www.e-education.psu.edu/geog862/node/1823.
33