[openstreetmap/openstreetmap-website] Guidance on Enhancing OSM Profile Pages with Contribution Data (Issue #5356)

[Emin Kocan]

### Problem

We want to enhance the OSM profile pages to include more engaging and informative features, similar to [HDYC](https://hdyc.neis-one.org/). The goal is to display user contribution summaries, activity patterns, and insights into changesets. However, we're unsure about the best approach to efficiently query and integrate this data, especially within the constraints of the existing OSM infrastructure.

Key challenges include:
1. **Data Import**: 
   - Changesets in the planet OSM files contain user data, but tools like Osmosis and Osmium cannot directly link users to contributions in a database.
   - Full history dumps provide the necessary data but are massive (~223 GB compressed, ~3.7 TB uncompressed) and complex to process.
2. **Performance**: 
   - We’re uncertain how querying user contribution data at scale would impact performance.
3. **Integration**:
   - Ideally, we want to avoid additional overhead or external systems, preferring a solution within the existing OSM infrastructure.


### Description


To achieve this, we’re considering several approaches, but we need guidance on:
- Whether anyone has implemented similar features before and has insights to share.
- The feasibility of querying contribution data directly versus preprocessing it into a database.
- How to efficiently test and benchmark the performance of querying user contribution data.
- Whether a solution can be integrated into the existing OSM infrastructure or if a separate system is necessary.

#### Questions

1. Has anyone worked on similar enhancements or features for OSM profile pages? If so, what approach did you take?
2. Are there recommended workflows or tools (e.g., Osmium, osm-history-renderer) for importing and querying user contribution data efficiently?
3. How can we test and compare the performance of different approaches without committing to a full-scale import?
4. Is it possible to leverage existing infrastructure to handle these queries, or would setting up a separate processing system be unavoidable?

We welcome any advice, insights, or references to similar projects to help us move forward. @gravitystorm @tomhughes @AntonKhorev @pa5cal

### Screenshots

_No response_

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/5356
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/5356 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20241125/151006c9/attachment.htm>