A Three.js-based framework written in Javascript/WebGL for visualizing 3D geospatial data
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 70%
Response Time: 3d
First Timer Success: 75%
iTowns/itowns has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in iTowns/itowns respond to incoming external pull requests in approximately 80.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.9 places iTowns/itowns in the A tier.
The external contributor pull request merge rate for iTowns/itowns is 69.8%, based on public PR activity from non-core contributors.
iTowns/itowns currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A Three.js-based framework written in Javascript/WebGL for visualizing 3D geospatial data
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in iTowns/itowns.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/iTowns/itowns?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~52 hours (87% approval). Large PRs (>500 lines) take ~386 hours (31% approval). Keep your diff compact for rapid review.
https://github.com/iTowns/itowns/blob/bbdd27d9eab2c32876162b22e065c666b1674c55/examples/jsm/PointCloudHelper.js#L47C1-L68C1 This feature was already started in CameraUtils.animateCameraToLookAtTarget , This feature allows you to position the camera on coordinates or an extend. It works in both planar and globe viewers. It takes into account the loading of the DTM, which can cause the terrain to pass over the camera. There are several parameters: tilt, heading, distance, animated. It is used in GlobeControls and could also be used in PlanarControls. This is a possibility for factorization. For this, the layer must have a footprint property. I had asked @ftoromanoff to keep it in Clouds Layer. Unfortunately, I don't have time to start this factorization at the moment.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to iTowns/itowns, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of iTowns/itowns acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.8% were successfully merged into the primary branch.
iTowns/itowns has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.9 places iTowns/itowns in the Welcoming tier.
The external pull request merge rate is 69.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, iTowns/itowns currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for iTowns/itowns are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.