Navara is a highly extensible 3D map engine. Load a wide range of GIS data, from satellite imagery and terrain to 3D city models and vector data, then freely layer your own visualizations on top.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 100%
Response Time: 1h
First Timer Success: 100%
maplibre/navara has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in maplibre/navara respond to incoming external pull requests in approximately 1.2 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 73.0 places maplibre/navara in the S tier.
The external contributor pull request merge rate for maplibre/navara is 100.0%, based on public PR activity from non-core contributors.
maplibre/navara currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Navara is a highly extensible 3D map engine. Load a wide range of GIS data, from satellite imagery and terrain to 3D city models and vector data, then freely layer your own visualizations on top.
Collaborative maintainer environment in maplibre/navara. Reviews community pull requests with focus on project quality.
Discussions in maplibre/navara focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/maplibre/navara?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~6 hours (45% approval). Keep your diff compact for rapid review.
Motivation SunLightOptions.intensity is documented only as "Higher values result in brighter light. Default: 1", and every example uses 1.0. But three.js shades diffuse materials with BRDF_Lambert = albedo * RECIPROCAL_PI, so intensity 1 renders a fully sunlit surface at albedo / π — about 32% brightness. The photorealistic path hides this behind the atmosphere's physical irradiance and tone mapping. Without them, the docs lead straight to a muddy basemap with nothing to suggest why. intensity: Math.PI cancels the factor. Proposed solution Document the caveat on SunLightDesc.intensity and AmbientLightDesc.intensity (+ ja): without the atmosphere and tone mapping, use Math.PI for true albedo. Replace the "If you are not using the atmosphere system, use AmbientLightDesc and LightProbeDesc instead" note in Light Desc/about.md with a working recipe. SunLightDesc works without the atmosphere and keeps directional shading and CSM shadows: view.addLight({ sun: { applyColor: true, int
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 maplibre/navara, 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 maplibre/navara acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
maplibre/navara has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 73.0 places maplibre/navara in the Elite tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, maplibre/navara 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 maplibre/navara 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.