{"action":"opened","issue":{"url":"https://api.github.com/repos/meganmilesoneill/usgs-earthquakes/issues/9","repository_url":"https://api.github.com/repos/meganmilesoneill/usgs-earthquakes","labels_url":"https://api.github.com/repos/meganmilesoneill/usgs-earthquakes/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/meganmilesoneill/usgs-earthquakes/issues/9/comments","events_url":"https://api.github.com/repos/meganmilesoneill/usgs-earthquakes/issues/9/events","html_url":"https://github.com/meganmilesoneill/usgs-earthquakes/issues/9","id":143335372,"number":9,"title":"Fix issue with GeoAlchemy ORM to support 3D Geometry/Point for earthquake events.","user":{"login":"meganmilesoneill","id":1872231,"avatar_url":"https://avatars.githubusercontent.com/u/1872231?v=3","gravatar_id":"","url":"https://api.github.com/users/meganmilesoneill","html_url":"https://github.com/meganmilesoneill","followers_url":"https://api.github.com/users/meganmilesoneill/followers","following_url":"https://api.github.com/users/meganmilesoneill/following{/other_user}","gists_url":"https://api.github.com/users/meganmilesoneill/gists{/gist_id}","starred_url":"https://api.github.com/users/meganmilesoneill/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/meganmilesoneill/subscriptions","organizations_url":"https://api.github.com/users/meganmilesoneill/orgs","repos_url":"https://api.github.com/users/meganmilesoneill/repos","events_url":"https://api.github.com/users/meganmilesoneill/events{/privacy}","received_events_url":"https://api.github.com/users/meganmilesoneill/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-24T19:15:27Z","updated_at":"2016-03-24T19:15:27Z","closed_at":null,"body":"By default, the GeoAlchemy ORM does not support 3D Points.  As a workaround, the database field is manually dropped and recreated, along with its index, during database creation.\r\n\r\nThere is probably a setting I'm missing in using the GeoAlchemy library to configure the Geometry field correctly.  Otherwise, this may require a fix on the GeoAlchemy side."}}