1 / 21

GISIN Data Model Concepts

GISIN Data Model Concepts. Enabling Invasive Species Data Interchange. GISIN technical team. GISIN Training. Protocols. Protocol = Agreed upon language for data exchange File formats, HTTP, KML Dictates what can and cannot be exchagned Types of protocols DarwinCore: Loose

garin
Télécharger la présentation

GISIN Data Model Concepts

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. GISIN Data Model Concepts Enabling Invasive Species Data Interchange GISIN technical team GISIN Training

  2. Protocols • Protocol = Agreed upon language for data exchange • File formats, HTTP, KML • Dictates what can and cannot be exchagned • Types of protocols • DarwinCore: Loose • Country: United States, US, Estados Unidos, etc. • GISIN: “tighter” • UN Country codes

  3. GISIN Protocol • Based on DarwinCore • Added concepts for invasive species • Provided controlled vocabularies where possible and needed • Data Models • Occurrences • SpeciesStatus • SpeciesResourceURLs

  4. GISIN data models • Data model = data type of interest • Six data models • Three implemented • Species Resource URL • Species status • Occurrence • Three defined, not implemented • Management status • Impact status • Dispersal status • See the GISIN protocol for more information http://www.gisin.org/cwis438/websites/GISINDirectory/Tech/Protocol_Home.php

  5. Some Definitions • Data Models: Type of data • Concepts • Fields • Parameters • Data types: • String: Names, descriptions • Enumerated: Yes/No, Indigenous/Exotic • Date: “2010-11-20” • Integer: Number of records to return • Floating Point: Longitude/Latitude

  6. Data model concepts • Concepts = elements within data model • Common and data model specific • Required and optional • Free form and controlled vocabulary • Used standards where exist

  7. Enumerated Controlled Vocabularies Allows interchange of data at different levels of detail Do not capture all the detail of each provider Intended to be mutually exclusive

  8. Common Field Concepts • Descriptive • citation • memo • language (r) • Species • scientificName (R) • kingdom (R) • globalUniqueIdentifier • Dates • modified • endValidDate • startValidDate • Location • countryCode • stateProvince • county • localityName • localityType • locationStandard • locationValue

  9. GUIDs • Global unique identifier • Will accept existing GUIDs, if provided • If not provided, recommend DwC-recommended standard and authority for persistent and resolvable GUIDs • www.gisin.org/guid will be the authority for now. • GUID permalink gisin.org/guid/[InstitutionCode]/[CollectionCode]/[CatalogNumber] Example: gisin.org/guid/niiss/godm/34654

  10. Descriptive Concepts • Language • Required if any text is provided • Memo • Additional information from providers • Citation • Appropriate citation for each record • Must be maintained as data is repeated (retain previous provider citation) • GUIDs also helpful for this Available for all data models.

  11. Species (Required - all) • Scientific Name • Specific epithet for the species • Prefer “Genus species” without author • “Bromus tectorum” • “Tamarix” • Kingdom (enumerated) • Required to remove ambiguity • Can be set for an entire file

  12. Date • Date format must be: YYYY-MM-DD • Several date fields • Specify temporal precision • Year, month, or day • Start and end date can be the same

  13. Location • One required by: • SpeciesStatus • Occurrence • 3 Methods of specifying location in use: • Latitude/Longitude (Occurrence only) • Locality: An enumerated type with a name • Location: an enumerated standard with a code

  14. Locality • countryCode • Standard: Country code (ISO 3166) • stateProvince • Text in country’s primary language • county • Text in country’s primary language • Locality • localityType (enumerated): Waterbody, Locality (city), Island, etc. • localityName: Name of the area

  15. Location • locationStandad: • USA_FIPS, USA_HUC, AR_PostalCode • locationValue: • Varies with standard Contact us about adding additional types or standards.

  16. Latitude/Longitude • Required: • Decimal Latitude: 40.123 • Decimal Longitude: -105.23 • Optional: • geodeticDatum*: WGS84, HARN • coordinateUncertaintyInMeters • georeferenceProtocol (enumerated) *Datum should be required

  17. Occurrences • Required Concepts: • scientificName • kingdom • Any type of location • Coordinates, Locality, or Location • Optional: • startCollectionDate • endCollectionDate • collectionDatePrecision • georeferenceProtocol • coordinateUncertaintyInMeters • Datum

  18. SpeciesStatus • Required: • scientificName • kingdom • Locality or location Model specific • harmful • origin • presence • Optional: • startValidDate, • endValidDate • validDatePrecision • abundance • distribution • persistence • rateOfSpread • regulartoryListing • trend • publicationDate • publicationDatePrecision

  19. Presence • Presence: • Unknown • Absent • SometimesPresent • Present • Reported

  20. Harmful and Origin • Harmful: • Unknown • Yes • Potentially • No • Together: • Harmful = Yes, Origin = Exotic -> Invasive • Origin: • Unknown • Indigenous • Exotic

  21. SpeciesResourceURL • Required: • scientificName, kingdom • resourceType: • Profile, Expert list, Image, Video, Reference list, Identification key, Risk assessment, Unknown • URL: • Full Uniform Resource Locator • http://www.issg.org/database/species/ecology.asp?si=1538&fr=1&sts=&lang=EN

More Related