osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
maplegend vs patentsview
A side-by-side editorial comparison of maplegend and patentsview — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
maplegend vs patentsview: at a glance
What is maplegend?
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
What is patentsview?
Dormant for years, then rewritten wholesale when the API underneath it broke.
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
maplegend vs patentsview: editorial side-by-side
maplegend
0.0ANALYTICS
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
◆ Current state
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
◆ Where it's heading
This is a support library whose backlog is defined by its caller. Every legend type mapsf can produce needs a matching legend renderer, and the release notes are dominated by spacing, offset, and border details — box_cex for symbol spacing, NA box placement in horizontal choropleth legends, text overflow when no_data is set. The shared vocabulary with mapsf is being maintained deliberately, with val_rnd, val_big, and val_dec propagating through legend types release by release. Version numbering is not monotonic in this feed, with 0.4.0 published seconds after 0.5.0.
◆ Prediction
Expect the remaining combined map types to acquire matching legends and the val_* formatting arguments to reach the types that still lack them.
patentsview
0.0ANALYTICS
Dormant for years, then rewritten wholesale when the API underneath it broke.
◆ Current state
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
◆ Where it's heading
The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.
◆ Prediction
Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.
Alternatives to maplegend and patentsview
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either maplegend or patentsview.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all maplegend alternatives → · See all patentsview alternatives →
Recent activity from maplegend and patentsview
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agomaplegendContinuous legend formatting and aspect-ratio segment fix
- 4mo agomaplegendChoropleth legends on points, lines and symbols
- 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints ⚡
- 7mo agomaplegendPackage-wide refactor for non-unity aspect ratios, histogram legends
- 7mo agomaplegendSingle-modality legends allowed for typo, symb and prop_line
- 1y agomaplegendAlpha transparency and redraw on device resize
- 1y agomaplegendOffset and symbol sizing aligned with mapsf
- 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
- 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
- 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
- 8y agopatentsviewcast_pv_data() converts returned columns to real types
- 9y agopatentsviewFirst release: query DSL for the PatentsView API
Frequently asked questions
What is the difference between maplegend and patentsview?
Both compete on the same themes — r-package — within Analytics. maplegend and patentsview are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is maplegend better than patentsview?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. maplegend and patentsview are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to maplegend?
Top maplegend alternatives in Analytics are ranked by recent ship velocity. Browse the "maplegend alternatives" section above for the current picks, or visit /alternatives/maplegend for the full list with editorial commentary on each.
What are the best alternatives to patentsview?
Top patentsview alternatives in Analytics are ranked by recent ship velocity. Browse the "patentsview alternatives" section above for the current picks, or visit /alternatives/patentsview for the full list with editorial commentary on each.