← Back to software development tools
Alternatives · software development tools

libosmium alternatives

The best libosmium alternatives in software development tools, ranked by Sparkpulse's velocity_score.

Updated Aug 10, 2026

Looking for the best alternatives to libosmium? Sparkpulse tracks and ranks 12 alternatives in software development tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, libosmium shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.

About libosmium

libosmium is a stable OSM parsing library whose main work now is shedding old dependencies

libosmium ships roughly once or twice a year and the release notes read accordingly: a handful of additions, a longer list of fixes, and a steady drumbeat of code cleanups. Recent cycles have been dominated by removing things — Google Sparsehash, the ancient Proj projection support, regex filters, and a series of long-deprecated classes. The library's core job of reading and writing OSM data has been stable long enough that most fixes now cluster around compression edge cases and PBF parsing tolerance.

Velocity 0.0 · Last update 1h ago

Read the full libosmium trajectory →

Top 12 alternatives to libosmium

Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.

Browse all software development tools products →

libosmium vs alternatives — shipping velocity at a glance

Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.

ProductVelocitySparks · 30dFocus areasLatest release
libosmium (baseline)0.00openstreetmapcpp-librarypbf-parsing
Nacos6.31service-discoveryai-registryagent-infrastructureProtocol-neutral agent registration and agentic resource discovery
Aerospike5.00nosql-databasecve-remediationmulti-branch-releases
Apache OpenNLP5.00nlpapachemodel-supply-chain
SimpleSAMLphp5.00samlidentity-federationsecurity-patches
Dapr5.00distributed-runtimeactorsworkflows
Z-Wave JS UI5.00zwavehome-automationsecurity-hardening
CP2K3.81dftk-pointsgpu-accelerationCP2K 2026.2: CUDA exact exchange and grand-canonical SCF
Mapnik2.50map-renderingvector-tilespmtilesMapnik 4.1.3 reads PMTiles over the network with SSL
deal.II2.50finite-elementsscientific-computingannual-release
RDKit2.50cheminformaticsstereochemistryquarterly-releases
Apache TomEE2.50jakarta-eeapplication-serverdependency-maintenance
OSRM2.50routingcpp20-migrationbuild-tooling

The 12 best libosmium alternatives, in depth

1. Nacos · velocity 6.3

Nacos is turning a microservice registry into a registry for AI agents.

Over the last 30 days Nacos shipped 1 meaningful update vs libosmium's 0, most recently “Protocol-neutral agent registration and agentic resource discovery”. Its velocity score of 6.3/10 blends that with longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Nacos focuses on service discovery, ai registry and agent infrastructure.

Over the last 30 days Nacos has been shipping faster than libosmium — a point in its favour if release momentum matters to you.

2. Aerospike · velocity 5.0

Aerospike shipped a coordinated CVE train across four release branches in one afternoon.

Its velocity score of 5.0/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Aerospike focuses on nosql database, cve remediation and multi branch releases.

Aerospike and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

3. Apache OpenNLP · velocity 5.0

Three parallel lines, one shared job: making model files safe to load.

Its velocity score of 5.0/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Apache OpenNLP focuses on nlp, apache and model supply chain.

Apache OpenNLP and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

4. SimpleSAMLphp · velocity 5.0

SimpleSAMLphp advances two maintenance branches in lockstep, security patches first.

Its velocity score of 5.0/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, SimpleSAMLphp focuses on saml, identity federation and security patches.

SimpleSAMLphp and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

5. Dapr · velocity 5.0

Dapr patches three release lines at once and writes root-cause notes for each fix.

Its velocity score of 5.0/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Dapr focuses on distributed runtime, actors and workflows.

Dapr and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

6. Z-Wave JS UI · velocity 5.0

Z-Wave JS UI is hardening its network surface while handing issue triage to agents.

Its velocity score of 5.0/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Z-Wave JS UI focuses on zwave, home automation and security hardening.

Z-Wave JS UI and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

7. CP2K · velocity 3.8

CP2K is rebuilding a legacy Fortran DFT code around GPUs, ML potentials, and k-points.

Over the last 30 days CP2K shipped 1 meaningful update vs libosmium's 0, most recently “CP2K 2026.2: CUDA exact exchange and grand-canonical SCF”. Its velocity score of 3.8/10 blends that with longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, CP2K focuses on dft, k points and gpu acceleration.

Over the last 30 days CP2K has been shipping faster than libosmium — a point in its favour if release momentum matters to you.

8. Mapnik · velocity 2.5

Mapnik is turning a local-file map renderer into a client of remote tile archives.

Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Mapnik 4.1.3 reads PMTiles over the network with SSL”.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Mapnik focuses on map rendering, vector tiles and pmtiles.

Mapnik and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

9. deal.II · velocity 2.5

Deal.II ships one big finite-element release a year, then patches it twice.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, deal.II focuses on finite elements, scientific computing and annual release.

deal.II and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

10. RDKit · velocity 2.5

Quarterly majors set the breaking changes; the patch train spends the rest of the year on stereochemistry.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, RDKit focuses on cheminformatics, stereochemistry and quarterly releases.

RDKit and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

11. Apache TomEE · velocity 2.5

A Jakarta EE server whose changelog is mostly dependabot — until EE11 moved to main.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, Apache TomEE focuses on jakarta ee, application server and dependency maintenance.

Apache TomEE and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

12. OSRM · velocity 2.5

A routing engine spending its release budget on the toolchain, not the router.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where libosmium leans on openstreetmap, cpp library and pbf parsing, OSRM focuses on routing, cpp20 migration and build tooling.

OSRM and libosmium have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

Frequently asked questions

What are the best alternatives to libosmium?

The top libosmium alternatives we currently track in software development tools are Nacos, Aerospike, Apache OpenNLP, SimpleSAMLphp, Dapr, ranked by recent ship velocity.

How is this list of libosmium alternatives ranked?

Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.

Can I compare libosmium directly with one of these alternatives?

Yes — every card has a "Compare with libosmium" link to a side-by-side /compare page.