feat: add 2026_may folder and nppes data example#13
Open
asenetcky wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Add May 2026 Example: Handling Large NPPES Data with DuckDB & Parquet
Summary
This PR adds a new module for the May 2026 R User Group session focusing on efficient ingestion and processing of large datasets. The example uses the National Plan and
Provider Enumeration System (NPPES) "Full Replacement File" (~11GB CSV) to demonstrate how to bypass memory limitations using DuckDB and Parquet.
Key Changes
large-scale CSV work.
Why this is valuable
Health care data (like NPPES) is often too large for standard read_csv() calls on consumer-grade hardware. This contribution provides the group with a template for
"out-of-memory" data engineering in R, making these datasets accessible to more users.
How to Test