Releases: hotosm/osm-fieldwork
Releases · hotosm/osm-fieldwork
v0.17.0
v0.16.12
What's Changed
- Update mandatory fields XLSForm to better handle new_feature field injection.
Full Changelog: 0.16.11...0.16.12
v0.16.11
What's Changed
- Sanitize column names to follow defined standards by @Sujanadh in #313
- Add row to calculate coordinates of additional entity by @Sujanadh in #312
- Update labels and entities name in test cases by @Sujanadh in #317
- Photo question outside the verification section as a standalone question by @Sujanadh in #319
Full Changelog: 0.16.10...0.16.11
v0.16.10
What's Changed
- Updates the minimum pin for
python-calamine
ensuring that all required dependencies are bundled. - This should improve compatibility with Python 3.12 and dependency lockers: see dimastbk/python-calamine#93
Full Changelog: 0.16.9...0.16.10
v0.16.9
What's Changed
Full Changelog: 0.16.8...0.16.9
0.16.8
What's Changed
Note
It would seem this is a reversion of 0.16.7, but it is not.
Instead the logic was updated to remove duplicates based on the list_name
and name
column pair.
This way duplicates can still exist, as long as they are in a different choices list (list_name).
Full Changelog: 0.16.7...0.16.8
0.16.7
- Do not remove duplicate values from 'choices' XLSForm sheet, as these are actually valid.
- There may be duplicate 'name' column entries across 'list_name', for example multiple yes/no answers.
Full Changelog: 0.16.6...0.16.7
v0.16.6
What's Changed
- Removed 'feature does not exist' from the digitisation_correct options, as we moved this to a separate question at the start of the XLSForm.
Full Changelog: 0.16.5...0.16.6
v0.16.5rc0
BREAKING CHANGE (but small and won't affect anyone)
update_xlsform.append_mandatory_fields
now returns a tuple instead of only the XLSForm (xformid, xlsform_bytesio).- Small tweaks to questions in mandatory fields XLSForm.
Full Changelog: 0.16.3...0.16.5rc0
v0.16.5
- Simplify logic for digitisation and mandatory fields XLSForms based on field feedback.
- Remove the task_id and task_filter fields to simplify logic.
- They make it slightly easier to select a geometry by filtering down the available options, at the expense of complicating many things.
- Ideally the user just selects a geom via intent and doesn't even need to open the map anyway.
Full Changelog: 0.16.3...0.16.5