Open kamicut opened 1 year ago
@kamicut can we also structure some product goals for this? What would be a workflow, and is there a frontend envisioned for this tool?
Stated another way re: the goal of the project answering the question: "What if we use cloud native vector formats to parse the minutely replication to prepare stats in the browser?"
Additional relevant comparison stats platforms:
A pitch on OSM Tardis should include why the browser-based stats element is an advantage, how the time element is feasible and advantageous, and how/if a user-stats-focused approach is improved.
After discussion with @LanesGood, we are attempting to create a targeted frontend and workflow for the tool. It's important to focus on the advantages this tool has over other analytics tools.
The deliverables will include 2 services:
The advantage of having a cloud native format and a pipeline for generating these files can be highlighted through documentation on how to query the files over space and time. We should generate examples on how to create a stats collector for a group of users, or even distribute a CLI or SDK for interacting with the API.
This would have the same capabilities as the CLI:
Background
The goal of OSM Tardis is to answer the questions "What if we use cloud native vector formats to parse the minutely replication to prepare stats in the browser?" This would mean the user have to select a bounding box — which then allows us to use things like PMTiles & FlatGeoBuff or GeoParquet.
Goals
This has multiple components:
Resources
[internal] https://github.com/developmentseed/labs/issues/330
@wrynearson @batpad @geohacker for adding more detail to this issue