Scale Mapping is for labeling a large geographic area (up to 5km x 5km) over time with the ability to update the area based on new LIDAR or aerial imagery. This contrasts with the Lidar Topdown Tasking system which is better for labeling one small intersection-sized area at a time.
Terminology
- Storage Region - The geographic area for Scale to label over. Scale will create this for you. A Storage Region is associated with many Assets, Commits, and LabelJobs.
- Commit - A commit is a version of a Map (similar to Git commits). Each commit represents a snapshot of annotations and links at one time. A Storage Region holds a chain of commits, where the latest commit should be the latest high-quality version of the map.
- Asset - An asset is any input data for labeling. A Lidar Scene is one example of this.
- LabelJob - A LabelJob is how you tell Scale you are done uploading assets, and that Scale should start labeling.
- Audit - An Audit is a step in the labeling process where you can review the quality of Scale's work and provide comments or fixes along the way.
- MapProject - A MapProject is simply a group of Storage Regions. This concept is useful if you want to label an area whose large size requires Scale to break it up into smaller regions.
Typical Process
- A Map Project ID is given to you by Scale. You create a Storage Region representing the area you want labeled
- You upload Lidar Scenes or upload aerial imagery to the Storage Region
- You POST a LabelJob to tell Scale to start labeling using those assets
- Later on, Scale will finish labeling and a Map Commit will appear when you Retrieve your Storage Regions
- You can also update parts of the Storage Region by POSTing new Assets, then POSTing a new LabelJob.