1 / 7

An E xchange S tandard for Veg etation Data

An E xchange S tandard for Veg etation Data. Simple XML describing complex relational structures. What is ESVeg?. The idea of the XML schema ESVeg was to create a common data standard allowing an exchange between different software tools

ivory
Download Presentation

An E xchange S tandard for Veg etation Data

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. An ExchangeStandard for Vegetation Data Simple XML describing complex relational structures

  2. What is ESVeg? • The idea of the XML schema ESVeg was to create a common data standard allowing an exchange between different software tools • One of the aims was an easy import of existing data from spreadsheets and local databases • To achieve this, some XML entities are copies of the relational tables, but others are denormalized summaries of several tables • The data elements have been reviewed during three annual workshops in Germany, and much of the pioneer work from the VegBank and MoReTax projects have been included

  3. Overlappings in three systems • VegBank is the most voluminous implementation • TurboVeg does not support taxonconcepts • VegetWeb is the new German online vegetation database • These three exemplary systems have much in common • An exchange format has to implement the maximum information TurboVeg VegetWeb VegBank

  4. ESVeg: 8 entities define one relevé • project: summarizes several vegetation observations about an defined period of time • plot: describes time independent information • observation: time dependent plot attributes • taxon: key list of all original and interpreted taxa • cover: contains the taxoncover per stratum • coverindex: free definable scale • reference: bibliographic information • userdefined: decribes userdefined attributes on entities

  5. Codes for unique identification • All distributed systems with data exchange have the same identification problem • Technical IDs are not suited for exchange between several systems • The solution are system wide unique codes • Which system is leading? • Code generation from existent attributes allows recognition in all systems • For example: authors + year + first character from title words form the reference code:Pfadenhauer, J.1969EWiJuidbA

  6. Example: XML entity observation <observation> <observationCode>BgWd042119690701</observationCode> <plot>BgWd0421</plot> <project>BgWd</project> <date>1969-07-01</date> <coverMethod>Braun-Blanquet</coverMethod> <reference>Pfadenhauer, J.1969EWiJuidbA</reference> <stratum1type>B1</stratum1type> <stratum1height>20</stratum1height> <stratum2type>S</stratum2type> <stratum2height>.6</stratum2height> <stratum3type>K</stratum3type> <stratum3cover>80</stratum3cover> </observation>

  7. Many systems, one standard? • An exchange standard allows decentralized data storage • The satellite systems export and import through this interface • Like VegBranch, ESVeg can be the entry point for data • While all attributes are exported, one system can import only its specific information

More Related