- Zero-Upload SQL Data Exploration: Querying RFC-4180 CSV, JSONL logs, and Parquet schemas directly in browser RAM without uploading production data to external servers.
- One-Click PII Redaction for Safe Bug Reports: Automatically masking email addresses and IPv4 octets before exporting filtered CSV or JSONL subsets.
- Haversine GPS Timestamp Interpolation: How to merge split Garmin/Wahoo
.gpxrides and synthesize missing<time>tags so Strava accepts the upload. - Location Privacy Trimming & EXIF Scrubbing: Trimming start/finish home coordinates from GPX routes and stripping smartphone GPS metadata from photos.
Software engineers, data analysts, and telemetry enthusiasts constantly work with structured files that contain sensitive personal information—from production database CSV exports containing customer emails and IP addresses to GPS activity logs that start and end at a user's front door. Uploading these files to random server-side converters violates corporate data governance and personal privacy. Here is how to run these data engineering workflows 100% locally in your browser on Vexolora.online.
1. Querying CSV, JSONL & Parquet Schemas Locally with SQL
With the Local-First Parquet, JSONL & CSV SQL Explorer, your file is read into a local JavaScript array via an RFC-4180 state-machine parser that properly handles quoted commas and escaped double quotes. The tool immediately profiles every column's distinct cardinality and null percentage, lets you run SELECT ... WHERE ... ORDER BY ... LIMIT queries, and includes a 1-Click Mask PII toggle that redacts email usernames (s***@enterprise.io) and IPv4 addresses (198.51.xxx.xxx) before you export a clean CSV or JSONL reproduction file.
2. Merging Split GPX Tracks & Synthesizing Missing Strava Timestamps
In the GPX Track Merger, Strava Timestamp Synthesizer & Home Privacy Trimmer, you can select multiple local .gpx files and combine all <trkpt> nodes into a single GPX 1.1 segment. When you enable Synthesize Missing Timestamps, the engine applies the Haversine great-circle formula between each consecutive coordinate pair and interpolates sequential ISO-8601 timestamps matching your target speed in km/h.
3. Protecting Home Coordinates in GPX Routes & Photo EXIF Headers
Before exporting your merged ride from the GPX Merger, set the Home Privacy Trim (m) input to 200 or 500 meters to automatically strip trackpoints inside your start and finish radius. Then, pass any accompanying activity photos through the Lossless 300 DPI & EXIF Privacy Scrubber to strip embedded JPEG APP1 GPS latitude/longitude coordinates, or inspect binary API attachments in the Base64 to PDF Debugger.