Urgent.News

What's breaking now, across thousands of outlets.

Tech

I made a tiny open dataset of which dirt bikes share plastics

I like dirt bikes and I like small data projects, so this one was bound to happen. The question behind it is simple. You find a graphics kit you like, the listing says "2024 KX450", and your bike is a 2025 KX250. Will it fit? Often it does, because manufacturers keep the same plastic panels for a few model years and share them between the 250 and the 450. I couldn't find that written down in one…

A small data project emerged from the author's dual passion for dirt bikes and tiny datasets. The underlying question was whether a graphics kit for one bike model would fit another bike model from the same manufacturer. The author discovered that manufacturers often reuse the same plastic panels for multiple model years, creating an opportunity to compile this information systematically.

The author created a GitHub repository called 'dirt-bike-graphics' where they stored the collected data. The repository currently includes information on 175 model years from 76 models and 11 brands. Each model year is grouped with a reference bike, and every shared panel across model years is included in that group. The rule is that a model year can only belong to one group to ensure accuracy.

The data is presented in two files: one for people and one for code. The 'FITMENT.md' file is a plain table that anyone can easily understand, while the 'fitment.json' file is a JSON version of the same data for developers who want to use it in their projects. The GitHub Pages feature was utilized to serve the JSON file with cross-origin access, allowing any webpage to fetch the data directly.

The author added translations of the README file in German, French, Italian, Polish, and Japanese to cater to a wider audience, each stored as separate Markdown files in the repository. The project also does not require any build step, as each translation is automatically turned into a separate page by GitHub Pages.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Transactional Outbox Pattern - Improving how we deal with atomicity

Transactional Outbox Pattern: Solving the Dual-Write Problem with Atomicity When building distributed systems, we often need to perform multiple operations as part of a single business action.

  • Transactional Outbox Pattern resolves dual-write problem in distributed systems
  • Persists event with business operation in same database transaction
  • Outbox relay reads pending events and forwards them to messaging system

More from Wednesday 21 October →