Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

DB Issue: Unit is attached with Value table #38

Open
arne-broering opened this issue Dec 17, 2013 · 2 comments
Open

DB Issue: Unit is attached with Value table #38

arne-broering opened this issue Dec 17, 2013 · 2 comments

Comments

@arne-broering
Copy link

Consequently, it is costly to determine the used unit for a specific observed property. This is needed for creating SensorML documents for a procedure (output element needs unit).

TODO: Clarify with EEA to change DB model.

@ridoo
Copy link
Member

ridoo commented Dec 19, 2013

Clarification includes the need to have hamonized UOM for a procedure. Having multiple UOM adds complexity in database. Also it leads to several output sections for the same phenomenon in the procedure's SensorML (DescribeSensor response format).

@ridoo
Copy link
Member

ridoo commented Dec 20, 2013

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants