← Back to home
Comparison · Analytics

datapack vs maplegend

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

datapack vs maplegend: at a glance

Featuredatapackmaplegend
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesresearch-data, dataone, provenance, bagitcartography, legends, base-graphics, spatial
Last editorial update48m ago2h ago
WebsiteVisit →Visit →

What is datapack?

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

Read the full datapack trajectory →

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.

Read the full maplegend trajectory →

datapack vs maplegend: editorial side-by-side

D
datapack
ANALYTICS
0.0

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

◆ Current state

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

◆ Where it's heading

The arc runs from assembly to correctness of the resulting archive. Later releases keep tightening the metadata the resource map must carry — dc:creator always present, dcterms:modified always updated, the package correctly flagged as modified after any access-policy change — because a bundle whose provenance record is subtly wrong is worse than one that fails outright. The three-year gap between 1.4.1 and 1.4.2, and the latter's CRAN-note content, place this package firmly in preservation.

◆ Prediction

Expect the next release, if any, to be another CRAN-compliance patch rather than functional work. The 1.4.2 note that it contains no new features is the clearest statement in the feed about where this package sits.

M
maplegend
ANALYTICS
0.0

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.

Alternatives to datapack and maplegend

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 datapack or maplegend.

See all datapack alternatives → · See all maplegend alternatives →

Recent activity from datapack and maplegend

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

  1. 2mo agomaplegendContinuous legend formatting and aspect-ratio segment fix
  2. 4mo agomaplegendChoropleth legends on points, lines and symbols
  3. 7mo agomaplegendPackage-wide refactor for non-unity aspect ratios, histogram legends
  4. 7mo agomaplegendSingle-modality legends allowed for typo, symb and prop_line
  5. 10mo agodatapackCRAN documentation and CI cleanup
  6. 1y agomaplegendAlpha transparency and redraw on device resize
  7. 1y agomaplegendOffset and symbol sizing aligned with mapsf
  8. 4y agodatapackBagIt serialisation brought in line with the current spec
  9. 5y agodatapackSHA-256 becomes the default checksum algorithm
  10. 6y agodatapackResource map metadata guaranteed; removeRelationships() added
  11. 8y agodatapackupdateMetadata no longer drops package relationships
  12. 9y agodatapackAssembled data packages become editable in place

Frequently asked questions

What is the difference between datapack and maplegend?

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

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

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

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.