OGC compliant XML Export from Access Database

Data is required to be exported from a database in an Open Geoscience Consortium xml format as specified by the Australian Bureau of Meturology and called the Water Data Transfer Format.? This work is to write the program to provide the export from an existing database. ## Deliverables This project will be awarded based firstly on developer experience and likely product quality, with price a second consideration.? (the bid will need to describe relevant experience or has a lower chance of being considered) ? The following categories of data will need to be reported (1, 2, 3 (except f), 4, ? ? 9) as described in the following link.? Other categories may be added as a stage 2. <[login to view URL]> ? ? The developer will need to familiarise themselves with the documentation for the current (v1) transfer format, which can be downloaded from: <[login to view URL]> ? ? Particular attention is directed to the section titled. ? ? The developer will need to validate their work against the validation tool provide by the department: <[login to view URL]> ? ? The software must be written in VB.Net? or C#, using VS 2008.? Export code should be well organised in logical components,? include comments for clarification,? and? distinct from the interface. The GUI will be a simple prompt for the database name, which can also be passed as a startup parameter (so it can be launched from another program), and another to ask where the output file should be saved. The developer will be expected to be familiar with XML.? The developer will also need to be familiary with GIS, Environmental, Timeseries data. The developer should direct all enquiries through us, rather than contacting the department directly. The Access database which is being used for storage of the data is included.? The developer should review the database against the requirements and indicate any alterations that may be required.? In reference to the categories of data listed in the first paragraph the data tables are: 1.? ? ? ? ? ? Watercourses: Table: Surface_Water_Flow 2.? ? ? ? ? ? Groundwater: Tables: WaterLevel and Wells *? *The developer may need to read the section in the v1 transfer format documentation (second paragraph) titled “special section on ground water encoding in WDTF??? Note that water pressure is not stored, only data recorded in depths or elevation is to be supported. 3.? ? ? ? ? ? Levels and Volumes: Tables: Surface_Water_Storage, Surface_Water_Release, Pumping (for 3d) 4.? ? ? ? ? ? Meteorological Information: Tables: Rainfall (4a), Wind(4b), Evaporation(4c), Temperature_Humidity_Pressure_Deficit (4f,4g, 4h,4i), Solar_Exposure(4d), Solar_Irradiance(4e) ? ? ? ? ? ? ? 9.? ? ? Water Quality Information ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tables:Chemistry_Samples, Chemistry_Results, zRef_Chemistry_Lookup, zRef_ConvertUnits ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *Some fields that are in the original database but not relevant for this work are removed for ease of clarity. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *The Chemistry Results will need a unit conversion, as given in the example query in the database ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *The different parameters (ie pH, Turbidity) will always have a unique/consistent ChemCode Other relevant tables are: Location, Project (contains datum, co-ordinate system)