1 / 16

Data Interchange

Data Interchange. The Problems. Codes, numbers and meaning Implied codes and units Within organisations Between organisations Between countries. Codes. Codes only have meaning when both sides agree on the meaning Me - 10=rainfall You - 10=water level Result - Chaos Me - PL=Polyethylene

mulan
Download Presentation

Data Interchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Interchange

  2. The Problems • Codes, numbers and meaning • Implied codes and units • Within organisations • Between organisations • Between countries

  3. Codes • Codes only have meaning when both sides agree on the meaning • Me - 10=rainfall • You - 10=water level • Result - Chaos • Me - PL=Polyethylene • You - PL=Polyproplyene • Result - Chaos

  4. Discrete Codes • Taken from limited possible range • May be possible to map one to another • Rainfall and water level can be coded anything, and always mapped • Quality codes cannot easily map between one organisation and another • Rock types would be nearly impossible

  5. Fuzzy Codes • Codes taken from one or more continuous ranges • SLMS = Sandy limestone with mud streaks • 2=mainly good edited data with occasional gaps of <60 minutes • 16=good enough to use

  6. Fuzzy codes • Need to impose limited discrete codes for mapping purposes • Will lose information during exchange • SLMS = Sandy limestone with mud streaks becomesLMST - Limestone • 2 and 16 become1 - Good

  7. Numbers • Numbers can only be interchanged in the same units • Me - rainfall in mm • You - rainfall in points • Result - chaos

  8. Time • Time datum changes from place to place • 12:15 - Eastern Standard, Central, Greenwich Mean, Pacific Standard? • Hydstra does not record time datum anywhere

  9. Implied Units • Temperature in gaugings • Pipe diameters in groundwater • Every real number in a database should have a unitcode next to it - but it doesn’t!

  10. Database Structures • You might be running HYDSYS 5, and I am running HYDSYS 6. • HYDSYS 6 combines sections into one table • Cannot export sections from 6 to 5

  11. Solutions • If everyone uses the same codes, units, datums, versions, there are no problems • IMPEXP within organisations works quite well

  12. Problems • If different organisations use different codes, you cannot exchange data. • One workaround is to keep separate systems in different directories • Another possible solution is to agree on common codes for interchange and provide translations at each end • HYDSYS 6 is much more strict about invalid codes

  13. Partial Solutions • HYTRAN does some conversions - variables, units, quality codes in TS data • Some rating conversion is supplied • IMPEXP can upgrade HYDSYS 5 exports before import to HYDSYS 6 (ish) • No general solution • No agreed interchange standards

  14. Where To Next? • More problems can be solved, but they will take a lot of work • The organisations with the greatest interest are small - eg MDBC, universities, consultants • It will probably never be possible to exchange heavily coded data like groundwater data

  15. Project? • Is there financial interest in proceeding? • Is Federal funding available? • Do we care? • No more work on interchange will be done without $$$

  16. Data Interchange

More Related