{"action":"created","issue":{"url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32","labels_url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32/comments","events_url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32/events","html_url":"https://github.com/Reading-eScience-Centre/coveragejson/issues/32","id":117104657,"number":32,"title":"Curvilinear grids / coordinate parameters","user":{"login":"neothemachine","id":530988,"avatar_url":"https://avatars.githubusercontent.com/u/530988?v=3","gravatar_id":"","url":"https://api.github.com/users/neothemachine","html_url":"https://github.com/neothemachine","followers_url":"https://api.github.com/users/neothemachine/followers","following_url":"https://api.github.com/users/neothemachine/following{/other_user}","gists_url":"https://api.github.com/users/neothemachine/gists{/gist_id}","starred_url":"https://api.github.com/users/neothemachine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/neothemachine/subscriptions","organizations_url":"https://api.github.com/users/neothemachine/orgs","repos_url":"https://api.github.com/users/neothemachine/repos","events_url":"https://api.github.com/users/neothemachine/events{/privacy}","received_events_url":"https://api.github.com/users/neothemachine/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/labels/needs%20discussion","name":"needs discussion","color":"207de5"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-11-16T11:28:44Z","updated_at":"2015-11-17T10:46:20Z","closed_at":null,"body":"Continuing from https://github.com/Reading-eScience-Centre/coveragejson/issues/24#issuecomment-151551355\r\n\r\n- curvilinear grids -> lat/lon are best exposed as ranges (as \"coordinate\" parameter) and not inside the domain\r\n- having \"coordinate parameters\" makes sense, e.g. for DEMs where the domain is just x and y, and the range is z\r\n- CRS definition for coordinate parameters should be similar to how it's done in the domain -> problem: how to specify CRS for single axis like \"latitude\"? maybe use parameter groups for that?"},"comment":{"url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/comments/157334119","html_url":"https://github.com/Reading-eScience-Centre/coveragejson/issues/32#issuecomment-157334119","issue_url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32","id":157334119,"user":{"login":"jonblower","id":6309993,"avatar_url":"https://avatars.githubusercontent.com/u/6309993?v=3","gravatar_id":"","url":"https://api.github.com/users/jonblower","html_url":"https://github.com/jonblower","followers_url":"https://api.github.com/users/jonblower/followers","following_url":"https://api.github.com/users/jonblower/following{/other_user}","gists_url":"https://api.github.com/users/jonblower/gists{/gist_id}","starred_url":"https://api.github.com/users/jonblower/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jonblower/subscriptions","organizations_url":"https://api.github.com/users/jonblower/orgs","repos_url":"https://api.github.com/users/jonblower/repos","events_url":"https://api.github.com/users/jonblower/events{/privacy}","received_events_url":"https://api.github.com/users/jonblower/received_events","type":"User","site_admin":false},"created_at":"2015-11-17T10:46:19Z","updated_at":"2015-11-17T10:46:19Z","body":"Yes, you want to distinguish coordinate information from \"variables\", I see what you mean now. Not sure what the best way to do this is. My feeling is to make everything a \"Parameter\" but add a property to coordinate parameters. (But if you wanted to use a different type, how about \"CoordinateParameter\"?)"}}