) there is built in support for restricting the area in which a tree can be added. There is currently no UI for updating the bounds, so changing it will require running a Postgres/PostGIS query.
SELECT id, url_name, bounds_id
FROM treemap_instance
WHERE url_name = 'test';
id | url_name | bounds_id
----+----------+-----------
47 | test | 30
This bounds_id value is used to join the treemap_instance table to the treemap_instancebounds table, in which the boundary geometry is stored
SELECT i.id, i.url_name, ST_AsGeoJSON(geom) as bounds FROM treemap_instance i
JOIN treemap_instancebounds ib
WHERE url_name = 'test';
id | url_name | bounds
----+----------+----------------------------------------------------------------------------------
47 | test | {"type":"MultiPolygon","coordinates":[...web mercator (3857) coordinate list...]}
If you do not already have a new boundary polygon, you can draw one on
http://geojson.io and copy just the geometry object shown in the right sidebar
You can then remove the newline characters from that GeoJSON and use it to update the treemap_instancebounds row for your instance.
UPDATE treemap_instancebounds ib
SET geom = ST_Transform(ST_Multi(ST_SetSRID(ST_GeomFromGeoJSON('...GeoJSON...'), 4326)), 3857)
FROM treemap_instance i
WHERE i.bounds_id = ib.id AND i.url_name = ‘test';
UPDATE 1