{"action":"opened","issue":{"url":"https://api.github.com/repos/opengeospatial/geopackage-elevation/issues/3","labels_url":"https://api.github.com/repos/opengeospatial/geopackage-elevation/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/opengeospatial/geopackage-elevation/issues/3/comments","events_url":"https://api.github.com/repos/opengeospatial/geopackage-elevation/issues/3/events","html_url":"https://github.com/opengeospatial/geopackage-elevation/issues/3","id":105752432,"number":3,"title":"uom should be constrained from UCUM","user":{"login":"bradh","id":174642,"avatar_url":"https://avatars.githubusercontent.com/u/174642?v=3","gravatar_id":"","url":"https://api.github.com/users/bradh","html_url":"https://github.com/bradh","followers_url":"https://api.github.com/users/bradh/followers","following_url":"https://api.github.com/users/bradh/following{/other_user}","gists_url":"https://api.github.com/users/bradh/gists{/gist_id}","starred_url":"https://api.github.com/users/bradh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bradh/subscriptions","organizations_url":"https://api.github.com/users/bradh/orgs","repos_url":"https://api.github.com/users/bradh/repos","events_url":"https://api.github.com/users/bradh/events{/privacy}","received_events_url":"https://api.github.com/users/bradh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-10T07:56:40Z","updated_at":"2015-09-10T07:56:40Z","closed_at":null,"body":"The UCUM reference for `uom` should be profiled to restrict / constrain the number of values. At least it should be restricted to use of simple lengths (rather than a combination of things that end up being a length, like a velocity measure combined with a time measure).\r\n\r\nIdeally there would be a single unit of measure - SI metres. However realistically we'd need to add at least feet since the target audience is so US-centric.\r\n\r\nI think it is generally unreasonable to expect mobile application developers to use anything else (e.g. survey's chains, engineers chains, fathoms, miles, nautical miles) for elevation."}}