Ticket #1046 (closed issue: worksforme)

Opened 10 years ago

Last modified 10 years ago

[M] role and signficance of MO_Station cf SamplingFeature and MO_Platform

Reported by: lawrence Owned by: lawrence
Priority: required Milestone: NDG3
Component: MOLES Version:
Keywords: simonc Cc:

Description

We need to decide on whether station is different from either a sampling feature or a platform ...

Currently examples of stations include: Chilbolton, Boreholes etc, where the characteristics extend beyond the geometric properties of a SF alone.

(Assigned to Bryan as a proxy for Simon)

Attachments

Summary Platform 3.2 rev1981.png Download (155.8 KB) - added by lawrence 10 years ago.

Change History

comment:1 Changed 10 years ago by lawrence

  • Status changed from new to assigned

Changed 10 years ago by lawrence

comment:2 Changed 10 years ago by lawrence

Email from Simon: I now think there is a case to be made that MO_Station is a specialization of MI_Platform, one which doesn't move. It may also be associated with a SamplingPoint? or other SamplingFeatures?, but this is in the context of a deployment. If the station is not used for in-situ observations, then there may not be an associated SamplingPoint? at all. We want to utilize the same mountedOn-instrument association to instruments, with a DeploymentPeriod? association class, so I've resolved this by removing the MO_Station class and adding a 'Stationary' option to the PlatformTypeCode?. I also added LandVehicle?, since it seemed to be missing.

This takes me back to the relationship between deployment and instrument. In ISO 19115-2 there is not direct link - there is always a platform involved. I have resisted this in the past, because it seemed superfluous for field-trips, which sometimes involve walking, but maybe it is simpler to always have a platform object there, even if it is 'nominal'.

comment:3 Changed 10 years ago by lawrence

  • Status changed from assigned to closed
  • Resolution set to worksforme

Resolved in current UML, with explanatory notes.

Note: See TracTickets for help on using tickets.