{"action":"created","issue":{"url":"https://api.github.com/repos/opengeospatial/geopackage/issues/77","labels_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/77/comments","events_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/77/events","html_url":"https://github.com/opengeospatial/geopackage/issues/77","id":47155343,"number":77,"title":"Request for multiple geometry columns","user":{"login":"Pat28","id":2316171,"avatar_url":"https://avatars.githubusercontent.com/u/2316171?v=3","gravatar_id":"","url":"https://api.github.com/users/Pat28","html_url":"https://github.com/Pat28","followers_url":"https://api.github.com/users/Pat28/followers","following_url":"https://api.github.com/users/Pat28/following{/other_user}","gists_url":"https://api.github.com/users/Pat28/gists{/gist_id}","starred_url":"https://api.github.com/users/Pat28/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Pat28/subscriptions","organizations_url":"https://api.github.com/users/Pat28/orgs","repos_url":"https://api.github.com/users/Pat28/repos","events_url":"https://api.github.com/users/Pat28/events{/privacy}","received_events_url":"https://api.github.com/users/Pat28/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2014-10-29T14:36:33Z","updated_at":"2015-05-13T15:48:28Z","closed_at":null,"body":"Referring to https://github.com/opengeospatial/geopackage/issues/19.\r\nCan I request support for multiple geometry columns."},"comment":{"url":"https://api.github.com/repos/opengeospatial/geopackage/issues/comments/101721712","html_url":"https://github.com/opengeospatial/geopackage/issues/77#issuecomment-101721712","issue_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/77","id":101721712,"user":{"login":"trgn","id":1833023,"avatar_url":"https://avatars.githubusercontent.com/u/1833023?v=3","gravatar_id":"","url":"https://api.github.com/users/trgn","html_url":"https://github.com/trgn","followers_url":"https://api.github.com/users/trgn/followers","following_url":"https://api.github.com/users/trgn/following{/other_user}","gists_url":"https://api.github.com/users/trgn/gists{/gist_id}","starred_url":"https://api.github.com/users/trgn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trgn/subscriptions","organizations_url":"https://api.github.com/users/trgn/orgs","repos_url":"https://api.github.com/users/trgn/repos","events_url":"https://api.github.com/users/trgn/events{/privacy}","received_events_url":"https://api.github.com/users/trgn/received_events","type":"User","site_admin":false},"created_at":"2015-05-13T15:48:28Z","updated_at":"2015-05-13T15:48:28Z","body":"I'd be hesitant adding this, mainly because it would not be entirely clear what the meaning of this extra geometry would be. Is this additional geometry a sub-shape of the feature? Does it share the same properties as the main \"shape\"? Does it need to be visualized by standard viewers? What do we want to do if we want convert this table to a different format? How to index this: is the MBR now the union of all geometry columns?\r\n\r\nThis is a data-modeling exercise, that is perhaps be better addressed on a higher level (i.e. work with multiple tables, linked with a key. These can be joined on the application level, or with a VIEW).\r\n\r\nAlso, would a GeometryCollection not be sufficient to achieve a similar capability? The semantics of the constituents of this collections can then be resolved by the user of the collection?"}}