1 / 39

Fluvial Architecture Knowledge Transfer System (FAKTS): database interrogation through SQL queries

Fluvial Architecture Knowledge Transfer System (FAKTS): database interrogation through SQL queries. Luca Colombera, Nigel P. Mountney. Fluvial & Eolian Research Group – University of Leeds. Querying FAKTS. Two alternative ways to interrogate FAKTS :

imogene-phelps
Download Presentation

Fluvial Architecture Knowledge Transfer System (FAKTS): database interrogation through SQL queries

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. Fluvial Architecture Knowledge Transfer System (FAKTS):database interrogation through SQL queries Luca Colombera, Nigel P. Mountney Fluvial & Eolian Research Group – University of Leeds

  2. Querying FAKTS • Two alternative ways to interrogate FAKTS: • WEB-BASED FRONT-END hosted on FRG website. • Easy to use, but of limited capability. • Queries can be run on the website without requiring download of software or data. • SQL QUERIES on MySQL. • More difficult to use, but it enables full database interrogation. • Queries are run locally, requiring download of software (MySQL and HeidiSQL) and database.

  3. MySQL queries • Fully searchable • but requires SQL • knowledge: • output referring to any type of genetic unit can be generated; • any type of output can be queried (including proportions, grain size, etc.); • all available filters can be applied; • it is possible to tailor the query so that output does not require further data analysis.

  4. MySQL queries FAKTS + documents MySQL HeidiSQL Interrogation of FAKTS through MySQL queries requires having MySQL (back-end) and HeidiSQL (front-end) installed locally. The software, database and documentation can be downloaded from the FRG website (Doc ID: 598)

  5. MySQL queries Once all software is installed (see FAKTS manual for instructions), users can login to the local MySQL server using HeidiSQL.

  6. MySQL queries The screen will appear as above: now FAKTS can be loaded.

  7. MySQL queries The FAKTS dump file needs to be chosen, opened and run.

  8. MySQL queries The FAKTS dump file needs to be chosen, opened and run.

  9. MySQL queries Now, if you refresh (F5)…

  10. MySQL queries …the FAKTS database will appear on the database panel.

  11. MySQL queries If you click on the database, you will select it.

  12. MySQL queries You can now query FAKTS by writing or loading a query in a tab.

  13. MySQL queries You can write a query in the query editor panel.

  14. MySQL queries Information on SQL syntax and functions can be found in Chapters 12 and 13 of MySQL manual: http://dev.mysql.com/doc/refman/5.6/en/index.html.

  15. MySQL queries For example, we can write a query for the thickness of channel complexes from sparsely vegetated basins.

  16. MySQL queries Then we can click on ‘Execute SQL’, or press F9.

  17. MySQL queries Results will appear in the panel at the bottom.

  18. MySQL queries Let’s open a new query tab and load a template query.

  19. MySQL queries Click on ‘Load SQL file’ or press ctrl + O.

  20. MySQL queries The ‘template query’ folder contains over 50 SQL scripts.

  21. MySQL queries To guide the choice of a script suitable for your specific scopes, the ‘template query’ document should be referred to.

  22. MySQL queries To guide the choice of a script suitable for your specific scopes, the ‘template query’ document should be referred to.

  23. MySQL queries Let’s say we are interested in the types and thicknesses of facies units overlying a 4th-order channel base: we open tq_32.

  24. MySQL queries In particular, we are interested in information on facies units overlying the base of crevasse channels.

  25. MySQL queries After identifying the clause that specifies the architectural element type, we edit the script changing ‘CH’ into ‘CR’.

  26. MySQL queries After editing the script, we can run the query.

  27. MySQL queries The results are returned in the bottom panel.

  28. MySQL queries The query we have just run entailed the generation of a temporary table: if we want to edit and run the same script we need to…

  29. MySQL queries …either edit the script re-naming the temporary table (in addition to the changes required for obtaining the desired output),…

  30. MySQL queries …or open a new session, in which the same query can be run, without requiring re-naming the temporary table.

  31. MySQL queries …or open a new session, in which the same query can be run, without requiring re-naming the temporary table.

  32. MySQL queries The new output – referring to facies units overlying the base of LA barform elements – is now displayed.

  33. MySQL queries The queries can be designed in a way that all required functions are included: the results do not require any further processing.

  34. MySQL queries If we want to export the results: we can right click on them…

  35. MySQL queries …and select ‘Export grid rows’.

  36. MySQL queries The results can now be exported conveniently as CSV file.

  37. MySQL queries After exporting either all the results or the selected rows...

  38. MySQL queries …the FAKTS output can be further analysed or graphed after opening the CSV file using Excel.

  39. Conclusions • FAKTS interrogation • FRG website • MySQL queries • HeidiSQL front-end requires basic SQL knowledge; • output referring to any type of genetic unit can be generated; • any type of output can be queried (including proportions, grain size, etc.); • all available filters can be applied; • it is possible to tailor the query so that output does not require further data analysis. • user-friendly menu-driven front-end; • depositional and architectural elements currently included; • dimension and transition data currently made available; • limited number of filters; • output is given in the form of raw data, which may require further analysis. • Further developments will follow.

More Related