{"comment":{"created_at":"2011-10-11T07:37:42Z","body":"[artem] Yes, good stuff. I applied PostgisSpecifyGeometryField patch. We need to update load_map to handle this.","updated_at":"2011-10-11T07:37:42Z","url":"https://api.github.com/repos/mapnik-org/mapnik/issues/comments/2356668","id":2356668,"user":{"avatar_url":"https://secure.gravatar.com/avatar/941f68386168a8a6b60f2529a7830af7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/artemp","id":59056,"login":"artemp"}},"action":"created","issue":{"number":137,"created_at":"2011-10-11T07:37:40Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"If a table has multiple geometry fields, mapnik will take the first one returned from querying `geometry_columns`.\r\n\r\nThe attached patch adds an optional `geometry_field` parameter to the postgis datasource constructor, so you can specify a specific column to use via (python example):\r\n {{{\r\nmylayer.datasource = mapnik.Datasource(\r\n    type = 'postgis', \r\n    table = 'test', \r\n    host = 'localhost', \r\n    dbname = 'test', \r\n    user = 'me', \r\n    password = 'me', \r\n    geometry_field = 'other_geom')\r\n}}}","comments":3,"title":"Ability to specify geometry field for postgis plugin","updated_at":"2011-10-11T07:37:42Z","url":"https://api.github.com/repos/mapnik-org/mapnik/issues/137","id":1871647,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/941f68386168a8a6b60f2529a7830af7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/artemp","id":59056,"login":"artemp"},"html_url":"https://github.com/mapnik-org/mapnik/issues/137","labels":[{"name":"PostGIS_Input_Driver","url":"https://api.github.com/repos/mapnik-org/mapnik/labels/PostGIS_Input_Driver","color":"FFFFFF"}],"state":"open"},"legacy":{"issue_id":1871647,"comment_id":2356668}}