Versions Compared

Old Version 25

changes.mady.by.user Javier Sanchez

Saved on

compared with

New Version Current

changes.mady.by.user Edmond Chuc

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Encoding each row in RDF requires:

  • Status
    colourRed
    titletodo

Comments

  • The “hits” field is captured as an observation with the parameter “basal area count”. This is fine but we may not need to capture this since the stand basal area is derived from the number of hits, and the stand basal area is the measurement that users are interested in. This may cause confusion especially since they are both using the same method.

  • The parameter used to record the basal area is wrong. The basal area calculated in this table is the tree basal area.

Mapping Table

Source Column

Destination RDF Predicate

Comments

id

dct:identifier, rdfs:label

site_location_visit_id

plot:wasSubActivityOf

Domain: ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

Range: plot:SiteVisit

veg_barcode

sosa:hasSample

Domain: ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

Range: sosa:Sample

  • sosa:hasResult:

    • rdf:type: data:Text

    • data:value: veg_barcode

Create sosa:Sampling instance

point_id

ssn-ext:hasMember, sosa:hasResult

Member of ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

  • sosa:observedProperty:

    Status
    colourRed
    titlereviewed
    Point ID as described in plot layout, , can this be linked to table ‘site location point’? not sure if this should be part of an observation collection?

  • sosa:usedProcedure: Plot layout and positioning

  • sosa:hasResult:

    • rdf:type: data:Concept

    • data:value: value from collection Basal Point

hits

ssn-ext:hasMember, sosa:hasResult

Member of ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

  • sosa:observedProperty: Basal Area Count

    Status
    colourYellow
    titlereview required
    TS, this is correct

  • sosa:usedProcedure: Basal area method

  • sosa:hasResult:

    • rdf:type: data:Count

    • data:value: hits

basal_area_factor

ssn-ext:hasMember, sosa:hasResult

Status
colourYellow
titlereview
- should this be modelled the same as CORVEG using sosa:Input?

Member of ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

  • sosa:observedProperty: Basal Area Factor

  • sosa:usedProcedure: Basal area method

  • sosa:hasResult:

    • rdf:type: data:QuantitativeMeasure

    • data:standard:

      Status
      colourRed
      titletodo
      - it should probably be a controlled vocabulary like CORVEG. TS, yes values are numerical and can only be 0.1, 0.25, 0.5, 0.75, 1, 2

  • data:value: basal_area_factor

basal_area

ssn-ext:hasMember, sosa:hasResult

Member of ssn-ext:ObservationCollection with dct:type

Status
colourYellow
titleTERN:
Flora Species

Status
colourGreen
titleAUSPLOTS:
Plant species per stratum

  • sosa:observedProperty: Basal Area

  • sosa:usedProcedure: Basal area method

  • sosa:hasResult:

    • rdf:type: data:QuantitativeMeasure

    • data:standard:

      Status
      colourRed
      titletodo
      unit of measurement is m2/ha unit:M2-PER-HA

    • data:value: basal_area

Example Row

...