You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node_keys= {"amenity"}
functionnode_function()
Layer("amenity")
end
and
node_keys= {"tourism"}
functionnode_function()
Layer("tourism")
end
and do mapt build, you will get two layers who each contain only amenity or tourism nodes.
If you do mapt build --single, you will get two layers who contain all nodes. This is because the merged driver file does not attempt to express your node_keys (or way_keys) to tilemaker, or filter on them before calling you.
So users need to write their functions defensively, e.g.:
node_keys= {"amenity"}
functionnode_function()
ifFind("amenity") =="" thenreturnendLayer("amenity")
end
This is OK for a v1, but it'd be nicer if:
the driver enforced node_keys/way_keys before delegating to your function
the driver (when possible) expressed node_keys/way_keys to tilemaker, to allow it to optimize reading
it's not generally possible to do this for all permutations, but if your keys were all positive (i.e. no ~building entries), we could just union them all together
The text was updated successfully, but these errors were encountered:
If you write two slices:
and
and do
mapt build
, you will get two layers who each contain only amenity or tourism nodes.If you do
mapt build --single
, you will get two layers who contain all nodes. This is because the merged driver file does not attempt to express your node_keys (or way_keys) to tilemaker, or filter on them before calling you.So users need to write their functions defensively, e.g.:
This is OK for a v1, but it'd be nicer if:
~building
entries), we could just union them all togetherThe text was updated successfully, but these errors were encountered: