← Back to home
Comparison · Analytics

ggmapinset vs healthyR.data

A side-by-side editorial comparison of ggmapinset and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.

ggmapinset vs healthyR.data: at a glance

FeatureggmapinsethealthyR.data
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, geospatial, inset-maps, extension-apir-package, healthcare-data, cms, api-client
Last editorial update5h ago1h ago
WebsiteVisit →Visit →

What is ggmapinset?

A ggplot2 inset-map extension that is now infrastructure for other packages

ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.

Read the full ggmapinset trajectory →

What is healthyR.data?

From a bundled hospital dataset to a live CMS API client.

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

Read the full healthyR.data trajectory →

ggmapinset vs healthyR.data: editorial side-by-side

G
ggmapinset
ANALYTICS
0.0

A ggplot2 inset-map extension that is now infrastructure for other packages

◆ Current state

ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.

◆ Where it's heading

The package has moved steadily from feature to foundation. 0.3.0 replaced confusing parameter names and rebuilt everything on stat_sf_inset() so coordinate limits stayed correct, then exposed transform_to_inset() explicitly for extension developers. 0.4.0 generalised inset shapes beyond circles to rectangles and arbitrary sf geometries. 0.5.0 continues in that direction, changing defaults in ways that require downstream extensions to adapt — the cost of being depended upon.

◆ Prediction

Expect further extension points driven by what ggautomap and the other cidm-ph mapping packages need, with the user-facing inset API staying largely settled after the shape generalisation.

H
healthyR.data
ANALYTICS
0.0

From a bundled hospital dataset to a live CMS API client.

◆ Current state

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

◆ Where it's heading

The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.

◆ Prediction

With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.

Alternatives to ggmapinset and healthyR.data

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 ggmapinset or healthyR.data.

See all ggmapinset alternatives → · See all healthyR.data alternatives →

Recent activity from ggmapinset and healthyR.data

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agoggmapinsetNew extension point for ggautomap; waiver() replaces NA
  2. 1y agohealthyR.datahttr2 compatibility fix
  3. 1y agoggmapinsetRectangular and arbitrary sf inset shapes
  4. 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
  5. 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data
  6. 3y agohealthyR.dataTwenty CMS measure accessors added
  7. 3y agoggmapinsetRebuilt on stat_sf_inset() with corrected coordinate limits
  8. 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
  9. 5y agohealthyR.dataxz compression added to meet CRAN size policy

Frequently asked questions

What is the difference between ggmapinset and healthyR.data?

They serve adjacent needs but don't currently overlap on shipped themes. ggmapinset and healthyR.data 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 ggmapinset better than healthyR.data?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggmapinset and healthyR.data 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 ggmapinset?

Top ggmapinset alternatives in Analytics are ranked by recent ship velocity. Browse the "ggmapinset alternatives" section above for the current picks, or visit /alternatives/ggmapinset for the full list with editorial commentary on each.

What are the best alternatives to healthyR.data?

Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data for the full list with editorial commentary on each.