How should I define my fields in Atlas?

Fields in Atlas should cover a specific geographic area which generally shouldn't change unless there is an error or problem with the field definition. Billing and processing requests in Atlas are partially based on field definitions, so it's important to consider them carefully, as well-defined fields can help save on processing costs.

Fields should be defined in such a way that the defined area entirely covers only the specific field you are interested in capturing, even if you may only be flying over portions of that field at any given time. It's okay to cover one field with multiple drone flights on the same day, as Atlas can combine these flights to create a mosaic from all of the available data. Fields should not overlap other fields. 

Fields in the MicaSense Uploader

Field definitions will also appear on a map in the MicaSense Uploader tool, which can help reduce upload times by allowing the user to see and exclude images taken outside of their defined fields.

Fields in Atlas Flight

Fields defined in Atlas can be used to plan flights within Atlas Flight, so it's helpful to define your fields before heading out to fly.

Fields should not overlap

A field that overlaps another field may cause unwanted multiple processing requests to be generated, which may result in being charged for extra processing that was not desired.

Example of fields that do not overlap

good-fields.png 

Example of overlapping fields (do not create overlapping fields)

bad-fields.png

very-bad-fields.png

 

Have more questions? Submit a request