Knowledge Base
Search…
0.6.0
Launched on 7/23/2020

Change Summary πŸš€β€‹

  • Data import improvements
    • Data imports will now check for duplicate field names before attempting to import
    • Ability to run multiple imports on the same project
  • Data import bug fixes
    • Long field names no longer break data imports
  • Smart Defaults changes
  • Quantification changes
  • Quantification bug fixes
  • Misc bug fixes

Data import improvements

Data imports will now check for duplicate field names before attempting to import

Import files with duplicate field names will now fail earlier on in the import process
Previously, data imports would not validate import files by checking for duplicate field names before beginning the import process. As such, the result could have inconsistently caused the importer to partially import the project which could in turn potentially cause it to misconfigure the project.

Ability to run multiple imports on the same project

Imports can now be run multiple times per project
In the past, running an import multiple times in the same project could have resulted in field boundaries being duplicated. Now, however, running a data import will merge with existing project data.
Successive imports will:
  • overwrite data in cells that previously had values written to them by imports
  • write data to cells that did not have values written to them in previous imports
Successive imports will not:
  • delete/clear cells that previously had values written to them by imports.

Data import bug fixes

Long field names no longer break data imports

Fields with more than 23 or more characters will be truncated to the 22nd character and have an underscore and two random characters appended.
For instance, a field named "This is a very long field name"will be truncated to be "This is a very long fi_aB"
We recently noticed a bug that was causing data imports to fail when they had fields defined within the import file that were more than 23 characters. After investigation, we found that the error was being caused by our usage of the Google Sheets API and an undocumented limitation of named ranges (a Google Sheets feature which we use in the spreadsheet).
Unfortunately, there is nothing we can do about this issue on the current intake sheet. As such, in order to prevent data imports from failing, we have begun truncating fields and appending random characters to the end of fields longer than 23 characters (to avoid duplicate field names-- which is another limitation of the Google Sheets API).

Misc bug fixes

  • Fixed a bug causing the fertilizer amounts to be imported incorrectly

Smart Defaults changes

  • Removed the fertilizer classification field in the UI when running Smart Default

Quantification changes

  • The COMET farm timeout error has been increased from 15 minutes to 90 minutes to reduce the likelihood of a false positive timeout

Quantification bug fixes

Misc bug fixes

  • Fixed a bug causing crops to be ignored when no harvests were defined
  • Fixed a bug where polygons in fields that are less than 1 acre resulted in comet erroring out when trying to find intersecting soil maps

Misc bug fixes

  • Fixed an issue causing SVGs to error out across our services
    ​
​
​
Last modified 1yr ago