Ecocat

Initial Review

Welcome to the team that over the past decade has developed several outstanding GIS interactive web applications - RMMS, Ecocat, WIRT, Farmedu. Team members have gone on to work with major corporations including Verizon, Google, Yahoo, as well as smaller firms who value the importance of web-based GIS applications.

The links Anand sent for Ecocat can be a bit daunting. The bottom line is that at some point in the screens of information the public user has to complete regarding compliance issues etc, the users enters information regarding the location of the proposed project which must be approved or denied. At that point - when the user enters the location via a particular PLSS designation - certain things happen,

  1. an xml file is written by the company CDM that gives the project code assigned, date/time stamps, the type of review requested (e.g. are wetlands to be included in the review?)
  2. We obtain that xml file and the info contained therein. A map frame which pulls in an ESRI published map service and the location of that PLSS is zoomed to. That map service includes map layers such as streets, interstates, DOQs, DRGs etc. which can be turned on or off by the user. Other standard tools such as zoom in, pan, last extent etc are available in that map frame. (We have to build those, now using ESRI tools provided in the silverlight api.)
  3. After deciding on the appropriate location, which may mean panning to different plss etc, the user uses tools we provide to draw a polygon which displays the footprint of the proposed project.
  4. The polygon is then used to “cut” various secured layers to see if the proposed project impacts various criteria that would impact on say Threatened and Endangered wildlife or wetlands or other protected layers.
  5. The results of the cut are passed back to CDM - the company that developed the initial screens - via xml specifications CDM provides for use in their programming.
  6. Most of this info is also written to an SDE database (sqlserver is the underlying RDMS) In ESRI v10, .net 4 and silverlight 2.0 this can be done instead of using the methods we used in the past.
  7. A log is written to indicating that the insert/modification to the SDE database was success or not - not quite, but that is the idea - Records are written indicating the project code assigned, a date-time stamp when the sde insert began and when it was completed. If there was an error that was thrown, the sde error is written to the log file.

There is one other twist in the programming - While most of the time entries come in through the public ecocat interface that CDM has created, sometimes IDNR staff create entries directly from a CDM provided interface available to OREP staff within IDNR. So our programming has to track that as well.

All of this programming exists. We just need to change the programming to

  1. Use ESRI v10 ArcGIS Server and other v10 products
  2. Use the Silverlight 2.0 ESRI API,.net 4.0, and Silverlight 4.0
  3. instead of the homegrown framework used previously to implement the Ecocat mapping tool.

Once you digest this info, I'm glad to meet with you to walk you through the Ecocat code developed previously.