SQL Server TSQL metrological model library

A small library of SQL Server SPs and functions needed for the modelling of metrological data. This project requires reading and interpreting scientific papers and converting algebra into code. This area is well researched and there are many published models to draw from. Appropriate research into suitable scientific methods should be considered as part of this project. See attached paper and embedded links for some ideas/methods and starting points. This project is important to us but it should be mentioned that we are looking for good TSQL programmers who can research and adapt scientific models for future larger projects. The performance and quality of this projects deliverables will be considered when choosing developers for future assignments. A sample DB schema with sample data will be provided upon project initialisation. ## Deliverables Appropriate research into suitable scientific methods should be considered as part of this project. See attached paper and embedded links for some ideas/methods and starting points. We are aware that the phrase ‘Appropriate research’ appears open ended though we will be looking for bidders who are confident and ideally experienced in this subject area. We believe that this project will require a maximum 1 week research. If you are not experienced in reading and interpreting scientific papers and converting algebra into code then this project is not for you. Below is a list of models that we require as SQL Server Stored Procedures/functions. NOTE The word ‘Considering’ signifies input parameters. Whenever possible these should be function/SP parameters though some models my require data to be queried from the database within the SP/Function i.e. Soil Temperature model given the lag effect. The phrase ‘Optionally considering’ indicates a separate model that produces the same result. The reason for this is that not all variables are available all of the time i.e. not all weather stations record the same parameters. If the phrase ‘Optionally considering’ is mentioned more than once for a particular model then this indicates more than one variation. We will consider bids for individual models depending on response though prefer the project to be handled as a whole. Hourly air temperature from daily observations Considering: Minimum and maximum daily temperature Optionally considering: Daily observed temperatures at 6, 12, 18 UTC Hourly relative humidity Considering: Daily minimum and maximum relative humidity Daily solar radiation Considering: Date Latitude Optionally considering: Hours of daylight Cloud cover (eights) Low level cloud cover (eights) Derived hourly Soil Temperature at a given depth Considering: Soil depth Hourly air temperature at ground level Soil moisture due to precipitation Vegetation canopy cover (i.e. by crops) Optionally considering: Snow cover (depth) Daily solar radiation Some starting points: [login to view URL]~daisy/ftp/[login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] A simple and efficient method of calculating average daily soil temperature at a given depth would also be desirable extra module though this is open to discussion. This module would not be one that feeds from the hourly model but one that uses daily min/max temperatures and precipitation. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 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) ## Platform Coding Practice As stated SQL Server 2000 TSQL Stored procedures and functions should e used. No SQL Server external applications should be used. The code should be efficient The code must include appropriate error handling that raises a message that indicates what failed, why, the last row count (if applicable), transaction control i.e. rollbacks (if applicable). Stored Procedure(s)/Functions must adhere to a set of provided company standards. The TSQL should not be dynamic i.e. build queries as strings Basic documentation should be provided (parameters, units, references) All code must be commented with references to methods (scientific papers etc) where applicable.