JSON data files for OSM Notes Viewer and AI-assisted note resolution.
This repository contains pre-calculated analytics data exported from the OSM Notes Analytics data warehouse, optimized for consumption by web viewers and AI systems.
Individual JSON files for each OpenStreetMap user, organized in a hexadecimal subdirectory structure for optimal filesystem performance:
- Structure:
data/users/{hex1}/{hex2}/{hex3}/{user_id}.json - Example:
data/users/0/3/2/421938.json - Format: Hexadecimal hash-based 3-level directory structure (modulo 4096)
- Purpose: Provides detailed statistics per user including:
- Notes created, resolved, and commented
- Application usage (mobile vs desktop)
- Resolution metrics and response times
- Historical data by year/month
- Contributor type information
Why subdirectories? With hundreds of thousands of user files, organizing them in subdirectories improves:
- Filesystem performance (faster directory listings)
- GitHub UI navigation (no truncation)
- Scalability for future growth (millions of users)
Individual JSON files for each country:
- Structure:
data/countries/{country_id}.json - Purpose: Country-level statistics including:
- Notes by country
- Resolution rates and metrics
- Application usage patterns
- Temporal resolution data
Quick lookup files for efficient data discovery:
users.json: Array of all users with basic statistics (sorted by activity)countries.json: Array of all countries with basic statistics- Purpose: Enables fast user/country discovery without loading individual files
Export metadata including:
- Export timestamp
- Total counts (users, countries, notes)
- Data version information
countries.geojson.gz: Compressed GeoJSON with country boundariesmaritimes.geojson.gz: Compressed GeoJSON with maritime boundaries- Purpose: Geographic data for map visualization
Purpose: Provide context to AI systems for note resolution assistance.
These CSV files contain notes organized by country, formatted to help AI models understand:
- Note content and context
- Geographic distribution
- Resolution patterns
- Historical data for training/context
Use Case: When an AI system needs to assist in resolving OpenStreetMap notes, these files provide the necessary context about:
- What types of notes exist in each country
- Common resolution patterns
- Geographic and cultural context
- Historical resolution data
Files are named by country ID: {country_id}_{country_name}.csv
noteLocation.csv.zip: Compressed CSV with note locations (lat/lon coordinates)schemas/: JSON Schema files for data validation (copied from OSM-Notes-Analytics)
This repository is configured for GitHub Pages. Data files are accessible via:
https://{username}.github.io/OSM-Notes-Data/data/{path}
See index.html for a complete list of available endpoints.
All data is exported from the OSM Notes Analytics data warehouse (notes_dwh database) using automated ETL processes. The export scripts are located in the OSM-Notes-Analytics repository.
Data is automatically updated via scheduled exports that:
- Extract modified data from the data warehouse
- Export to JSON files
- Validate against JSON schemas
- Commit and push to this repository
- Deploy via GitHub Pages
- JSON: All user, country, and index data
- GeoJSON: Geographic boundaries (compressed with gzip)
- CSV: Note data for AI context (organized by country)
- Schemas: JSON Schema for validation
- OSM-Notes-Analytics: Data warehouse and ETL processes
- OSM-Notes-Viewer: Web viewer that consumes this data
See LICENSE file for details.