sip packaging on focal and bullseyeĨ6 87 QgsBrowserGuiModel::flags(): take into number of providers for cached drop values (refs #53265)ĩ0 91 QgsBrowserGuiModel::flags(): cache value for faster browser redrawn (refs #53265)ġ06 107 fix deactivate mesh layer contoursġ10 111 debian packaging: don't move sip bindings only on focal and bullseye (ie. An idea could be to (ab)use theĤ7 description field of the GeoPackage system table to include aĤ8 conventional suffix like " (type Integer)" that would be automaticallyĤ9 set and stripped off by the OGR GPKG driver.ĥ0 51 It could also be nice that the QGIS GUI only proposes types that makeĥ2 sense for the underlying provider, but there's a lack of infrastructureĥ6 57 When testing custom coordinate transforms in dialog, always useĥ8 EPSG:4326 for the input coordinates IF the crs definitionĦ0 61 Only use geodetic crs associated with the actual crs definitionĦ3 64 This matches the dialog text better, which describe the inputħ0 71 Expand range of z index spin for annotationsħ4 75 Ensure quadrant segments are always at least 8 when doing offset curveħ6 77 Works around a GEOS bug artifacts when using GEOS 3.11.Ĩ2 83 debian packaging: fix. As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers.Īlternatively you can here view or download the uninterpreted source code file.Ī hint: This file contains one or more very long lines, so maybe it is better readable using the pure text view mode that shows the contents as wrapped lines within the browser window.Ģ 3 translation update for 3.28.8 from transifexĦ 7 Fix some build issues on 3.28 with newer GCCġ0 11 Fix GPKG project storage home path.ġ6 17 r.series: add missing tvalue optionĢ8 29 Don't create alpha bands for non-rotated, south up rastersģ8 39 OGR Field domain creation: properly convert QVariant to expect OGR data type (fixes #52318)Ĥ0 41 This fixes the main issues: crashes / data corruption.Ĥ2 43 Note however that currently the GeoPackage driver doesn't really supportĤ4 storing the data type of a field domain, so on reading, range domainsĤ5 are always read as of type Real (unless there is a layer fieldĤ6 associated with that domain).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |