{"push_id":697381387,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"20f596401ec7015e6697c4958b641e0a020f932c","before":"e26db4c088bbb32a1edfad80795bedf3d6ffe6f0","commits":[{"sha":"255def89ccf39153c28933888286677e7715e340","author":{"email":"6da0130c5aeef94e5bbaabadbf8017270be25c64@azavea.com","name":"RickMohr"},"message":"Support polygonal map features\n\nA polygonal map feature has both\n* a row in the `stormwater_polygonalmapfeature` table (with a polygon), and\n* a row in the `treemap_mapfeature` table (with a point)\n\nPolygonal map features are rendered separately from point map features becuase a tile request can only show one geometry column. They are distinguished by passing `stormwater_polygonalmapfeature` as the `table` segment of the tile URL.\n\nWe still use `treemap_mapfeature` as the primary table of the SQL query, joining to `stormwater_polygonalmapfeature` to get its geometry. For example:\n\n```sql\nSELECT stormwater_polygonalmapfeature.polygon AS the_geom_webmercator, feature_type\n    FROM treemap_mapfeature\n    INNER JOIN stormwater_polygonalmapfeature ON stormwater_polygonalmapfeature.mapfeature_ptr_id =\n    treemap_mapfeature.id\n    WHERE treemap_mapfeature.instance_id = 39\n```\n\nCurrently a polygonal map feature is rendered as both a polygon and a point (i.e. in both `polygonalmapfeature` and `mapfeature` tiles). That will be fixed in a future PR.\n\nConnects #60","distinct":true,"url":"https://api.github.com/repos/OpenTreeMap/otm-tiler/commits/255def89ccf39153c28933888286677e7715e340"},{"sha":"20f596401ec7015e6697c4958b641e0a020f932c","author":{"email":"6da0130c5aeef94e5bbaabadbf8017270be25c64@azavea.com","name":"Rick Mohr"},"message":"Merge pull request #63 from RickMohr/polygonal-map-features\n\nSupport polygonal map features","distinct":true,"url":"https://api.github.com/repos/OpenTreeMap/otm-tiler/commits/20f596401ec7015e6697c4958b641e0a020f932c"}]}