🌍 The open source route planner api with plenty of features.
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 69%
Response Time: 21h
First Timer Success: 67%
GIScience/openrouteservice has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in GIScience/openrouteservice respond to incoming external pull requests in approximately 21.1 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 69.7 places GIScience/openrouteservice in the A tier.
The external contributor pull request merge rate for GIScience/openrouteservice is 69.1%, based on public PR activity from non-core contributors.
GIScience/openrouteservice currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in GIScience/openrouteservice. Prompt code reviews with positive guidance for new contributors.
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/GIScience/openrouteservice?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (86% approval). Large PRs (>500 lines) take ~101 hours (31% approval). Keep your diff compact for rapid review.
Is there an existing issue for this? I have searched the existing issues Feature/Enhancement Proposal Currently (v10.0.1) openrouteservice does not check the graph version of local graphs before loading the graphs. When openrouteservice is upgraded to a new version requiring graphs with a higher graph version, openrouteservice tries to load the local graphs and application start fails because the graph structure has changed and the graphs cannot be loaded. This happens even if graph management is enabled and the graphs for the configured profiles and graph version are available in the configured graph repository. It would be good, if openrouteservice would check the graph version of local graphs and delete or archive the local graphs before trying to load them. Depending on the configuration (source_file, graph repo config) a new graph should be calculated or downloaded, extracted. Additional context No response Possible Implementation No response Forum Topic Link No response
Is there an existing issue for this? I have searched the existing issues Problem description Here’s my config ors: engine: profile_default: build: source_file: example.osm.pbf profiles: cycling-regular: enabled: true build: encoder_options: enable_custom_models: true ext_storages: OsmId: foot-walking: enabled: true build: encoder_options: enable_custom_models: true ext_storages: OsmId: I’m getting the following error: 2026-08-07 16:59:19 WARN [o.a.c.l.WebappClassLoaderBase ] - The web application [ors] appears to have started a thread named [ORS-pl-foot-walking] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: com.fasterxml.jackson.core.base.ParserBase.getDoubleValue(ParserBase.java:853) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer._fromFloat(JsonNode
Problem description For a route involving two intermediate points connected via a skipped segment, the starting point for the segment is returned in the geometry as snapped, whereas the end point of the segment remains unsnapped. The geometry of the segment following the snapped segment is altered, see screen below. Proposed solution Always resort consistently to snapped points, if available.
Is there an existing issue for this? I have searched the existing issues Where did you encounter this issue? live API Request URL https://api.openrouteservice.org/v2/directions/foot-walking/json POST Request Body {"coordinates":[[8.611360492439918,49.422259353758854],[8.616435471168897,49.42033314380132],[8.618195056915285,49.419663140005824],[8.621574633194992,49.41823237211069]],"instructions":"false","geometry":"false"} Response Response { "bbox": [ 8.610761, 49.417645, 8.620996, 49.421596 ], "routes": [ { "summary": { "distance": 861, "duration": 619.9 }, "bbox": [ 8.610761, 49.417645, 8.620996, 49.421596 ] } ], "metadata": { "attribution": "openrouteservice.org | OpenStreetMap contributors", "service": "routing", "timestamp": 1768993304909, "query": { "coordinates": [ [ 8.611360492439918, 49.422259353758854 ],
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 GIScience/openrouteservice, 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 GIScience/openrouteservice acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.1% were successfully merged into the primary branch.
GIScience/openrouteservice has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 69.7 places GIScience/openrouteservice in the Welcoming tier.
The external pull request merge rate is 69.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, GIScience/openrouteservice currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for GIScience/openrouteservice 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.