{"action":"opened","issue":{"url":"https://api.github.com/repos/hajicj/MUSCIMarker/issues/15","repository_url":"https://api.github.com/repos/hajicj/MUSCIMarker","labels_url":"https://api.github.com/repos/hajicj/MUSCIMarker/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/hajicj/MUSCIMarker/issues/15/comments","events_url":"https://api.github.com/repos/hajicj/MUSCIMarker/issues/15/events","html_url":"https://github.com/hajicj/MUSCIMarker/issues/15","id":182932913,"number":15,"title":"Change CropObject definition to be either X/Y/Width/Height, or Top/Left/Bottom/Right","user":{"login":"hajicj","id":4629511,"avatar_url":"https://avatars.githubusercontent.com/u/4629511?v=3","gravatar_id":"","url":"https://api.github.com/users/hajicj","html_url":"https://github.com/hajicj","followers_url":"https://api.github.com/users/hajicj/followers","following_url":"https://api.github.com/users/hajicj/following{/other_user}","gists_url":"https://api.github.com/users/hajicj/gists{/gist_id}","starred_url":"https://api.github.com/users/hajicj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hajicj/subscriptions","organizations_url":"https://api.github.com/users/hajicj/orgs","repos_url":"https://api.github.com/users/hajicj/repos","events_url":"https://api.github.com/users/hajicj/events{/privacy}","received_events_url":"https://api.github.com/users/hajicj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-13T23:56:45Z","updated_at":"2016-10-13T23:56:45Z","closed_at":null,"body":"X and Y is really ambiguous. There is an ugly coord-swap step in parsing, beccause X in CropObjects is originally column (horizontal direction) and Y is row (vertical direction), while Python uses row-first indexing. At the same time, it is not self-explanatory, which is always worse than self-explanatory in a data format. Top/Left/Bottom/Right is obvious, whether you need row-major or column-major ordering, top to bottom vs. bottom to top, etc.\r\n\r\nProposed fix: make it possible to encode CropObjects using both X/Y/W/H and T/L/B/R."}}
{"actor":{"display_login":"hajicj"}}