Project metadata
Name, description, creation time and modification time remain in the project archive.
Practice
Project Management
Organize objects, layers, tracks and imports in the project.
Workflow
Typical Flow
Use these steps to complete the workflow on the map.
- Step 1Review project structure
- Step 2Name and filter objects
- Step 3Enable imports and layers as needed
- Step 4Back up the project regularly as .asmaps
Traceability
Preserve project metadata and import origin
Project structure and import evidence help explain large data sets later and prevent unintended duplicate imports.
Collections and import groups
Both can be renamed and described later without importing their objects again.
Import evidence
Sanitized file name, SHA-256, time, destination and object count record the origin of a project import.
Detect duplicate imports
The same file is not silently imported again into the same project.
Detailed guides
Projects, collections and restore targets
A project stores objects, collections, search grids, ViewRanges and app metadata, while linked external files may remain separate.
Free and Pro
Free keeps one current project and replaces it on project import after a warning. Pro provides a project library for creating, renaming, switching and moving selected objects.
Project or backup
.asmaps preserves an editable project; .asmaps.bak can include more projects, resources and settings. Choose new, replace, merge or selective restore deliberately and keep the encryption password.