Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Background and Goals

Open
#6 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript

Research direction

This issue is a project-level outline rather than a self-contained task, and it names no files, tests, or entry points. Read the linked issue #3 and the referenced labs issue first; the implementation scope and completion criteria still need to be defined before work can begin.

Written by the indexing model from the issue text.

Description

issue-1

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:

  1. Creating a pipeline of minutely changeset files and turning them into a cloud native format #3
  2. Selecting the relevant files on the frontend using a UI
  3. Collecting statistics by parsing the files on the frontend and displaying them
  4. (stretch goal) Visualizing change over time inside the bounding box

Resources

[internal] https://github.com/developmentseed/labs/issues/330

@wrynearson @batpad @geohacker for adding more detail to this issue

Dominant language
TypeScript
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/osm-gradient

All issues in developmentseed/osm-gradient

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.