Submissions:Trajectory

From Odp

Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 12794

Graphical representation

Diagram

Image:Trajectory.png

General description

Name: Trajectory
Submitted by: AdilaKrisnadhi
Also Known As:
Intent: The pattern provides a model of trajectory, which is understood as a sequence of spatiotemporal points. The model generalizing the Semantic Trajectory pattern from [Hu, et al., COSIT 2013] by employing the notion of place, instead of location/geo-coordinate, to represent the spatial extent of the trajectory. This pattern is suitable for a variety of trajectory datasets and easily extendible by by aligning to or matching with existing trajectory ontologies, foundational ontologies, or other domain specific vocabularies.
Domains:

General, Earth Science or Geoscience

Competency Questions:
  • Show the birds which stop at x and y
  • Show the birds which move at a ground speed of 0.4 m/s
  • Show the trajectories of rivers which cross national parks
  • Where are the ports at which the oceanographic cruise A3221 stopped after leaving Woods Hole?
  • List the places and times that represent the spatiotemporal extent of the 1990 World Chess Championship event
Solution description: This pattern is reengineered from [Hu, et al., COSIT 2013] with changes as described in the intent of the pattern.
Reusable OWL Building Block: http://krisnadhi.github.io/onto/trajectory.owl (185)
Consequences: Unlike the original version of Semantic Trajectory, this pattern omits the hook to the data source for fixes (which was a subclass of ssn:Device) because instead of location/geo-coordinate, the notion of place is employed to capture the spatial extent. Nevertheless, it should be relatively straightforward to extend this version if the user wishes to attach data source information to the fixes.
Scenarios: Mike's trip to the GeoVoCamp 2012 from his home integrating data from GPS device, vehicle information, and personal information.A toucan flies through the air as recorded by researchers in the MoveBank.The 1990 World Chess Championship event that was held in two locations at two different times.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
  • Yingjie Hu; Krzysztof Janowicz; David Carral; Simon Scheider; Werner Kuhn; Gary Berg-Cross; Pascal Hitzler; Mike Dean; Dave Kolas: A Geo-ontology Design Pattern for Semantic Trajectories. In International Conference on Spatial Information Theory (COSIT) 2013) 438-456
Has Components:
Specialization Of:
Related CPs:


Elements

The Trajectory Content OP locally defines the following ontology elements:

ObjectProperty atPlace (owl:ObjectProperty) Connects anything (including fixes in this pattern) to Place.
atPlace page
ObjectProperty atTime (owl:ObjectProperty) Connects anything (including fixes in this pattern) to TimeEntity
atTime page
ObjectProperty endsAt (owl:ObjectProperty) Connects a segment to the fix it ends at.
endsAt page
ObjectProperty hasAttribute (owl:ObjectProperty) Connects a fix or a segment to an additional information as represented by an instance of Attribute.
hasAttribute page
ObjectProperty hasFix (owl:ObjectProperty) Relating the trajectory to each of its fixes.
hasFix page
ObjectProperty hasSegment (owl:ObjectProperty) Relating the trajectory to each of its segments.
hasSegment page
ObjectProperty hasTrajectory (owl:ObjectProperty) Anything that has a trajectory can use this property to connect it to the trajectory instance.
hasTrajectory page
ObjectProperty nextFix (owl:ObjectProperty) Relates one fix to the immediately following fix in the sequence.
nextFix page
ObjectProperty startsFrom (owl:ObjectProperty) Connects a segment to the fix it starts from.
startsFrom page
ObjectProperty traversedBy (owl:ObjectProperty) Connect a segment to the moving object that traverses it.
traversedBy page
Class Attribute (owl:Class) Captures additional information that enriches some fix or segment.
Attribute page
Class EndingFix (owl:Class) The last fix in a particular sequence of fixes.
EndingFix page
Class Fix (owl:Class) Describes a fix, which is an adorned spatiotemporal point. A sequence of fixes form the trajectory.
Fix page
Class MovingObject (owl:Class) This is the hook to an ontology/pattern that describes the moving object, if any, which moves along the trajectory.
MovingObject page
Class Place (owl:Class) This is the hook to other pattern/ontology that describes the notion of place, which is more general than just a location/geo-coordinate.
Place page
Class Segment (owl:Class) The Segment class captures the "connection" between two consecutive fixes. That is, a segment starts from a fix and ends at another fix. If the pattern is used to model the trajectory of some moving object, each segment is traversed by that moving object. Additional information about a segment can be attached as attributes.
Segment page
Class StartingFix (owl:Class) The first fix in a particular sequence of fixes.
StartingFix page
Class TimeEntity (owl:Class) The hook to class/pattern/ontology that models time, this class provides the temporal extent of the trajectory. One example of time model is the W3C Time Ontology.
TimeEntity page
Class Trajectory (owl:Class) Represents the notion of trajectory, this is the main class that can be hooked with other patterns that use the Trajectory pattern. Trajectory in this model is understood as a sequence of fixes connected by segments. There is exactly one starting fix and exactly one ending fix. Each fix has a temporal extent and a place (which is more general than just a location).
Trajectory page

Additional information

Scenarios

Scenarios about Trajectory

No scenario is added to this Content OP.

Reviews

Reviews about Trajectory

There is no review about this proposal. This revision (revision ID 12794) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Trajectory

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers