LP1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 36

COLLEGE OF BUILT ENVIRONMENT

DIPLOMA OF SCIENCE GEOMATIC (AP120)

GEODETIC STUDIES (GSS230)

Prepared for:

DR. MUHAMMAD FAIZ PA’SUYA

Prepared by:

NAME UITM NO

MUHAMMAD HAZIM BIN AZMI 2022617218

ABDUL LOKMAN HAKIM BIN AB RAHMAN 2022832144

HAIKAL IKHWAN BIN ABDUL AZIZ 2022492362

SAMANTHA CHIN 2022896586

NURQISTINA ALLISYA BINTI ROHAIZAD 2022864122

Group:

RCAP1203G
TABLE OF CONTENT

1.0 Introduction

1.1 GNSS Static


1.2 Objective
To establish geodetic control network using different method

2.0 Members

Picture, name, student id

3.0 Equipment and software

4.0 Methodology

4.1 Explain the procedure of GNSS static survey

4.2 Show the steps of processing in TBC software

5.0 Result and Analysis

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

Log sheet of GNSS observation at each station


ABSTARCT

As part of our syllabus in Geodetic Studies (GSS230), we are conducting a fieldwork


tasks which is to establish geodetic control network. The first task is to use a point fix
at a known station (JUPEM pillar) and the second is to use a point fix at Arau
Continuously Operating Reference Station (CORS). This tasks is done in UiTM Arau,
Perlis using the CRM point that is provided by our lecturer. In this tasks we also need
to convert all the coordinate to MRT68, Cassini Old and New and RSO Old and New
using GDTS software.

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.

Thus, we would like to acknowledge our lecturer, Dr Muhammad Faiz Bin


Pa’suya. Without is encouragement and guidance, we couldn’t finish this task within
the time given. We would like to thank him for teaching us throughout this task.

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

1.1 GNSS STATIC

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

To establish geodetic control network using different method .

1
2.0 MEMBERS

THE TEAM

ABDUL LOKMAN HAKIM NURQISTINA ALLISYA SAMANTHA CHIN


BIN AB RAHMAN BINTI ROHAIZAD
2022896586
2022832144 2022864122

MUHAMAD HAZIM BIN HAIKAL IKHWAN BIN


AZMI ABDUL AZIZ
2022617218 2022492362

2
3.0 EQUIUPMENT AND SOFTWARE

Survey Equiment and Software Used

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).

GNSS Base Station GNSS base station is to serve as a fixed


reference point with accurately known
coordinates.

Antenna Receives satellite signals and plays a critical


role in the accuracy of the GNSS
measurements. Antennas can be of different
types, including single-frequency and multi-
frequency, and may have specific
characteristics for different surveying
applications.

3
Tripod Stand Supports the GNSS receiver and provides
stability during the survey. Tripods are
essential for stationary or static surveys.

Bipod Similar to a tripod, a bipod is a two-legged


support that is more portable and suitable
for quick setups in dynamic surveying
environments.

Survey Pole Used to mount the GNSS antenna at a


specified height above the ground to ensure
accurate measurements, especially when
conducting ground surveys.

Field Controller A handheld device or tablet that runs


surveying software, enabling the user to
control the GNSS receiver, collect data, and
input survey parameters. It may have a
touchscreen, keyboard, and other
input/output features.

4
Measuring Tape This typically use for measuring height of
our instrument such as South base and the
Topcon gnss receiver that we used

Tribrach It typically consists of three leveling


screws and a circular bubble level. The
tribrach is mounted on a tripod, and the
surveying instrument is then mounted on
the tribrach.

Trimble Business Center Trimble Business Center (TBC) is a


software package designed for surveying
and geospatial professionals, providing a
range of functions to process, analyze,
and manage survey data.

5
ToRinex To convert any data sth to any format that
available in it so the data can be process
later

GDTS This software use for converting a map


projection to another kind of map projection

Magnet Tools allows users to process and adjust survey


data collected from total stations, GNSS
receivers, and other surveying instruments.
It includes features for importing,
managing, and analyzing field data.

6
4.0 METHODOLOGY

4.1 PROCEDURE OF GNSS STATIC SURVEY

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.

iii. Data processing

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

Written report will be done by when finish all the sitework.

8
4.1.3 Data Processing

1. We use software Trimble Business Centre (TBC) to


process all the data that we has collected during observation.

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

5.1 CONVERT ALL COORDINATE

KNOWN STATION

CP14

COORDINATE LATITUDE LONGITUDE HEIGHT (m)


SYSTEM
GDM2000 06 26 58.53870 100 16 52.73994 20.181
MRT68 06 27 00.14352 100 16 57.33670 34.631

COORDINATE NORTH (m) EAST (m)


SYSTEM
Cassini (new) 53590.636 m -39420.848 m

Cassini (Old) 53626.730 -42280.310


MRSO(new) 716332.245 1299206.356
MRSO (Old) 714005.210 255717.409

CP57

COORDINATE LATITUDE LONGITUDE HEIGHT (m)


SYSTEM
GDM2000 06 26 46.65023 100 16 41.89617 13.262
MRT68 06 26 48.25423 100 16 46.49147 27.716

COORDINATE NORTH (m) EAST (m)


SYSTEM
Cassini (new) 53225.664 m -39754.238 m

Cassini (Old) 53274.842 -39613.327


MRSO (new) 716320.546 1299195.296
MRSO (Old) 713641.739 255382.435

17
CP5

COORDINATE LATITUDE LONGITUDE HEIGHT (m)


SYSTEM
GDM2000 06 27 06.73822 100 16 35.42398 3.837
MRT68 06 27 08.34371 100 16 40.01850 18.312

COORDINATE NORTH (m) EAST (m)


SYSTEM
Cassini (new) 53842.840 m -39952.690 m

Cassini (Old) 53892.064 -39811.805


MRSO (new) 660210.085 1298602.417
MRSO (Old) 714259.710 255186.682

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

COODINATE SYSTEM NORTH (m) EAST (m)


Geocentric Cassini 53591.766 -39419.920
Cassini (Old) 53591.792 -39423.739
Geocentric MRSO 713962.258 255378.809
MRSO (Old) 713957.800 255573.376

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

COODINATE SYSTEM NORTH (m) EAST (m)


Geocentric Cassini 53224.201 -39752.285
Cassini (Old) 53224.204 -39756.079
Geocentric MRSO 713591.734 255239.485
MRSO (Old) 713596.191 255044.919

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

COODINATE SYSTEM NORTH (m) EAST (m)


Geocentric Cassini 53844.000 -39951.756
Cassini (Old) 53843.991 -39955.586
Geocentric MRSO 714216.732 254848.147
MRSO (Old) 714212.275 255042.714

20
5.2 ANALYSIS RESULT

KNOWN POINT :

COORDINATE LATITUDE LONGITUDE HEIGHT STANDARD


SYSTEM ERROR
CP57 N6°26'46.65023" E100°16'41.89617" 28.089 m ΔEasting = 0.004 m

ΔNorthing = 0.003 m

ΔElevation = 0.008 m

CP14 N6°26'58.53870" E100°16'52.73994" 35.005 m ΔEasting = 0.003 m

ΔNorthing = 0.002 m

ΔElevation = 0.007 m

CP5 N6°27'06.73822" E100°16'35.42398" 18.685 m ΔEasting = 0.004 m

ΔNorthing = 0.003 m

ΔElevation = 0.008 m

21
CORS ARAU :

COORDINATE
HEIGHT
SYSTEM LATITUDE LONGITUDE
(M)
(GDM2000)

CP14 6°26'56.97166"N 100°16'48.05956"E 18.146

CP57 6°26'44.99889"N 100°16'37.25153"E 7.999

CP5 6°27'05.17035"N 100°16'30.74573"E 1.767

22
5.3 COMPARE AND EXPLAIN THE DIFFERENCE

5.3.1 MRT68 VS GDM2000

CP14 (KNOWN POINT) :

COORDINATE LATITUDE LONGITUDE HEIGHT


SYSTEM
GDM2000 06 26 58.53870 100 16 52.73994 20.181
MRT68 06 27 00.14352 100 16 57.33670 34.631
DIFFERENCE 1.6” 4.6” 14.45
DIFFERENCE (M) 48 m 138 m

CP14 (CORS ARAU) :

DATUM LATITUDE LONGITUDE HEIGHT (m)

GDM 2000 6°26'56.97166"N 100°16'48.05956"E 18.146

MRT 68 6°26'58.57639"N 100°16’52.65570”E 32.600

Differences 49.508 142.000 14.454

CP57 (KNOWN POINT) :

COORDINATE LATITUDE LONGITUDE HEIGHT


SYSTEM
GDM2000 06 26 46.65023 100 16 41.89617 13.262
MRT68 06 26 48.25423 100 16 46.49147 27.716
DIFFERENCE 1.6” 4.6” 14.454
DIFFERENCE (M) 48 m 138 m

23
CP57 (CORS ARAU) :

DATUM LATITUDE LONGITUDE HEIGHT (m)

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

CP5 (KNOWN POINT) :

COORDINATE LATITUDE LONGITUDE HEIGHT


SYSTEM
GDM2000 06 27 06.73822 100 16 35.42398 3.837
MRT68 06 27 08.34371 100 16 40.01850 18.312
DIFFERENCE 1.61” 4.59” 14.475
DIFFERENCE (M) 48.3 m 137.7 m

CP5 (CORS ARAU) :

DATUM LATITUDE LONGITUDE HEIGHT (m)

GDM 2000 6°27’ 05.17035”N 100°16'30.74573"E 1.767

MRT 68 6°27’06.77575” N 100°16’35.33963” E 16.246

Differences 49.667 141.667 14.479

24
5.3.2 RSO OLD VS RSO NEW

CP14 (KNOWN POINT) :

COORDINATE SYSTEM NORTHING EASTING

RSO OLD 714005.210 255717.409

RSO NEW 716332.245 1299206.356

DIFFERENCE 2327.035 1043488.947

CP14 (CORS ARAU) :

COORDINATE
NORTH (m) EAST (m)
SYSTEM

RSO OLD 714212.275 255042.714

RSO NEW 714216.732 254848.147

Differences -4.457 194.567

CP57 (KNOWN POINT) :

COORDINATE SYSTEM NORTHING EASTING

RSO OLD 713641.739 255382.435

RSO NEW 716320.546 1299195.296

DIFFERENCE 2678.807 1043812.861

25
CP57 (CORS ARAU) :

COORDINATE
NORTH (m) EAST (m)
SYSTEM

RSO OLD 713957.800 255573.376

RSO NEW 713591.734 255239.485

Differences 366.066 333.891

CP5 (KNOWN POINT) :

COORDINATE SYSTEM NORTHING EASTING

RSO OLD 714259.710 255186.682

RSO NEW 660210.085 1298602.417

DIFFERENCE -54049.625 1043415.735

CP5 (CORS ARAU) :

COORDINATE
NORTH (m) EAST (m)
SYSTEM

RSO OLD 714212.275 255042.714

RSO NEW 714216.732 254848.147

Differences -4.457 194.567

26
5.3.3 CASSINI OLD VS CASSINI NEW

CP14 (KNOWN POINT) :

COORDINATE SYSTEM LATITUDE LONGITUDE

CASSINI OLD 53590.636 -42280.310

CASSINI NEW 53590.636 -39420.848

DIFFERENCE 0 -81701.158

CP14 (CORS ARAU) :

COORDINATE
NORTH (m) EAST (m)
SYSTEM

Cassini OLD 53591.792 -39423.739

Cassini NEW 53591.766 -39419.920

Differences 0.026 -3.819

27
CP57 (KNOWN POINT) :

COORDINATE SYSTEM LATITUDE LONGITUDE

CASSINI OLD 53274.842 -39613.327

CASSINI NEW 53225.664 -39754.238

DIFFERENCE -49.178 -140.911

CP57 (CORS ARAU) :

COORDINATE
NORTH (m) EAST(m)
SYSTEM

Cassini OLD 53224.204 -39756.079

Cassini NEW 53224.201 -39752.285

Differences 0.003 -3.794

28
CP5 (KNOWN POINT)

COORDINATE SYSTEM LATITUDE LONGITUDE

CASSINI OLD 53842.840 -39811.805

CASSINI NEW 53842.840 -39952.690

DIFFERENCE 0 140.885

CP5 (CORS ARAU)

COORDINATE
NORTH (m) EAST (m)
SYSTEM

Cassini OLD 53843.991 -39955.586

Cassini NEW 53844.000 -39951.756

Differences -0.009 -3.83

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.

(3) Lesson 7: Static Global Positioning System Surveying. https://www.e-


education.psu.edu/geog862/print/l7.html.

33

You might also like