Once a project is open, the next job is to assemble the layer stack in a way that matches the work. Tamaat lets users add layers, remove them from the project, and organize them into layer groups so the project remains understandable as it grows.
Add layers with intent
Bring in the layers that define the task in front of you:
- point or address layers for asset or service-location work
- line layers for roads, routes, or networks
- polygon layers for service areas, FSAs, parcels, or building footprints
The goal is not to load everything at once. The goal is to add the layers that make the project operational.
Organize the project layers
As the layer count grows, group layers by function. For example:
- operational layers
- reference layers
- boundary layers
- edit targets
This makes the project easier to work with for both the original analyst and anyone else who opens it later.
Use the project layer list actively
Inside the project layers panel, users can:
- reorder layers
- move layers into or out of layer groups
- turn visibility on and off
- open layer actions for configuration or data access
Recommended practice
If a project is likely to be shared, create the groups early. Layer organization is not just visual cleanup. It becomes part of the operational handoff.