The CogoKit toolbox

All Tools

Practical tools for the work between the field and CAD. Choose a task and start with the file you already have.

Choose by task

36 available tools

36 tools

Not sure which tool fits?

Compare input requirements, recommended steps and output checks by workflow.

COGO Calculators for Survey Coordinates →

Choose coordinate geometry tools for bearings, distances, intersections, areas, offsets and point generation with explicit axes and reviewable results.

Survey Point File Tools →

Choose a point-file workflow for checking, merging, renumbering, editing codes and preparing traceable CSV or CAD handoffs.

Survey Quality Control Tools →

Separate file checks, design deviations, closure and control residuals. Choose the evidence and comparison needed for a defensible survey review.

Construction Staking Calculations →

Plan straight grades, station offsets, circular curves and offset lines with explicit references, point schedules and independent checks.

Choosing surveying tools for a complete file workflow

Start with the task, then choose a calculator

This directory groups the available surveying tools by the result you need: a checked point file, a geometric calculation, a staking schedule, a quality review, or a map and terrain handoff. Search a familiar term such as DXF, bearing, elevation, or LandXML, then narrow the list by task. The categories help you choose an entry point; they do not change any uploaded data. If you are unsure which tool fits, begin with the point file checker and read the guide on the destination page before calculating. Every tool page explains its accepted inputs, output conventions, worked example, and limits.

Check a received point file before editing it

A file that opens successfully can still contain missing coordinates, repeated identifiers, shifted columns, or descriptions with embedded commas. The checker preserves the source records and identifies the rows that need attention. The viewer adds a planar picture so you can inspect the distribution and locate a particular record. Neither result identifies the coordinate system for you. Keep the original file, confirm its axis order with the sender, and record the project reference. A missing elevation remains missing, while a zero elevation is an actual supplied value. These two conditions must remain distinguishable when the file moves into another calculation.

Choose a format change or a coordinate change

Use the point file converter when the coordinates are already correct but another program expects a different field order, delimiter, or number format. PNEZD and PENZD describe column order; switching between them does not establish a new reference frame. Use the batch coordinate converter only when you know the supported source and target coordinate systems. A local rotation or translation belongs in the known-parameter transformation tool. If parameters must be estimated from matching controls, use the two-dimensional fitting tool and reserve independent check points. These operations solve different problems, even though each can produce a new coordinate table.

Keep edits traceable through a cleanup workflow

Merging, renumbering, code editing, filtering, and duplicate review belong to a cleanup workflow. Map each source separately before merging and resolve identifier conflicts deliberately. Review an old-to-new identifier list before applying renumbering, especially when control points must keep their names. Code mappings operate on the descriptions you provide; they do not translate survey codes with the interface language. Filtering should account for both selected and unselected records. Nearby points may represent different physical features, so proximity alone is not an instruction to delete one. Save the change report alongside the cleaned file so another person can reconstruct what you chose.

Match the geometry tool to the known information

Use inverse calculations when you have two coordinates and need their direction and distance. Use forward calculations when an origin, direction, and horizontal distance are known. An intersection can return more than one valid candidate, and selecting a candidate requires project context. A point-to-line offset distinguishes an infinite reference line from a finite segment. An area calculation needs vertices in the actual boundary order; an unordered scatter of points is not a boundary. The angle converter helps distinguish decimal degrees, ordinary degrees-minutes-seconds, compact angle strings, and gon before those values enter another calculation. Explicit formats prevent plausible but wrong results.

Prepare staking schedules with explicit limits

Straight-grade elevations, station-offset calculations, curve elements, curve staking, and parallel offsets support related but distinct preparation tasks. Check the start station, baseline direction, interval, and endpoint behavior before exporting a schedule. Cross-section offsets use the direction from A toward B, with negative values on the left and positive values on the right. A circular curve schedule uses distances along the arc, which differ from adjacent chords. Known ground and grid distances also require the correct interpretation of the supplied combined factor. These pages prepare numerical schedules; they do not connect to an instrument or confirm that a point was staked in the field.

Separate observation reduction from adjustment

The observation reduction tool starts with slope distance, a zenith or vertical angle, instrument height, and target height. It calculates the horizontal component and the ground height difference using the declared convention. The level run tool instead processes the order of backsights, intermediate sights, and foresights. Traverse review starts from directions and horizontal distances. When a closure can be evaluated, inspect the original discrepancy before choosing a supported distribution method. Adjusted coordinates do not erase the original observations or establish a tolerance by themselves. Use a tolerance and acceptance procedure from the actual project, rather than treating the displayed decimal places as an accuracy statement.

Compare the right design representation

For matching design and measured point identifiers, use the point comparison tool and review unmatched or ambiguous pairs. When the measured location has no matching design point but lies on a design TIN, use the surface elevation tool. First inspect the LandXML object, original triangle references, units, and excluded areas. Surface queries use the original mesh rather than constructing a replacement from its vertices. Points outside coverage, inside excluded holes, or within conflicting triangles remain unresolved. Terrain sections use the same original surface information to retain triangle crossings and gaps. A height difference is not an earthwork volume, and a displayed profile does not fill missing terrain.

Check the destination before exporting CAD or maps

A DXF handoff and a KML handoff require different coordinates and geometry choices. Supported DXF output creates ordinary points, labels, and explicitly selected paths for CAD. KML uses verified WGS84 longitude and latitude, with a declared altitude mode. Projection changes do not automatically transform height datums or convert feet to metres. Declare the unchanged height unit when continuing from projection conversion. Non-ground KML modes require metre heights; ground-clamped output omits altitude coordinates while the original height remains in the source report. When extracting an incoming file, review the unsupported-entity list so that a successful point export is not mistaken for a complete conversion of the drawing.

Test the complete handoff on a small known file

Before a large batch, use a few known points with a deliberately missing height, a leading-zero identifier, and a description containing punctuation. Check the preview, download the result, and inspect it in the receiving application. For example, a formatting task can follow checker, converter, then viewer; a terrain review can follow LandXML viewer, surface query, then sections. Keep record counts, units, chosen mappings, and source revision together. Session transfers carry data locally between supported tools, but they are not a backup. Keep the source tab open until transfer finishes and save the report you need before clearing the session or closing the browser.

Questions about choosing a tool

Which tool should I use for a file that will not import?

Start with the point file checker. Confirm the delimiter and column meanings, inspect the reported source rows, then use the converter if the destination needs another field order. Changing coordinate systems is a separate operation.

Can I upload an Excel workbook?

Tools that list XLSX support let you choose the worksheet explicitly. Replace formulas, dates, and error cells with verified plain values first. Check leading-zero identifiers and coordinate columns after reading the sheet.

Does a clean result prove my survey is accurate?

No. File validation checks structure, and calculations use the supplied assumptions. Instrument condition, reference control, observation quality, boundary meaning, and project acceptance still need the appropriate independent review.

Are my coordinate files sent to a server?

Survey file parsing and calculations run in your browser. Supported transfers use a temporary local browser channel. Downloaded files are saved through your browser; project coordinates are not placed in the transfer URL or automatically stored as a saved project.

Can I use the tools with unknown coordinates or units?

You can inspect the source structure, but a meaningful geometric or projection result needs verified context. Ask the sender for axis order, horizontal units, height units, reference frame, and revision. Do not choose a plausible default solely because the numbers look reasonable.

Why does a downloaded report contain an error row?

Retaining an invalid row makes the missing result visible and keeps source counts traceable. Review the status and blank result fields. Correct the input and recalculate, or document a deliberate exclusion using a tool that supports reviewed selection.

Start with a traceable check.

Use your own UTF-8 file, paste a few records, or explore the synthetic example. Field order and units always need your confirmation. A clean file check describes the structure of the data; it does not certify survey accuracy.

Browse the field guides