{"push_id":1197594841,"size":1,"distinct_size":1,"ref":"refs/heads/dev","head":"317f1e80d2c20b2d51f68d7d82f24e3f9df3b38a","before":"d888215136e8ab42186b930162e3af7439f6e751","commits":[{"sha":"317f1e80d2c20b2d51f68d7d82f24e3f9df3b38a","author":{"name":"Andrew Champion","email":"195a663ec25138e1df6e12f20c27e767096c7597@gmail.com"},"message":"Node: spatially query connectors and links\n\nPreviously, connectors were queried based on whether they were related\nto a treenode in the bounding box or were in a z-section of the bounding\nbox. This had several downsides:\n\n1. Joining a large set of treenodes into links when few would actually\n   exist\n2. Links where the connector and treenode were both outside the bounding\n   box were omitted even if the link intersected the bounding box\n3. Querying connectors by section axis does not generalize to arbitrary\n   planes\n\nInstead, query links and connectors spatially via a PostGIS edge table\nas is done for treenodes.\n\nThere are several possible implementations. The one in this commit\ncreates separate geometry tables for treenode_connectors and connectors.\n\nSee catmaid/CATMAID#1085.","distinct":true,"url":"https://api.github.com/repos/catmaid/CATMAID/commits/317f1e80d2c20b2d51f68d7d82f24e3f9df3b38a"}]}
{"actor":{"display_login":"aschampion"}}