Applicator View

Grower email should not be a required field. Some farmers do not have emails and while working with ag Cooperatives there are multiple contacts that could be emailed. If there was an option to add more than one contact/ email to the grower account that would be great.

When exporting KML files, they are missing critical information for as-applied maps. No nozzle on/off state No flow rate or application rate No ExtendedData or SchemaData blocks (the format KML uses for custom fields) No TimeStamp or TimeSpan per point (timestamps only exist in the track name string, not attached to individual coordinates) No speed, altitude variation, or any sensor values

Need to find a decent workflow to manage fields with a co-op. Currently they have their own login and will share fields to my account, but is there a way to share the flight data in a team assignment so that data flows more smoothly? Say have a team and share the fields to that team and once completed both parties can access flight data?

Won't allow me to pick a chemical needed for job scheduling. should be able to input a "custom chemical" if not found on the list or get a better searchable list from EPA. Job scheduling workflow could be better for batched jobs. Also, when sending maps created online to the controller there's no way to batch send to the controller you have to do that individually.