{"html_url": "https://github.com/simonw/datasette/issues/276#issuecomment-391050113", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/276", "id": 391050113, "node_id": "MDEyOklzc3VlQ29tbWVudDM5MTA1MDExMw==", "user": {"value": 45057, "label": "russss"}, "created_at": "2018-05-22T16:13:00Z", "updated_at": "2018-05-22T16:13:00Z", "author_association": "CONTRIBUTOR", "body": "Yup, I'll have a think about it. My current thoughts are for spatialite we'll need to hook into the following places:\r\n\r\n* Inspection, so we can detect which columns are geometry columns. (We also currently ignore spatialite tables during inspection, it may be worth moving that to the plugin as well.)\r\n* After data load, so we can convert WKB into the correct intermediate format for display. The alternative here is to alter the select SQL itself and get spatialite to do this conversion, but that strikes me as a bit more complex and possibly not as useful.\r\n* HTML rendering.\r\n* Querying?\r\n\r\nThe rendering and querying hooks could also potentially be used to move the units support into a plugin.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 324835838, "label": "Handle spatialite geometry columns better"}, "performed_via_github_app": null}