lotobo/geo-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Release Geo Tools 0.2.0
Verify / verify (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
zemion
2026-09-02 12:02:09 +02:00
parent 2acdb66399
commit 3538e4e12b
29 changed files with 1352 additions and 172 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/PRIVACY-SECURITY.md
+4 -2
View File
@@ -2,6 +2,8 @@
Imported coordinates and generated exports stay in page memory. The app has no telemetry, analytics, account, persistence, map-tile request or other runtime network path. Names and properties are rendered as React text and escaped on XML export.
Text/file input is limited to 16 MiB and the common model to 200,000 coordinates. XML is rejected above 250,000 elements or 256 levels before DOM parsing; DOCTYPE, entity and XML stylesheet declarations are rejected. These controls bound supported input but are not a general XML sanitiser.
Text/file input is limited to 16 MiB and the common model to 200,000 coordinates, 20,000 geometries and 16 GeometryCollection levels. XML is rejected above 250,000 elements or 256 levels before DOM parsing; DOCTYPE, entity and XML stylesheet declarations are rejected. These controls bound supported input but are not a general XML sanitiser.
Coordinates are interpreted as WGS 84 longitude/latitude. There is no CRS transformation and the local SVG sketch is not a map projection. Distance is a spherical approximation, elevation gain/loss uses the supplied samples without smoothing, and conversion intentionally drops unsupported styles, extensions, geometry structure or properties as stated beside each result. Do not treat results as survey-grade measurements.
Coordinates are interpreted as WGS 84 longitude/latitude. There is no CRS transformation and the local SVG sketch is not a map projection. Distance is a spherical approximation, elevation gain/loss uses the supplied samples without smoothing, and conversion intentionally drops unsupported styles, extensions, properties, or flattens geometry structure where the target format cannot preserve it, as stated beside each result. Do not treat results as survey-grade measurements.
Geometry editing validates coordinate bounds, model size and recursion limits but does not repair topology, ring winding, self-intersections or semantic feature relationships. GPX import retains track geometry and available elevations in the common model; timestamps, extensions and vendor-specific track metadata are not round-tripped. The two-point ruler measures a great-circle segment only and never contacts a routing or map service.