TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: Xplore Path – Explore untidy data spread across scattered files/formats

1 pointsby offbynull4 months ago
Xplore Path is a tool for quick-and-dirty data exploration, built for messy, untidy data scattered across files and formats.<p>* Simple syntax: Query data with an intuitive, XPath-like syntax.<p>* Broad format support: Search through CSVs, XLSXs, JSONs, YAMLs, DOCXs, PDFs, XMLs, HTMLs, ...<p>* Fuzzy search support: Search using globs, regex, number ranges, or approximate string matching.<p>* Unified environment: Search through disparate files and formats within a single context.<p>* Extendable: Add functions and formats to customize to your use case (e.g. 3D scene graphs, flow cytometry, ...).<p>Xplore Path aims to be the first tool you reach for when inspecting &#x2F; exploring new data &quot;thrown over the fence&quot; by a colleague or partner. Imagine receiving a zip file containing a nested directory structure full of cryptically named CSVs, XLSXs, PDFs, JSONs, HTMLs, and maybe even a SQLite database. Instead of hopping between tools or libraries to piece it all together, Xplore Path loads everything as a hierarchy and lets you search it with XPath-like simplicity. You can explore, slice, and integrate data with an easy to use REPL that provides auto-completion.<p>The GitHub link has instructions on getting started. Please take a look and let me know your thoughts. I wrote Xplore Path over the holiday break becauause the scenario above is one I&#x27;ve commonly experienced throughout my career, especially when dealing with third parties (e.g. university labs and CROs).<p>The project is functional but still rough around the edges. Here&#x27;s what needs ironing out:<p>* Language grammar needs to be tightened up.<p>* More exhaustive testing.<p>* More exhaustive documentation (both code documentation and user documentation).<p>* Squeezing more speed (joins are especially slow).<p>* Some formats need better support &#x2F; more formats need to be supported.<p>* Some formats need functionality added to allow the user to transform how the hierarchy gets loaded.<p>The first item (grammar design) is the one I&#x27;m most inexperienced with. If any language design experts have time to kill, please feel free to review and make suggestions.

no comments

no comments