Skip to content

2024.3.2

Latest
Compare
Choose a tag to compare
@spwoodcock spwoodcock released this 30 Jul 23:16
· 64 commits to development since this release

FMTM 2024.3.2 Patch Release

A minor release stabilising FMTM prior to webinar and wider public communication.

🛠️ Improvements

  • Faster project creation: we significantly improved the project creation workflow to optimise for speed. Creation should complete in under 10 seconds for most projects of any size.

  • Layer opacity: reduce the opacity of the task overlay with satellite base: The high opacity of task colour hindered field mappers to view the base layers clearly. Reducing the opacity has greatly improved the user's experience.
    image

  • Form question ordering: we moved the digitisation related questions to the end of all forms, based on field-user feedback. Typically a mapper will interact with the owner / ask questions, prior to assessing the building footprint and trespassing on land.

  • Project generation failure: if project generation fails, the remaining steps are now halted and the steps so far are reverted. This allows the user to correct their input and try again.

  • Form updates: form category and uploaded form should be pre populated while editing project form: While editing the form, the form category was not being populated causing confusion for users on form category. However, the form category can’t be edited because it has some serious impact on task splitting and data extraction activities.
    image

  • ODK token refresh: submitting data from ODK Collect uses a special authentication token. This token can now be refreshed if needed, if the token is lost of suspected to be compromised.

🐛 Bugs Fixed

  • 'Map Feature in ODK' button is enabled if the task area is locked: For some field mappers who work on groups may require mapping single building within locked tasks too. FMTM now offers users to map a few features within locked tasks to be mapped from ODK.
  • Error message during submission download when there is no submission on that project: The vague error message saying “something went wrong” or “The data can’t be downloaded” used to be shown to the user when there is no submission within that project. This is now fixed by providing a clear error message.
  • Parsing of hashtags was sometimes incorrect on varied input. It should now be consistent.
  • Improved GeoJSON parsing, allowing for more flexible input without failures: MultiPolygon, Feature, FeatureCollection, etc.
  • Fixed MBTile / PMTile generation when using a custom TMS URL - this was not always working previously.
  • S3-based objects related to a project were not deleted on project deletion - they are now.
Technical Summary

What's Changed

Full Changelog: 2024.3.0...2024.3.2