{"action":"opened","issue":{"url":"https://api.github.com/repos/uber/deck.gl/issues/2443","repository_url":"https://api.github.com/repos/uber/deck.gl","labels_url":"https://api.github.com/repos/uber/deck.gl/issues/2443/labels{/name}","comments_url":"https://api.github.com/repos/uber/deck.gl/issues/2443/comments","events_url":"https://api.github.com/repos/uber/deck.gl/issues/2443/events","html_url":"https://github.com/uber/deck.gl/issues/2443","id":381704497,"node_id":"MDU6SXNzdWUzODE3MDQ0OTc=","number":2443,"title":"H3 layer support?","user":{"login":"dcj","id":479535,"node_id":"MDQ6VXNlcjQ3OTUzNQ==","avatar_url":"https://avatars2.githubusercontent.com/u/479535?v=4","gravatar_id":"","url":"https://api.github.com/users/dcj","html_url":"https://github.com/dcj","followers_url":"https://api.github.com/users/dcj/followers","following_url":"https://api.github.com/users/dcj/following{/other_user}","gists_url":"https://api.github.com/users/dcj/gists{/gist_id}","starred_url":"https://api.github.com/users/dcj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dcj/subscriptions","organizations_url":"https://api.github.com/users/dcj/orgs","repos_url":"https://api.github.com/users/dcj/repos","events_url":"https://api.github.com/users/dcj/events{/privacy}","received_events_url":"https://api.github.com/users/dcj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-16T18:05:43Z","updated_at":"2018-11-16T18:05:43Z","closed_at":null,"author_association":"NONE","body":"Learned a lot more about H3 yesterday at the [Uber Open Summit](https://uberopen2018.splashthat.com), it would \"sure be nice\" :-) if there was H3 layer/support in deck.gl\r\n\r\nSome background on my application is described in issue #2428,  two near-term applications of an H3 layer for me include:\r\n\r\n- Compute/measure aircraft noise on an H3 grid, and visualize/present these results via deck.gl.  These  predictions/simulations, and/or aggregated measurements, are computationally intensive, and would most likely be pre-computed in the back end, per H3 index. \r\n- Compute maximum frequency and/or total count of aircraft over an H3 grid, again, per H3 index.\r\n\r\nIn both use-cases above, my dataset for these layers would (conceptually) be a list of objects, each object containing the H3 index, and various key/values to display."}}
{"actor":{"display_login":"dcj"}}