webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
Comparison · Analytics
charlatan vs giscoR
A side-by-side editorial comparison of charlatan and giscoR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packageropensci
charlatan vs giscoR: at a glance
What is charlatan?
R's fake-data generator rebuilt its provider hierarchy so contributors can add one locale without touching the rest.
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
What is giscoR?
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
charlatan vs giscoR: editorial side-by-side
charlatan
0.0ANALYTICS
R's fake-data generator rebuilt its provider hierarchy so contributors can add one locale without touching the rest.
◆ Current state
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
◆ Where it's heading
The package's value scales with locale coverage, and its releases track that: early versions added data-type providers, middle versions added locales one contributor at a time, and 0.6.1 attacked the bottleneck by restructuring the class hierarchy so a locale can override a single function. Development has effectively been handed to contributors, with maintainer releases reduced to docs rebuilds and CRAN compliance.
◆ Prediction
Expect the next substantive release to be an accumulation of contributed locales and providers arriving through the new parent-provider structure, rather than maintainer-driven feature work.
giscoR
0.0ANALYTICS
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
◆ Current state
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
◆ Where it's heading
The package is decoupling itself from Eurostat's publication calendar. Historically each new GISCO vintage required a release that bumped default years and rebuilt an internal dataset; after 1.0.0 a user can call gisco_get_cached_db(update_cache = TRUE) and reach new data without waiting. The follow-up releases are consistent with a project in consolidation — fixing the cache it just introduced, exposing a timeout for slow downloads, and tidying internals.
◆ Prediction
With the database now self-updating, expect releases to shift toward download reliability and new GISCO endpoints rather than annual dataset bumps; the timeout option in 1.1.0 suggests large downloads are the current pain point.
Alternatives to charlatan and giscoR
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 charlatan or giscoR.
sftime
The spatiotemporal companion to sf, moving at the pace of the packages around it.
ReLTER
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
waywiser
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
taxizedb
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
fellingdater
Went from estimating felling dates to doing the crossdating that produces them.
See all charlatan alternatives → · See all giscoR alternatives →
Recent activity from charlatan and giscoR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agogiscoRInternal refactor with faster mocked tests
- 4mo agogiscoRDownload timeout becomes configurable
- 6mo agogiscoRCache persistence fixed; urban audit defaults to 2024
- 7mo agocharlatanDocs rebuild surfaces a duplicate Norwegian phone pattern
- 7mo agogiscoR1.0 caches the dataset index so new vintages need no release ⚡
- 1y agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agocharlatanProvider classes restructured so locales can override single functions ⚡
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
- 6y agocharlatanNew locales and providers; allowed_locales() added
- 7y agocharlatanLocale naming standardised; French and Danish data corrected
- 8y agocharlatancharlatan v0.2.2
- 8y agocharlatanSix new providers broaden charlatan beyond names and addresses
Frequently asked questions
What is the difference between charlatan and giscoR?
Both compete on the same themes — r-package, ropensci — within Analytics. charlatan and giscoR 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 charlatan better than giscoR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. charlatan and giscoR 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 charlatan?
Top charlatan alternatives in Analytics are ranked by recent ship velocity. Browse the "charlatan alternatives" section above for the current picks, or visit /alternatives/charlatan for the full list with editorial commentary on each.
What are the best alternatives to giscoR?
Top giscoR alternatives in Analytics are ranked by recent ship velocity. Browse the "giscoR alternatives" section above for the current picks, or visit /alternatives/giscor for the full list with editorial commentary on each.