{"action":"created","issue":{"url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/7","repository_url":"https://api.github.com/repos/FugroRoames/PointClouds.jl","labels_url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/7/comments","events_url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/7/events","html_url":"https://github.com/FugroRoames/PointClouds.jl/issues/7","id":172858814,"number":7,"title":"API worries: What should a PointCloud be?","user":{"login":"c42f","id":601473,"avatar_url":"https://avatars.githubusercontent.com/u/601473?v=3","gravatar_id":"","url":"https://api.github.com/users/c42f","html_url":"https://github.com/c42f","followers_url":"https://api.github.com/users/c42f/followers","following_url":"https://api.github.com/users/c42f/following{/other_user}","gists_url":"https://api.github.com/users/c42f/gists{/gist_id}","starred_url":"https://api.github.com/users/c42f/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/c42f/subscriptions","organizations_url":"https://api.github.com/users/c42f/orgs","repos_url":"https://api.github.com/users/c42f/repos","events_url":"https://api.github.com/users/c42f/events{/privacy}","received_events_url":"https://api.github.com/users/c42f/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-08-24T03:51:29Z","updated_at":"2016-08-25T03:50:48Z","closed_at":null,"body":"At the moment it's a table with a spatial index.  Ie, each point is a row in the table, and columns are point attributes, which are shared by all points.  The spatial index is a KDTree by default.\r\n\r\nHowever, it's not clear\r\n\r\n* Whether a spatial index is always required\r\n* That a KDTree is always the right choice\r\n* Whether we should just be wrapping an existing table-like data structure (DataFrame?  TypedTable?  more general abstract table type?)  The choice here can impact performance a lot."},"comment":{"url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/comments/242274436","html_url":"https://github.com/FugroRoames/PointClouds.jl/issues/7#issuecomment-242274436","issue_url":"https://api.github.com/repos/FugroRoames/PointClouds.jl/issues/7","id":242274436,"user":{"login":"c42f","id":601473,"avatar_url":"https://avatars.githubusercontent.com/u/601473?v=3","gravatar_id":"","url":"https://api.github.com/users/c42f","html_url":"https://github.com/c42f","followers_url":"https://api.github.com/users/c42f/followers","following_url":"https://api.github.com/users/c42f/following{/other_user}","gists_url":"https://api.github.com/users/c42f/gists{/gist_id}","starred_url":"https://api.github.com/users/c42f/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/c42f/subscriptions","organizations_url":"https://api.github.com/users/c42f/orgs","repos_url":"https://api.github.com/users/c42f/repos","events_url":"https://api.github.com/users/c42f/events{/privacy}","received_events_url":"https://api.github.com/users/c42f/received_events","type":"User","site_admin":false},"created_at":"2016-08-25T03:50:48Z","updated_at":"2016-08-25T03:50:48Z","body":"Yes, @OmriRoames this is exactly the point: the best index is the one which is specialized to the problem.  A KDTree is just a robust default.\r\n\r\n@andyferris it might be just a table, and that's fine too (though maybe no point even having this package if that's the case ;-) )\r\n\r\nMaybe the answer is \"A generic point cloud is an abstract table; a `PointCloud` is an abstract table which happens to have a spatial index\"?"}}
{"actor":{"display_login":"c42f"}}