{"action":"created","issue":{"url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/105","labels_url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/105/labels{/name}","comments_url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/105/comments","events_url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/105/events","html_url":"https://github.com/USGS-CMG/usgs-cmg-portal/issues/105","id":105810895,"number":105,"title":"content of platform and crs variables correct?","user":{"login":"emontgomery-usgs","id":1771422,"avatar_url":"https://avatars.githubusercontent.com/u/1771422?v=3","gravatar_id":"","url":"https://api.github.com/users/emontgomery-usgs","html_url":"https://github.com/emontgomery-usgs","followers_url":"https://api.github.com/users/emontgomery-usgs/followers","following_url":"https://api.github.com/users/emontgomery-usgs/following{/other_user}","gists_url":"https://api.github.com/users/emontgomery-usgs/gists{/gist_id}","starred_url":"https://api.github.com/users/emontgomery-usgs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emontgomery-usgs/subscriptions","organizations_url":"https://api.github.com/users/emontgomery-usgs/orgs","repos_url":"https://api.github.com/users/emontgomery-usgs/repos","events_url":"https://api.github.com/users/emontgomery-usgs/events{/privacy}","received_events_url":"https://api.github.com/users/emontgomery-usgs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-09-10T13:54:29Z","updated_at":"2015-10-23T15:49:51Z","closed_at":null,"body":"@kwilcox @rsignell-usgs \r\nFor the 'platform' and 'crs' variables in the CF-1.6 files, does the -2147483647 indicate missing or unknown?  I don't see the equivalent of a fill_value for these variables, so how is a client supposed to understand this content?\r\n\r\nCan we fabricate better answers for these variables?  If they are not mandatory for the data model, can we get rid of them?  Below are examples of both variables from /MVCO_11/9102sc-a.nc.\r\n\r\n```\r\nDataset {\r\n    Int32 platform;\r\n} usgs/data2/emontgomery/stellwagen/CF-1.6/MVCO_11/9102sc-a.nc\r\n---------------------------------------------\r\nplatform, -2147483647\r\n\r\nDataset {\r\n    Int32 crs;\r\n} usgs/data2/emontgomery/stellwagen/CF-1.6/MVCO_11/9102sc-a.nc\r\n---------------------------------------------\r\ncrs, -2147483647\r\n```"},"comment":{"url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/comments/150613696","html_url":"https://github.com/USGS-CMG/usgs-cmg-portal/issues/105#issuecomment-150613696","issue_url":"https://api.github.com/repos/USGS-CMG/usgs-cmg-portal/issues/105","id":150613696,"user":{"login":"emontgomery-usgs","id":1771422,"avatar_url":"https://avatars.githubusercontent.com/u/1771422?v=3","gravatar_id":"","url":"https://api.github.com/users/emontgomery-usgs","html_url":"https://github.com/emontgomery-usgs","followers_url":"https://api.github.com/users/emontgomery-usgs/followers","following_url":"https://api.github.com/users/emontgomery-usgs/following{/other_user}","gists_url":"https://api.github.com/users/emontgomery-usgs/gists{/gist_id}","starred_url":"https://api.github.com/users/emontgomery-usgs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emontgomery-usgs/subscriptions","organizations_url":"https://api.github.com/users/emontgomery-usgs/orgs","repos_url":"https://api.github.com/users/emontgomery-usgs/repos","events_url":"https://api.github.com/users/emontgomery-usgs/events{/privacy}","received_events_url":"https://api.github.com/users/emontgomery-usgs/received_events","type":"User","site_admin":false},"created_at":"2015-10-23T15:49:51Z","updated_at":"2015-10-23T15:49:51Z","body":"@kwilcox  Sorry, I was confusing.  I only want these attributes in the \"platform\" variable.  I also want the attributes in the platform variable to be consistent for all the instruments (files) on 1 platform (920 in previous example).  Some platforms only support one instrument, others like 920 support many.\r\n\r\nI think \"fixed\" may be important for the NODC/ACDD vocabularies, and is a step more abstract as a concept.  More specific information that could go in a \"type\" attribute; as I see it, \"tripod\", \"quadpod\" are more specific descriptions for a \"fixed\" platform."}}