Taivaskero brings not only new gadgets like the print of atlas features, the Finnish address search and an improved relation editor widget. There are as well lots of other improvements like a smarter progressive rendering and some revamps in the user interface.
Search for Finnish addresses
You can find addresses in Finnland using the search bar with Pelias geocoder in the backend.
Search results are remembered when reopening the search bar after you clicked on one result, which helps navigate through the returned locations.
The Finnish geocoder will auto enable its non-prefix use in the search bar whenever the user switches the position/location/GPS button on and overlaps with Finland's bounding box. You can manually turn it on/off in QField Settings > General > Customize Search bar
The position check is only done when the user toggles the position/location/GPS button on, this way, we insure that we're using such data when the user has explicitly expressed he/she is OK fetching that data to begin with.
Print Atlas Features to PDF
Exporting prints to PDF has been possible before, but now you are able to export your full atlas or only consider the features of your choice. This means, it enables a print button attached to focused and selected features on vector layers found to be atlas coverage layers in any of the print layouts for the currently loaded project.
 |  |  |
And for printing only a single feature, this print action is available in in the feature form viewing the attributes.
Geometry digitizing when adding a child feature
When adding a feature via the relation editor widget, if the referenced relation layer has a geometry, you will jump into digitizing mode to add your point/line/polygon.
Opening of individual vector/raster datasets
You can open individual vector / raster datasets without the need for a QGIS project file. Opening such a file will automatically create a temporary project to display the dataset. If the dataset supports writing, you can use the digitizing tools to add and save features into the dataset.
Off the box, when opening individual datasets, QField will automatically add a openstreetmap layer as basemap on top of which the dataset is displayed. But you can add a custom basemap.qgs (or basemap.qgz) QGIS project file in their device's /QField/ directory to customize the layer(s) that will be used as basemap.
For datasets containing more than one layer (like Geopackage), all layers will be added and their stacking sorted. The logic is: points on top, then lines, then polygons, then rasters, then the basemap.
GeoPDFs have specific handling whereas by default, any vector feature layers from the GeoPDF are hidden to allow for the raster map to display. While the features are hidden by default, they can still be identified via the search bar.
And you can make use of dataset's default styles if present. This means a datasets' default style - embedded into a Geopackage database or served through a side .qml file - with symbology and also customized feature form will be loaded.
Smarter progressive rendering
Intermediate rendering by using a transformed cache image as temporary placeholder during progressive rendering and big improvements on the QGIS side. So progressive rendering is on by default. This is a great service to users who rely on WFS layers.
Restore last viewed map extent
QField will restore the last viewed map extent when re-loading a project that was previously opened by QField.
The implementation is cloud-stored project friendly as it doesn't save the project itself but rather store the extent in the user settings. This means a large cloud-stored project can have many users focused on their own specific extents, remember those without interfering with others.
Support for colors in attribute forms
Background colors on attribute form containers are applied in a mobile-friendly appearance.
Other nice things and fixes
- NMEA UI/UX improvements
- UI/UX of the fill ring tool improvements
- Preferance of lowercase characters when entering username on layer login
- No UI hang/freeze when opening the layer properties panel due to slow feature count
- No lock of screenOrientation in QFieldActivity - means you can change the orientation during runtime
- Use of C locale to validate doubles
- Fixed remembered values
- Fixed not showing the display string in value relation
- Fixed weird behavior on tab change