We've finished upgrading the site and everything seems to check out. We added a few features behind the scenes, but mostly we applied some security patches and brought a few other things up-to-date. Just so you know, little about the content has changed, but we're hoping to change that soon.  One minor update is that we are demo'ing the New Mexico version of EDAS2 from the demo links in the wiki. However, we don't have an anonymous version of the site running. So, please contact us if you'd like to see it in action. We're planning on pulling New Mexico's improvements into the code base and will post details about soon. Thank you to NM for the contributions!

In the meantime, please let John know if you have questions or problems with the site.

Please excuse the condition of the wiki and other pages. We are in the process of upgrading the site.

Most items on the site should now be readable however.

It's been some time since I've written and I wanted to post some notes about where things are with EDAS2.

There are a number of organizations (state agencies) around the country that are currently evaluating EDAS2 for production use. Please contact us if you are interested in coordinating with these agencies as we encourage everyone to pool their resources to save time and $$. EPA Region 7 is also evaluating using EDAS2 for data management and reporting. They have provided valuable feedback on their experience and find EDAS2 to be a very useful platform. They have noted some room for improvement and ways to make EDAS2 better. So we hope to be able incorporate these suggestions in a future release.

Also note that the state of New Mexico has adopted EDAS2 for internal water quality and biological data management. New Mexico is actively developing against EDAS2 and has agreed to share their improvements back to the project. Their improvements to date include enabling support for multiple users through the use of Seam Security (and the upgrade to Seam 2.1). They are currently implementing a number of other general and agency-specific improvements, and hopefully we will be able to post details about them here soon.

Also, please note that we have updated our Contributions section with a brief explanation of the process for submitting changes to the core EDAS2 project.

As promised we have posted the source code and everything you need to run this initial release of EDAS2.

This site should have everything that you need to run a local copy of EDAS2, including the database script files, database diagram, seed data, Java source code (for Java 5 and 6) and the installation instructions.

Note that the version we have posted here is the same as is running on our demonstration servers. This version also includes the example reverse-geocoding [2] request that looks up HUC8 when creating or editing a monitoring location. At this time this request points at a service provided from a Tetra Tech development server and is based on ArcGIS Server. The source code for this service is not available.

We have been getting a lot of interest from folks wanting to “kick the tires” after a successful webinar demonstrating some of the key aspects of EDAS2 (see embedded slide show below).

So, this announcement is for all of you who want to run EDAS2 within your own environments. Our target for our first source release is March 16. This release will contain all the sources needed to run EDAS2 and wiki-based documentation for deploying it. We are planning to make the sources available through the Sourceforge site (https://sourceforge.net/projects/edas2/)

So watch this space for the final announcement!

Want to know more about the technology underneath EDAS2?

Read this article by Dan Allen (and then read his book Seam in Action). Dan was instrumental in the early days of EDAS2 and he provided a lot of great performance tuning which we hope will be useful to all Seam developers.

Speed up your Data-Driven JSF/Seam Application by Two Orders of Magnitude - Part 1

We have posted some updated slides below in case you missed the web cast. You may chose to expand the slides into their own window for easier viewing. Click the image below or click [here].

The EDAS2 Project continues forward and since I posted last we have released versions 0.4 and 0.5 for preview. These versions introduced a lot of new functionality, but I’d like to highlight a few of my favorite additions here.

To streamline the user experience we’ve included modifications to the detailed results management screens that provide the user only with fields that are relevant to the type of activity they are working with. For example, there are dedicated screens for the management of sediment, fish, habitat, tissue, and plankton samples.

We have also included a many more lookup administration screens, as well as additional import/export capabilities such as a tabular station importer, and the ability to import and export WQX 2.0 XML straight from EDAS2 (without needing a Node).

But as a GIS guy my favorite new addition is the ability for EDAS2 to call a Reverse Geocoding (RG) service to populate geographic fields of a monitoring location. For example, when a user creates a station, EDAS2 will now call an RG service and automatically populate the HUC8 field of the Monitoring Location. Of course there was not a reliable RG service available for HUCs so we also crafted our own RG service based on ESRI’s ArcGIS Server to support our needs.

In summary, EDAS2 is shaping up to become a very usable platform for managing and sharing your environmental data.

As always, if you can find more information about the changes to EDAS2 at the Roadmap http://www.edas2.com/dokuwiki/doku.php/roadmap

If you find these items interesting and want to learn more, please contact us through the information at the left of the page. If you want to chat about EDAS2 and offer some of your ideas and thoughts, feel free to sign up for an account with this site and post your thoughts on the forum.

We made up a little ground with the last release and conducted the internal release of 0.2 today -- a little earlier than planned. Check out the roadmap to see the covered features.

Unfortunately the discussion rages about how we handle biological data in the database. We are trying to balance usability issues with the desire to maintain cross-organization exhange of bio data. Unfortunately, an elegant solution to cover both gracefully is so far elusive. Stay tuned for updates.

But, not wanting to reduce our momentum, we have an internal draft list of features that will we'll be implementing for 0.3 perhaps even by November 1! Again, watch the roadmap as we will post the proposed features there very soon. Progress marches on.