Field guide
Read the distribution without losing the records
A point plot is useful when it stays connected to the source. Use the picture to ask better questions, then check the original values before making a decision.
What this viewer helps you inspect
The survey point viewer turns a text table into a local two-dimensional distribution. It is useful for a quick handoff review: check whether points form the expected groups, locate a named point, compare its code with nearby records, or choose a subset for another task. The picture and the source table remain connected. A marker is a view of a record, not a replacement for the coordinate values or the project documentation.
Bring decimal northing and easting values in CSV or TXT. Point identifiers, elevations and descriptions are optional attributes. Missing elevation does not prevent a two-dimensional plot, and the viewer never invents a zero to fill the gap. A point without an ID can still appear if it has valid horizontal coordinates; its source line remains an unambiguous way to refer to that record within this file. XLSX workbooks are also accepted for this input: explicitly choose the worksheet, and replace formulas, dates or error cells with plain values before importing.
Confirm the coordinate columns first
A PNEZD viewer must read northing before easting, while a PENZD file puts those two positions in the opposite order. The input preview suggests recognized headings, but it cannot establish the meaning of arbitrary X and Y labels. Use the source export specification or a reliable known point to confirm the mapping. If the first record contains measurements rather than headings, select Point data explicitly so it is not accidentally treated as a header.
The unit selectors describe the values in your source. Changing them does not scale the coordinates. Both horizontal axes need a consistent unit for their relative shape to be meaningful, and elevation may use a separately stated unit. This tool displays elevation as an attribute and label; it does not turn the point list into a terrain surface, create contours or interpolate heights between observations.
Reconcile the picture with the source count
After reading the file, compare total source records with the number that have valid northing and easting. Records with missing or invalid horizontal values remain in the table and the full viewing record, but cannot receive a plotted position. A separate count makes that difference visible. Other validation problems, such as an invalid elevation, do not necessarily prevent a horizontal position; red rings identify plotted records that still have errors to review.
Coincident coordinates can produce a single visible-looking marker even when several independent records occupy that position. Duplicate point IDs also remain separate. The viewer tracks internal source-row identifiers rather than using the displayed point name as a unique database key. Click near a marker to inspect a source row, read the nearby-record count, and use the table to distinguish overlapping entries. Nothing is merged simply because the drawing looks crowded.
Find a point and follow it back to the source
Type part of an identifier in the Point ID filter. Matching is case sensitive and uses the original text, including leading zeros. Searching for 0012 is more specific than searching for 12. Combine that filter with a description or code fragment when you need a narrower view. Reset filters restores the table without changing the source, and Show all points also returns the plot to the full data extent.
The source-line button opens a detail card containing the original coordinate strings, elevation, description and raw record. Locate this point centers that record in the plot when its coordinates are valid. Clicking a plotted marker moves the table to the page containing its source row. This works even when the file is much longer than the 25 rows displayed on one table page. Pagination affects the interface, not the data available for selection or export.
Use descriptions to understand groups
Description values often distinguish control points, edges, trees or other recorded features. The viewer assigns a stable color from a small palette to each exact description and lists the most frequent groups. Colors can repeat; the actual code and source record remain the authority. If a file contains many unique descriptions, type a fragment into the description filter instead of relying on the short legend to represent every group.
Filtering is a reversible viewing choice. It does not delete records or certify that the remaining points belong to a single physical feature. A matching word may occur in several codes, so read the resulting table before selecting all filtered records. There is no automatic line connection. Alphabetical point names, row order and shared descriptions do not establish a boundary, breakline or legal parcel edge.
Why the points sometimes look like one dot
The full extent must include every coordinate-valid record. A far-away point can make a nearby cluster occupy only a few pixels. That does not mean the cluster was discarded. Compare the displayed minimum and maximum eastings and northings with the expected project range. A separated location could be intentional, such as an external control point, or could reveal a unit, column or transcription issue that needs investigation.
Filter a known code or identifier, then choose Fit filtered to inspect that group at a useful scale. Select a few records and use Fit selected when you already know which area matters. Zoom buttons enlarge or reduce the current view; drag the plot to pan. With the plot focused, arrow keys pan and plus or minus changes zoom. Return to Show all points whenever you need to see the complete distribution again.
Labels help inspection without controlling export
Choose point IDs or elevations as labels. The plot draws at most 120 labels that are visible in the current viewport to keep dense files usable. Every coordinate-valid filtered record still contributes a marker, including points without a displayed label. An empty elevation has no elevation label, and text can overlap when points are close. Search, filter and zoom to read a small group rather than expecting every label in a large survey to fit at once.
The counters distinguish filtered coordinate-valid records, records currently inside the viewport and the number of labels drawn. Panning a point outside the view does not remove it from the source. Neither label limits nor the table page size restrict the selected-point export. For a complete handoff, check the selection count rather than estimating the number of records from visible dots or readable names.
Select records and make an explainable export
Use the table checkboxes to select individual source records, or select every record matching the current filters. Selection persists when filters change. A counter tells you how many selected records are currently hidden, so an export cannot quietly surprise you with a larger set. Clear selection removes the selection only. Clear data in the input workspace releases the current source and results from the session.
The selected CSV retains every original source column in source order, including additional fields and duplicate IDs. It uses commas even when the input used another supported delimiter, and quotes fields where needed. Selected invalid rows are retained too; their presence should be intentional and reviewed. This raw data export does not apply spreadsheet formula protection. Use the converter to make a separate protected review copy if that is required, while preserving the raw point file.
Save a picture with the right expectations
Download current plot produces a PNG of the current viewport, including direction labels, the plotted count, selection count and units. It is a schematic review image, not a georeferenced raster, certified plan or finished drawing. Keep the point file alongside it so another person can inspect the actual values. The full viewing JSON retains the complete source, findings, selected row IDs and the current view settings for a more detailed record.
No satellite imagery or third-party basemap is loaded. A northing/easting table does not, by itself, identify a real-world location: the coordinate reference system, zone, datum and units are separate information. Plotting an internally consistent shape cannot prove that it is correctly located on Earth. Mapping to geographic coordinates is outside this viewer. It also does not compute areas, recognize parcel boundaries, or certify the measurement quality of a point.
Know the supported file and session limits
This version accepts UTF-8 CSV and TXT with comma, semicolon or tab delimiters, up to 10 MiB and 100,000 records. It rejects unsupported encodings rather than showing guessed text. Malformed quoting and inconsistent columns are reported against source lines. The file is processed locally in a worker, and you can cancel a read without losing the input. Split larger jobs at the source and keep clear batch names.
Your point data stays in the current browser session. It is not uploaded to a map service or saved in browser storage. Downloaded files are the copies you choose to keep. The local transfer buttons can send selected rows to the converter or the full source to the checker in another tab. Keep the sending tab open until receipt is confirmed, then verify the receiving tool’s mapping before running its next operation.