Frequently Asked Questions — Coordinate Conversion & Google Earth KML

If your site uses a local total station grid (such as a 1000, 1000 base), enter 3 or more known government control benchmarks. The software calculates scale correction and True North rotation, showing you the exact millimeter differences on each mark before exporting to Google Earth.

Yes. Field data collectors from Leica, Trimble, Topcon, and Sokkia often export comma-separated numbers without column headers. The importer lets you verify which column is Point ID, Easting, Northing, and Elevation before processing.

No. The desktop application handles 10,000+ points in under a second. You can paste large Excel sheets or drag in multi-megabyte CSV files containing entire highway traverses, cadastral boundary pegs, or topographic contour grids.

Each point is placed on Google Earth's terrain at its exact position, and its measured level appears in the balloon when you click it. The level is also kept inside the file, so it can be read back into a spreadsheet. Along a line of points you can get a level profile with chainage and grade, and the quality checks flag any level that jumps compared with its neighbours.

Yes. By grouping survey points with feature codes (like BOUNDARY, FENCE, or LOT), the software draws closed boundary outlines in Google Earth and automatically calculates boundary perimeter length and total ground area in square metres and hectares.

The conversion itself — reading your sheet, the coordinate maths and building the KML or KMZ — always runs on your own computer or in your browser. In the web app, the files you open and save are kept in your account so you can download them again from your dashboard, where you can also delete them. The Windows app sends only a short activity record (file name, number of points, coordinate system and export format), never your coordinates or photos.

Windows SmartScreen routinely shows this safety prompt on new software that isn't signed with an expensive commercial code-signing certificate yet. Click "More info" and then "Run anyway". You can also verify the official SHA-256 binary hash on GitHub.