When to use this file
Start with a small file whose structure is known before processing thousands of points. These synthetic teaching coordinates describe four corners of a square on a UTM grid. Test column mapping, conversion and the output preview without using client data. CSV does not automatically preserve a coordinate-system definition, so the system is stated here and in the filename.
Column and example preview
The preview shows the file structure. Observation data is synthetic; a dash means a blank field.
| point_id | easting | northing | height | code |
|---|---|---|---|---|
| P1 | 500000.000 | 3300000.000 | 10.000 | SYNTHETIC |
| P2 | 500100.000 | 3300000.000 | 10.000 | SYNTHETIC |
| P3 | 500100.000 | 3300100.000 | 10.000 | SYNTHETIC |
| P4 | 500000.000 | 3300100.000 | 10.000 | SYNTHETIC |
Use the file step by step
Check the file structure
Download the UTM file and open it in a text editor or Excel. The first row contains headers; commas separate fields and periods mark decimals, without thousands separators. point_id identifies the station, easting and northing are grid coordinates, height is a teaching value, and code labels the example. Keep the source copy before making changes.
Map columns and select the system
In the batch converter map point_id to the name, easting to easting, northing to northing and height to height. Select EPSG:32636, WGS84 / UTM zone 36N, as the source. Do not infer a system from the apparent magnitude alone. These coordinates are metres, not longitude and latitude degrees.
Convert and check one point
Choose geographic WGS84, EPSG:4326, as the target and export CSV. Compare the first point with the supplied WGS84 file after matching the column names. P1 has longitude 33° because it lies on this zone’s central meridian. Check the same point in the single-point converter too. A matching filename is not a coordinate check.
Review count and location before delivery
Open the output in the file viewer. Confirm four points in the expected area and unchanged identifiers. GeoJSON and KML use longitude before latitude. This is a horizontal conversion; changing the coordinate system does not turn height into a geoid-referenced reduced level. Document the height type and vertical datum for real work.
The result to check
Expect four points, retaining identifiers P1 through P4. The square has 100-metre grid sides. Compare coordinates at the precision shown in the file; this does not establish field-survey accuracy.
Common mistakes to avoid
- Swapping easting/northing or longitude/latitude.
- Choosing the wrong zone or hemisphere.
- Treating the teaching height as a real vertical reference.
Frequently asked questions
Are these actual project points?
No. Every point is synthetic and labelled SYNTHETIC for testing the tools. Replace them with your measurements and their coordinate-system definition before professional use.
Can I open the CSV in Excel?
Yes. If it opens in one column, import the data with comma delimiters and period decimals. Keep identifiers as text when they contain leading zeroes.