I will need a data upload application to be developed to accommodate additional data as part of this project. A simple Excel file upload type application will work. It should be able to do some data redundancy checking to prevent duplicate data importing
Then, to make the data easily usable, we will need a graphing application similar to what we have for the surface water stage and discharge data. at
<[url removed, login to view]>
We want it to be able to plot water levels in depth to water and/or water elevation for specified periods of record. We want it to be able to accommodate plotting more than one well??"up to about 6 wells would be useful--per graph for the specified period of time for comparison purposes.
Also, we would like for the graphs to be able to become "presentation ready" with a click. This is best described by example.
**USGS Real-Time Data** link in our **Water Data** portion of our web site. Any of the graphs that come up on that link have a link named **Create presentation-quality graph** underneath them. What comes up next is a cleaned up picture of the graph. This feature will enable us to incorporate visual data into dam safety discussions and considerations.
I will need any uploaded spreadsheet to fit into the SQL database structure with fieldnames and data types:
ID NUMBER (key field)
I expect the uploading Excel files to have the fields/structure:
So, the programming will have to include appropriate autonumbering functions to insert ID numbers into the ID field to fit in with and not duplicate those already in the SQL database. It will also need to check for basic duplication, like our groundwater level data upload does.
Later, I will also be turning another dam safety database into an SQL database that we will need to add to through Excel spreadsheets. The structure of this SQL database will be similar, but it also adds a temperature field named TEMP:
ID NUMBER (key)
The uploading Excel spreadsheets will have this structure also, except they also will need the ID field to be inserted through appropriate autonumbering functions, and have basic duplication checking as well.
The Access databases I am currently pulling together to form what will become the SQL database can be found in the attached files All Historic Dam [url removed, login to view]
And “2607 GWE99Eng?? is the database in there with the structure working best to be the recipient SQL database.
An example of an Excel spreadsheet that I have uploaded to All Historic Dam [url removed, login to view] can be found at the file:
[url removed, login to view]
worksheets EnglewoodData, GermantownData, HuffmanData, LockingtonData, TaylorsvilleData.
--But, I had to insert the ID field with preset number ranges to get them to import into All Historic Dam Data.mdb. That is one of the problems I need the programming to help me with??"automatic ID numbering without duplications to the SQL.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
ASP (VB Script) MS SQL Server
** We will be mirgating to Office 2007, so any code will HAVE to be able to support Both office XP and Office 2007 Excel Versions.