Home

ERDDAP

ERDDAP (the Environmental Research Division's Data Access Program) is a data server that gives you a simple, consistent way to download subsets of scientific datasets in common file formats and make graphs and maps.
See ERDDAP in action.

Tag Naming Convention for Commits

Public releases will have a tag (e.g., v1.38).

Project Guidelines

• I'll try to be a BDFL (Benevolent Dictator For Life), with the emphasis on Benevolent.
• I am open to pulling changes from you. (No guarantees)
• Please contact me before you start your changes, so we can coordinate a little to increase the odds that I will accept your changes.
• I will generally only accept changes that are of general usefulness (including adding hooks for more private changes), not just things specific to one project.
• Please restrict a given commit to a limited scope. I'll try to do the same. I'm new to Git so larger sets of changes are more daunting.
• The code will have to be of good quality.
• The code should follow the Java Code Conventions as closely as possible.
• Ideally, write a test() method for your changes (like the other test methods in almost all erddap classes) so I can automatically test the changes / new features.
• If you want to contribute significant new functionality (e.g., a new EDD subclass), I may only accept the changes if you take responsibility for maintenance, bug-fixing, and technical support for your changes. (As some authors have noted, code is a liability as well as an asset.)
• If I don't accept your changes, please don't be offended. I don't want ERDDAP to be a kitchen sink for everyone's favorite feature. I want to maintain a consistent vision for ERDDAP. Fortunately, Git should make it much easier for you to maintain your own fork of ERDDAP and still pull in all of the changes that I make.