{"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:50:26Z","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/157335312","html_url":"https://github.com/Reading-eScience-Centre/coveragejson/issues/32#issuecomment-157335312","issue_url":"https://api.github.com/repos/Reading-eScience-Centre/coveragejson/issues/32","id":157335312,"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},"created_at":"2015-11-17T10:50:26Z","updated_at":"2015-11-17T10:50:26Z","body":"\"CoordinateParameter\" sounds like it also applies to measured \ncoordinates. A property would be possible, yes, like `\"auxiliary\": true` \nor something like that.\n"}}