Submission Inquiry: nycOpenData

[martinezc1]

Submitting Author Name: Christian Martinez
Submitting Author Github Handle: @martinezc1
Repository: https://github.com/martinezc1/nycOpenData
Version submitted: 0.1.6
Submission type: Standard
Editor: @ronnyhdez
Reviewers: @donghl17, @MichaelPascale

Due date for @donghl17: 2026-05-04

Due date for @MichaelPascale: 2026-05-04
Archive: TBD
Version accepted: TBD
Language: en

---

• Paste the full DESCRIPTION file inside a code block below:

Package: nycOpenData
Type: Package
Title: Convenient Access to NYC Open Data API Endpoints
Version: 0.1.6
Authors@R: 
    c(
      person("Christian", "Martinez", 
             email = "c.martinez0@outlook.com", 
             role = c("aut", "cre"),
             comment = c(
               GitHub = "martinezc1",
               ORCID = "0009-0005-6026-6454"
             )),
      person("Crystal", "Adote",
             role = "ctb",
             comment = c(GitHub = "crystalna20")),
      person("Jonah", "Dratfield", 
             role = "ctb",
             comment = c(GitHub = "jdratfield38")),
      person("Joyce", "Escatel-Flores",
             role = "ctb",
             comment = c(GitHub = "JoyceEscatel")),
      person("Rob", "Hutto", 
             role = "ctb",
             comment = c(GitHub = "robhutto")),
      person("Isley", "Jean-Pierre",
             role = "ctb",
             comment = c(GitHub = "ijpier")),
      person("Shannon", "Joyce",
             role = "ctb",
             comment = c(GitHub = "shannonjoyce")),
      person("Laura", "Rose-Werner",
             role = "ctb",
             comment = c(GitHub = "laurarosewerner")),
      person("Emma", "Tupone",
             role = "ctb",
             comment = c(GitHub = "emmatup0205")),
      person("Xinru", "Wang",
             role = "ctb",
             comment = c(GitHub = "xrwangxr"))
    )
Description: Provides a unified set of helper functions to access datasets 
    from the NYC Open Data platform <https://opendata.cityofnewyork.us/>. 
    Functions return results as tidy tibbles and support optional filtering, 
    sorting, and row limits via the Socrata API. The package includes endpoints 
    for 311 service requests, DOB job applications, juvenile justice metrics, 
    school safety, environmental data, event permitting, and additional citywide datasets.
License: MIT + file LICENSE
Encoding: UTF-8
RoxygenNote: 7.3.3
Imports: 
    httr,
    jsonlite,
    tibble,
    curl
Suggests: 
    dplyr,
    ggplot2,
    knitr,
    rmarkdown,
    scales,
    testthat (>= 3.0.0),
    tidyr,
    vcr (>= 0.6.0),
    webmockr
URL: https://martinezc1.github.io/nycOpenData/, https://github.com/martinezc1/nycOpenData
BugReports: https://github.com/martinezc1/nycOpenData/issues
VignetteBuilder: knitr
Config/testthat/edition: 3

Scope

• Please indicate which category or categories from our package fit policies this package falls under: (Please check an appropriate box below. If you are unsure, we suggest you make a pre-submission inquiry.):

  • data retrieval
  • data extraction
  • data munging
  • data deposition
  • data validation and testing
  • workflow automation
  • version control
  • citation management and bibliometrics
  • scientific software wrappers
  • field and lab reproducibility tools
  • database software bindings
  • geospatial data
  • translation

• Explain how and why the package falls under these categories (briefly, 1-2 sentences):

The package provides a programmatic interface to the Socrata-backed NYC Open Data API, replacing manual CSV downloads with reproducible R code.

• Who is the target audience and what are scientific applications of this package?

Target Audience: The primary audience includes urban researchers, social scientists, and students in the CUNY system and beyond. It is specifically designed for analysts who need to integrate civic data into reproducible workflows without the overhead of manual data management.

Scientific Applications: nycOpenData facilitates large-scale urban studies, including spatial analysis of public service equity (via 311 data), longitudinal studies of urban ecology (via the Tree Census), and sociological research into school safety and juvenile justice trends. By providing a programmatic interface, it ensures that these urban analyses are fully reproducible and auditable.

• Are there other R packages that accomplish the same thing? If so, how does yours differ or meet our criteria for best-in-category?

The most closely related package is RSocrata, which provides a general-purpose interface for any Socrata-backed data portal. nycOpenData differs by meeting the "best-in-category" criteria through domain specialization.

• (If applicable) Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research?

Yes. The package exclusively accesses publicly available NYC Open Data datasets. It does not collect, infer, or augment personal data beyond what is provided by the data publisher, and it encourages responsible use of potentially sensitive fields (e.g., location data) in accordance with dataset-specific guidance and NYC Open Data terms.

• If you made a pre-submission inquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.

#748
@emilyriederer
@ronnyhdez

• Explain reasons for any pkgcheck items which your package is unable to pass.

None. All pkgcheck checks pass locally and in continuous integration.

Technical checks

Confirm each of the following by checking the box.

• I have read the rOpenSci packaging guide.
• I have read the author guide and I expect to maintain this package for at least 2 years or to find a replacement.

This package:

• does not violate the Terms of Service of any service it interacts with.
• has a CRAN and OSI accepted license.
• contains a README with instructions for installing the development version.
• includes documentation with examples for all functions, created with roxygen2.
• contains a vignette with examples of its essential functions and uses.
• has a test suite.
• has continuous integration, including reporting of test coverage.

Publication options

• Do you intend for this package to go on CRAN?

• Do you intend for this package to go on Bioconductor?

• Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution? If so:

MEE Options

• The package is novel and will be of interest to the broad readership of the journal.
• The manuscript describing the package is no longer than 3000 words.
• You intend to archive the code for the package in a long-term repository which meets the requirements of the journal (see MEE's Policy on Publishing Code)
• (Scope: Do consider MEE's Aims and Scope for your manuscript. We make no guarantee that your manuscript will be within MEE scope.)
• (Although not required, we strongly recommend having a full manuscript prepared when you submit here.)
• (Please do not submit your package separately to Methods in Ecology and Evolution)

Code of conduct

• I agree to abide by rOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

[ropensci-review-bot]

Thanks for submitting to rOpenSci, our editors and @ropensci-review-bot will reply soon. Type @ropensci-review-bot help for help.

[ropensci-review-bot]

🚀

Editor check started

👋

[ropensci-review-bot]

Checks for nycOpenData (v0.1.5)

git hash: 82d3afeb

• ✔️ Package is already on CRAN.
• ✔️ has a 'contributing' file.
• ✔️ uses 'roxygen2'.
• ✔️ 'DESCRIPTION' has a URL field.
• ✔️ 'DESCRIPTION' has a BugReports field.
• ✔️ Package has at least one HTML vignette
• ✔️ All functions have examples.
• ✖️ Package fails continuous integration checks.
• ✔️ Package coverage is 93.8%.
• ✔️ R CMD check found no errors.
• ✔️ R CMD check found no warnings.
• 👀 Some goodpractice linters failed.

Important: All failing checks above must be addressed prior to proceeding

(Checks marked with 👀 may be optionally addressed.)

Package License: MIT + file LICENSE

---

1. Package Dependencies

Details of Package Dependency Usage (click to open)

The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.

type	package	ncalls
internal	base	54
internal	nycOpenData	41
internal	utils	41
internal	methods	3
imports	httr	4
imports	jsonlite	1
imports	tibble	NA
imports	curl	NA
suggests	dplyr	NA
suggests	ggplot2	NA
suggests	knitr	NA
suggests	rmarkdown	NA
suggests	scales	NA
suggests	testthat	NA
suggests	tidyr	NA
suggests	vcr	NA
suggests	webmockr	NA
linking_to	NA	NA

Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table.

base

list (42), as.integer (2), character (2), gsub (2), tryCatch (2), vapply (2), names (1), paste0 (1)

nycOpenData

nyc_311 (1), nyc_311_2010_2019 (1), nyc_any_dataset (1), nyc_borough_community_report (1), nyc_borough_population (1), nyc_cause_of_death (1), nyc_city_record (1), nyc_civil_service_list (1), nyc_daily_attendance_2018_2019 (1), nyc_detention_admissions (1), nyc_dhs_daily_report (1), nyc_dob_job_applications (1), nyc_dob_permit_issuance (1), nyc_domestic_violence_annual_report (1), nyc_dop_juvenile_cases (1), nyc_dop_juvenile_rearrest_rate (1), nyc_film_permits (1), nyc_for_hire_vehicles (1), nyc_homeless_drop_in_centers (1), nyc_homeless_population_by_year (1), nyc_locallaw18_payreport (1), nyc_locallaw97_shelter_pets (1), nyc_medallion_drivers_active (1), nyc_medallion_drivers_authorized (1), nyc_motor_vehicle_collisions_crashes (1), nyc_museum_locations (1), nyc_nypd_hate_crimes (1), nyc_open_parking_camera_violations (1), nyc_period_attendance_reporting (1), nyc_permit_events_historic (1), nyc_pets_in_shelters (1), nyc_restaurant_inspection_results (1), nyc_runaway_and_homeless_youth_daily_census (1), nyc_school_discharge (1), nyc_school_discharge_report_2013_2015 (1), nyc_school_discharge_report_2015_2018 (1), nyc_street_hail_livery_active (1), nyc_tlc_new_driver_app_status (1), nyc_tree_census_2015 (1), nyc_urban_park_animal_condition (1), nyc_violent_disruptive_school_incidents (1)

utils

data (41)

httr

content (3), status_code (1)

methods

as (3)

jsonlite

fromJSON (1)

NOTE: Some imported packages appear to have no associated function calls; please ensure with author that these 'Imports' are listed appropriately.

---

2. Statistical Properties

This package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing.

Details of statistical properties (click to open)

The package has:

• code in R (100% in 42 files) and
• 1 authors
• 4 vignettes
• no internal data file
• 4 imported packages
• 41 exported functions (median 8 lines of code)
• 3 non-exported functions in R (median 11 lines of code)

---

Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:

• loc = "Lines of Code"
• fn = "function"
• exp/not_exp = exported / not exported

All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the checks_to_markdown() function

The final measure (fn_call_network_size) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.

measure	value	percentile	noteworthy
files_R	42	93.5
files_vignettes	4	93.7
files_tests	42	98.6
loc_R	462	43.1
loc_vignettes	300	60.6
loc_tests	435	66.5
num_vignettes	4	94.2
n_fns_r	44	72.5
n_fns_r_exported	41	83.5
n_fns_r_not_exported	3	44.1
n_fns_per_file_r	1	40.5
num_params_per_fn	3	31.3
loc_per_fn_r	8	23.4
loc_per_fn_r_exp	8	18.0
loc_per_fn_r_not_exp	11	70.4
rel_whitespace_R	31	59.8
rel_whitespace_vignettes	40	86.4
rel_whitespace_tests	29	86.8
doclines_per_fn_exp	35	44.2
doclines_per_fn_not_exp	29	97.5	TRUE
fn_call_network_size	121	80.4

---

2a. Network visualisation

Click to see the interactive network visualisation of calls between objects in package

---

3. goodpractice and other checks

Details of goodpractice checks (click to open)

---

3b. goodpractice results

R CMD check with rcmdcheck

R CMD check generated the following check_fail:

1. no_export_pattern

Test coverage with covr

Package coverage: 93.78

Cyclocomplexity with cyclocomp

No functions have cyclocomplexity >= 15

Static code analyses with lintr

lintr found no issues with this package!

---

Package Versions

package	version
pkgstats	0.2.1.14
pkgcheck	0.1.2.262

---

Editor-in-Chief Instructions:

Processing may not proceed until the items marked with ✖️ have been resolved.

[martinezc1]

@ropensci-review-bot CI is now passing on main — earlier failure was during an in-progress run while I pushed an update.

[ropensci-review-bot]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@ropensci-review-bot help

[emilyriederer]

@ropensci-review-bot check package

[ropensci-review-bot]

Thanks, about to send the query.

[ropensci-review-bot]

🚀

Editor check started

👋

[ropensci-review-bot]

Checks for nycOpenData (v0.1.5)

git hash: 1dc05855

• ✔️ Package is already on CRAN.
• ✔️ has a 'contributing' file.
• ✔️ uses 'roxygen2'.
• ✔️ 'DESCRIPTION' has a URL field.
• ✔️ 'DESCRIPTION' has a BugReports field.
• ✔️ Package has at least one HTML vignette
• ✔️ All functions have examples.
• ✔️ Package has continuous integration checks.
• ✔️ Package coverage is 93.8%.
• ✔️ R CMD check found no errors.
• ✔️ R CMD check found no warnings.
• 👀 Some goodpractice linters failed.

(Checks marked with 👀 may be optionally addressed.)

Package License: MIT + file LICENSE

---

1. Package Dependencies

Details of Package Dependency Usage (click to open)

The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.

type	package	ncalls
internal	base	54
internal	nycOpenData	41
internal	utils	41
internal	methods	3
imports	httr	4
imports	jsonlite	1
imports	tibble	NA
imports	curl	NA
suggests	dplyr	NA
suggests	ggplot2	NA
suggests	knitr	NA
suggests	rmarkdown	NA
suggests	scales	NA
suggests	testthat	NA
suggests	tidyr	NA
suggests	vcr	NA
suggests	webmockr	NA
linking_to	NA	NA

Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table.

base

list (42), as.integer (2), character (2), gsub (2), tryCatch (2), vapply (2), names (1), paste0 (1)

nycOpenData

nyc_311 (1), nyc_311_2010_2019 (1), nyc_any_dataset (1), nyc_borough_community_report (1), nyc_borough_population (1), nyc_cause_of_death (1), nyc_city_record (1), nyc_civil_service_list (1), nyc_daily_attendance_2018_2019 (1), nyc_detention_admissions (1), nyc_dhs_daily_report (1), nyc_dob_job_applications (1), nyc_dob_permit_issuance (1), nyc_domestic_violence_annual_report (1), nyc_dop_juvenile_cases (1), nyc_dop_juvenile_rearrest_rate (1), nyc_film_permits (1), nyc_for_hire_vehicles (1), nyc_homeless_drop_in_centers (1), nyc_homeless_population_by_year (1), nyc_locallaw18_payreport (1), nyc_locallaw97_shelter_pets (1), nyc_medallion_drivers_active (1), nyc_medallion_drivers_authorized (1), nyc_motor_vehicle_collisions_crashes (1), nyc_museum_locations (1), nyc_nypd_hate_crimes (1), nyc_open_parking_camera_violations (1), nyc_period_attendance_reporting (1), nyc_permit_events_historic (1), nyc_pets_in_shelters (1), nyc_restaurant_inspection_results (1), nyc_runaway_and_homeless_youth_daily_census (1), nyc_school_discharge (1), nyc_school_discharge_report_2013_2015 (1), nyc_school_discharge_report_2015_2018 (1), nyc_street_hail_livery_active (1), nyc_tlc_new_driver_app_status (1), nyc_tree_census_2015 (1), nyc_urban_park_animal_condition (1), nyc_violent_disruptive_school_incidents (1)

utils

data (41)

httr

content (3), status_code (1)

methods

as (3)

jsonlite

fromJSON (1)

NOTE: Some imported packages appear to have no associated function calls; please ensure with author that these 'Imports' are listed appropriately.

---

2. Statistical Properties

This package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing.

Details of statistical properties (click to open)

The package has:

• code in R (100% in 42 files) and
• 1 authors
• 4 vignettes
• no internal data file
• 4 imported packages
• 41 exported functions (median 8 lines of code)
• 3 non-exported functions in R (median 11 lines of code)

---

Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:

• loc = "Lines of Code"
• fn = "function"
• exp/not_exp = exported / not exported

All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the checks_to_markdown() function

The final measure (fn_call_network_size) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.

measure	value	percentile	noteworthy
files_R	42	93.5
files_vignettes	4	93.7
files_tests	42	98.6
loc_R	462	43.1
loc_vignettes	300	60.6
loc_tests	435	66.5
num_vignettes	4	94.2
n_fns_r	44	72.5
n_fns_r_exported	41	83.5
n_fns_r_not_exported	3	44.1
n_fns_per_file_r	1	40.5
num_params_per_fn	3	31.3
loc_per_fn_r	8	23.4
loc_per_fn_r_exp	8	18.0
loc_per_fn_r_not_exp	11	70.4
rel_whitespace_R	31	59.8
rel_whitespace_vignettes	40	86.4
rel_whitespace_tests	29	86.8
doclines_per_fn_exp	35	44.2
doclines_per_fn_not_exp	29	97.5	TRUE
fn_call_network_size	121	80.4

---

2a. Network visualisation

Click to see the interactive network visualisation of calls between objects in package

---

3. goodpractice and other checks

Details of goodpractice checks (click to open)

3a. Continuous Integration Badges

GitHub Workflow Results

id	name	conclusion	sha	run_number	date
21792082575	pkgcheck	success	1dc058	25	2026-02-08
21792082567	R-CMD-check.yaml	success	1dc058	29	2026-02-08
21792082571	test-coverage.yaml	success	1dc058	38	2026-02-08

---

3b. goodpractice results

R CMD check with rcmdcheck

R CMD check generated the following check_fail:

1. no_export_pattern

Test coverage with covr

Package coverage: 93.78

Cyclocomplexity with cyclocomp

No functions have cyclocomplexity >= 15

Static code analyses with lintr

lintr found no issues with this package!

---

Package Versions

package	version
pkgstats	0.2.1.14
pkgcheck	0.1.2.262

---

Editor-in-Chief Instructions:

This package is in top shape and may be passed on to a handling editor

[emilyriederer]

@ropensci-review-bot assign @ronnyhdez as editor

[ropensci-review-bot]

Assigned! @ronnyhdez is now the editor

[ronnyhdez]

Hi @martinezc1!

Thanks for submitting your package to the rOpenSci review process. It’s my pleasure to support this process as the editor.

Thanks as well to @emilyriederer for her help with the initial review steps!

To help you track my comments, I'll tag them with "r" and a numbered sequence (r01, r02, etc). Please refer to this notation in your responses.

• Comments following bullets are for you to consider -- you may or may not respond to them.

• Comments following checkboxes are requests for action -- please respond to those.

For example, here is my first comment:

• r01. Could you please suggest three potential reviewers without conflicts of interest? We may invite at most one, but having a few suggestions from your side helps us better understand the expertise you think would be beneficial. This may take some effort, but it helps us find good reviewers as quickly as possible.