Neatbo.

Local track, region and mesh delivery guide

Inspect GPX elevation, reduce track point counts, join CSV points to GeoJSON regions and split STL components under explicit geometry contracts.

Updated 6 min read

Inspect distance and elevation per original segment

Load one GPX 1.0/1.1 file up to 10 MiB and 50,000 track/route points. Distances use horizontal Haversine with mean Earth radius 6,371,008.8 m. Segments are not joined across gaps. The SVG plots raw known elevation; missing elevations remain missing and ascent/descent uses adjacent known values.

This is not ellipsoid survey distance or terrain length. GPS noise is not corrected. Stored timestamps require an explicit timezone and must not decrease within a segment. Export complete point metrics with the plot when another reviewer needs the measurements.

Read each report under its declared model
DeliverableRuleRetained evidence
GPX profileHorizontal sphere, separate segmentsComplete point metrics
Simplified GPXLocal planar error and endpoint constraintsOriginal nodes and retained indices
Region membershipValidated planar rings and explicit boundary policyAll matches and original CSV columns
STL component ZIPExact shared whole edgesTriangle blocks/tokens and source indices

Fit a point budget without replacing retained nodes

Choose a total target that can retain every segment endpoint. Simplification preserves the original retained XML point nodes, timestamps, namespaces and extensions. Its local equirectangular metric applies only within a five-degree extent in each coordinate, latitude ±80°, without an antimeridian crossing.

The report records retained indices and measured point-to-retained-segment deviation. If a required deviation limit cannot be met under the target, the whole run fails. One file supports up to 10,000 points and ten million distance evaluations; a successful point budget does not establish compatibility with a GPS device protocol.

Declare holes, boundaries and overlapping region policy

Supply exactly one CSV and one Polygon/MultiPolygon GeoJSON, at most 5 MiB each. Set longitude/latitude columns, a region-name property and include/exclude boundary policy. Multiple matches can be kept, reduced to the first or rejected explicitly.

The supported model is planar WGS84/CRS84 longitude/latitude, latitude ±85°, without an antimeridian crossing. Rings, holes and MultiPolygon interiors must pass topology checks. Candidate complexity is bounded before joining; no partial success is reported. JSON retains complete matches while CSV appends membership columns without overwriting original headings.

Split STL by exact whole shared edges

Binary or ASCII STL components are formed by exact shared-edge connectivity. Touching at a single point does not connect components. Binary output retains the original 50-byte triangle blocks and 80-byte header with an updated triangle count; ASCII output retains numeric tokens.

This is not fuzzy welding or semantic cutting. Coordinates, normals and triangle attributes remain unchanged, and nonmanifold edges are reported without repair. A file up to 30 MiB supports 100,000 triangles, 1,000 components and 40 MiB combined output; the ZIP includes the source-triangle index.

Keep the source and complete outputs

A plot or first-200-row table is a review surface. Download the full metrics, simplified GPX, membership report or component ZIP as appropriate. Correct invalid topology, unsupported extents or exceeded budgets before rerunning.

  • Check the declared coordinate model and supported extent.
  • Keep the full report with the delivered file.
  • Retain originals before importing simplified tracks or split meshes.

References

Tools in this category

Expand a tool to see its steps, options and supported formats, then open its workspace.

GPX distance and elevation profilePlot local GPX elevation against per-segment horizontal distance and export exact point metrics.

Read track segments and routes without online maps. Each segment starts at zero distance, missing elevation breaks the curve, and optional timestamp differences remain explicit. Download the profile SVG and complete point JSON/CSV.

Steps

  1. Choose a GPX with track segments or routes.
  2. Inspect the elevation profile and per-segment distance metrics.
  3. Download full SVG, JSON and CSV outputs.

Capabilities and limits

  • One GPX1.0/1.1 up to 10 MiB, 50,000 track/route points, 2,000 segments, XML depth32 and 200,000 elements.
  • Distances use spherical horizontal Haversine with mean Earth radius6,371,008.8m, including date-line crossings. They are not ellipsoid survey distances or 3D terrain length. Elevation is raw, with ascent/descent only between adjacent known values; GPS noise is not corrected. Timestamps require an explicit timezone and millisecond-or-less precision; decreasing stored times in a segment fail.
Open GPX distance and elevation profile →
GPX point-budget simplificationReduce GPX tracks to a specified total point budget while preserving original nodes and segment endpoints.

Create a track that meets a device point limit. Selected original XML nodes keep coordinates, elevation, time and namespaced extensions. Deterministic maximum-error subdivision preserves segment endpoints; the full report maps retained indices and measures actual deviation.

Steps

  1. Choose the GPX and set a total maximum point count.
  2. Choose whether to report deviation or require a maximum deviation.
  3. Review retained indices and measured error, then download the simplified GPX and reports.

Available options

Maximum total points
500
Error policy
Report measured deviation · Require maximum deviation
Required deviation bound (m)
10

Capabilities and limits

  • One GPX1.0/1.1 up to 10 MiB, 10,000 points, 2,000 segments, depth32, 200,000 XML elements and 10 million distance evaluations. The total point target must cover every segment's mandatory endpoints.
  • Local equirectangular metric with mean Earth radius6,371,008.8m and mid-bounds origin; extent at most5° in each coordinate, latitude within±80°, no antimeridian crossing. Deviation is point-to-retained-segment in this declared plane, not a global geodesic guarantee. Required error bound fails if the target cannot satisfy it. No GPS device protocol compatibility is promised.
Open GPX point-budget simplification →
Assign CSV points to GeoJSON regionsAssign local CSV coordinates to Polygon or MultiPolygon regions with explicit hole, boundary and multiple-match policies.

Add spatial region membership to every input row. Choose coordinate columns and a region-name property, then select boundary and overlap policies. A full JSON report preserves raw values and all matches; spreadsheet-safe CSV appends uniquely named status, region-list and feature-index columns.

Steps

  1. Select one CSV and one GeoJSON file.
  2. Set longitude/latitude columns, region-name property and boundary/multiple-match policies.
  3. Review matched, unmatched and multiple statuses; download full CSV/JSON reports.

Available options

Longitude column
lon
Latitude column
lat
Region-name property
name
Boundary policy
Include boundary · Exclude boundary
Multiple-region policy
Keep all · First in input order · Fail on multiple matches

Capabilities and limits

  • Exactly one .csv and one .json/.geojson, 5 MiB each/10 MiB total; 10,000 point rows, 100 region features, 10,000 edges, 2 million topology-validation operations, 10 million candidate point-edge tests, 100,000 matches and 8 MiB match text. Complexity is checked before joining; no partial-success output.
  • Finite planar longitude/latitude WGS84/CRS84 with latitude within±85°; no antimeridian crossing. Rings must be closed and nonselfintersecting, holes strictly inside and disjoint; MultiPolygon interiors cannot overlap. Boundary tolerance is1e−10°; near-touching invalid geometry rejects. Region-name value must be string/number. This reads GeoJSON, not SHP, and never calls geocoding or map services.
Open Assign CSV points to GeoJSON regions →
Split disconnected STL componentsSplit binary or ASCII STL by exact shared-edge connectivity while retaining original coordinates, normals and triangle data.

Recover disconnected parts from one STL. Whole matching undirected edges connect triangles; a single touching vertex, geometric intersection or merely nearby coordinates do not. Each component stays at its original position and gets a source triangle-index/bounds map.

Steps

  1. Choose the local STL.
  2. Inspect component counts, triangle counts and original bounds.
  3. Download the component ZIP and complete source-index reports.

Capabilities and limits

  • One STL up to 30 MiB, 100,000 triangles, 1,000 components and 40 MiB combined output. Nonfinite or degenerate triangles and inconsistent binary sizes fail. ASCII coordinates must support finite double arithmetic and have magnitude at most1e100.
  • Binary output copies each original50-byte triangle block, including normal and attribute bytes; the original80-byte header is retained with a new count. ASCII output retains facet numeric tokens, avoiding float32 precision loss. Negative zero is normalized only for connectivity keys. No fuzzy welding, repair, semantic cutting or automatic part repositioning; nonmanifold edges are reported without repair.
Open Split disconnected STL components →

Tools used in this article

GPX distance and elevation profile →Plot local GPX elevation against per-segment horizontal distance and export exact point metrics.GPX point-budget simplification →Reduce GPX tracks to a specified total point budget while preserving original nodes and segment endpoints.Assign CSV points to GeoJSON regions →Assign local CSV coordinates to Polygon or MultiPolygon regions with explicit hole, boundary and multiple-match policies.Split disconnected STL components →Split binary or ASCII STL by exact shared-edge connectivity while retaining original coordinates, normals and triangle data.