Skip to content

Roadmap

Jump to bottom Edit New page
Tom Schenk Jr edited this page Jul 11, 2015 · 26 revisions

Below outlines upcoming features and bug fixes slated for future releases of RSocrata on the Comprehensive R Archive Network (CRAN). Many of these items are already available on the issue page and are queued in the list below.

The next planned release of RSocrata on CRAN is 1.6.1 and is available in the master branch, while version 2.0 is being planned. The version numbers follow the recommendations of Semantic Versioning 2.0.0.

Version 1.5.1

Bug fixes

  • Deprecated httr::guess_media(), implement mime::guess_type() (#4)

Version 1.6

Features

  • Show list of datasets available on any Socrata portal ls.socrata()
  • Allow users to pass along SODA API tokens in separate, optional argument in read.socrata()
  • Add compatibility for data.json v1.1 (#22)

Bug fixes

  • Failure to posixify when no data (#24)

Planned Releases

Version 1.6.1

Bug fixes

  • Repair bug: Warning: replacing previous import by ‘curl::handle_reset’ when loading ‘RSocrata’ (#42)

Documentation & Maintenance

  • Add contributor instructions (#23 and #28)
  • Clean-up DESCRIPTION (#40)
  • Add continuous integration for Windows (#39)
  • Migrate Travis-CI to "proper" R YAML (#46)
  • Implement code coverage monitoring (#41)
  • Re-including man/ directory in repo (#20)
  • Moved unit testing library to testthat (#48)
  • Moved testing library to root so is automatically built on Rbuild

Version 2.0

This release will incorporate compatibility with recent features with Socrata's SoDA API. Tentatively, this includes:

New features

  • Compatibility with GeoJSON returns and leveraging it for mapping (#43)
  • Support for Catalog API calls
  • Adding fine-grain arguments to the read.socrata function for easier scriptability:
read.socrata(url, domain, fourbyfour, app_token, query)
  • Change default file type (when not specified in url argument) from CSV to JSON for performance improvements.

Document and maintenance

  • Provide explicit error handling for HTTP/url issues, for instance:
    • Add specific error message for non-SoDA resource (#16)
    • Replace errors similar to 2015-07-10 11:18:47.945 getResponse: Error in httr GET: 401 http://data.cityofchicago.org/resource/j8vp-2qpg.json with a nice message/warning/stop functions
  • Separate RSocrata.R into separate files
Clone this wiki locally