sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-03-12 00:02:25 -04:00
Code Issues Packages Projects Releases Wiki Activity
QGIS/tests/testdata/qgis_server/test_project_wms_grouped_layers.qgs

1937 lines
82 KiB
Plaintext
Raw Normal View History

[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<!DOCTYPE qgis PUBLIC 'http://mrcc.com/qgis.dtd' 'SYSTEM'>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<qgis projectname="QGIS Server - Grouped Layer" version="3.5.0-Master">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<homePath path=""/>
<title>QGIS Server - Grouped Layer</title>
<autotransaction active="0"/>
<evaluateDefaultValues active="0"/>
<trust active="0"/>
<projectCrs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</projectCrs>
<layer-tree-group>
<customproperties/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-group expanded="1" checked="Qt::Checked" name="city and district boundaries">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-layer providerKey="ogr" expanded="1" checked="Qt::Checked" id="cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b" name="cdb_lines" source="./test_project_wms_grouped_layers.gpkg|layername=cdb_lines">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
</layer-tree-layer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-layer providerKey="ogr" expanded="1" checked="Qt::Checked" id="cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf" name="cdb_labels" source="./test_project_wms_grouped_layers.gpkg|layername=cdb_labels">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
</layer-tree-layer>
</layer-tree-group>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-group expanded="1" checked="Qt::Checked" name="areas and symbols">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-layer providerKey="ogr" expanded="1" checked="Qt::Checked" id="as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76" name="as_symbols" source="./test_project_wms_grouped_layers.gpkg|layername=as_symbols">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
</layer-tree-layer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-layer providerKey="ogr" expanded="1" checked="Qt::Checked" id="as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467" name="as_areas" source="./test_project_wms_grouped_layers.gpkg|layername=as_areas">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
</layer-tree-layer>
</layer-tree-group>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-tree-layer providerKey="gdal" expanded="1" checked="Qt::Checked" id="osm_85c8eb94_b6fa_437b_b91a_7816ef2e2243" name="osm" source="GPKG:/home/ale/dev/QGIS/tests/testdata/qgis_server/test_project_wms_grouped_layers.gpkg:osm">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<customproperties/>
</layer-tree-layer>
<custom-order enabled="0">
<item>osm_85c8eb94_b6fa_437b_b91a_7816ef2e2243</item>
<item>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</item>
<item>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</item>
<item>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</item>
<item>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</item>
</custom-order>
</layer-tree-group>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<snapping-settings unit="1" intersection-snapping="0" type="1" tolerance="12" enabled="0" mode="2">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<individual-layer-settings>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<layer-setting id="as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76" type="1" tolerance="12" units="1" enabled="0"/>
<layer-setting id="as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467" type="1" tolerance="12" units="1" enabled="0"/>
<layer-setting id="cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b" type="1" tolerance="12" units="1" enabled="0"/>
<layer-setting id="cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf" type="1" tolerance="12" units="1" enabled="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</individual-layer-settings>
</snapping-settings>
<relations/>
<mapcanvas name="theMapCanvas" annotationsVisible="1">
<units>meters</units>
<extent>
<xmin>611130.7508374999742955</xmin>
<ymin>5808188.16393684130162001</ymin>
<xmax>623514.4366625000257045</xmax>
<ymax>5814318.83606315869837999</ymax>
</extent>
<rotation>0</rotation>
<destinationsrs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</destinationsrs>
<rendermaptile>0</rendermaptile>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
<expressionContextScope/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</mapcanvas>
<projectModels/>
<legend updateDrawingOrder="true">
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<legendgroup checked="Qt::Checked" open="true" name="city and district boundaries">
<legendlayer checked="Qt::Checked" open="true" name="cdb_lines" drawingOrder="-1" showFeatureCount="0">
<filegroup open="true" hidden="false">
<legendlayerfile layerid="cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b" visible="1" isInOverview="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</filegroup>
</legendlayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<legendlayer checked="Qt::Checked" open="true" name="cdb_labels" drawingOrder="-1" showFeatureCount="0">
<filegroup open="true" hidden="false">
<legendlayerfile layerid="cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf" visible="1" isInOverview="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</filegroup>
</legendlayer>
</legendgroup>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<legendgroup checked="Qt::Checked" open="true" name="areas and symbols">
<legendlayer checked="Qt::Checked" open="true" name="as_symbols" drawingOrder="-1" showFeatureCount="0">
<filegroup open="true" hidden="false">
<legendlayerfile layerid="as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76" visible="1" isInOverview="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</filegroup>
</legendlayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<legendlayer checked="Qt::Checked" open="true" name="as_areas" drawingOrder="-1" showFeatureCount="0">
<filegroup open="true" hidden="false">
<legendlayerfile layerid="as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467" visible="1" isInOverview="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</filegroup>
</legendlayer>
</legendgroup>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<legendlayer checked="Qt::Checked" open="true" name="osm" drawingOrder="-1" showFeatureCount="0">
<filegroup open="true" hidden="false">
<legendlayerfile layerid="osm_85c8eb94_b6fa_437b_b91a_7816ef2e2243" visible="1" isInOverview="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</filegroup>
</legendlayer>
</legend>
<mapViewDocks/>
<projectlayers>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<maplayer geometry="Polygon" simplifyDrawingTol="1" simplifyAlgorithm="0" simplifyMaxScale="1" styleCategories="AllStyleCategories" minScale="1e+08" maxScale="0" simplifyLocal="1" type="vector" labelsEnabled="0" readOnly="0" refreshOnNotifyEnabled="0" simplifyDrawingHints="1" autoRefreshTime="0" refreshOnNotifyMessage="" hasScaleBasedVisibilityFlag="0" autoRefreshEnabled="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<extent>
<xmin>614440.5625</xmin>
<ymin>5808607</ymin>
<xmax>618892</xmax>
<ymax>5812990</ymax>
</extent>
<id>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</id>
<datasource>./test_project_wms_grouped_layers.gpkg|layername=as_areas</datasource>
<keywordList>
<value></value>
</keywordList>
<layername>as_areas</layername>
<srs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</srs>
<resourceMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title></title>
<abstract></abstract>
<links/>
<fees></fees>
<encoding></encoding>
<crs>
<spatialrefsys>
<proj4></proj4>
<srsid>0</srsid>
<srid>0</srid>
<authid></authid>
<description></description>
<projectionacronym></projectionacronym>
<ellipsoidacronym></ellipsoidacronym>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<geographicflag>true</geographicflag>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</spatialrefsys>
</crs>
<extent/>
</resourceMetadata>
<provider encoding="UTF-8">ogr</provider>
<vectorjoins/>
<layerDependencies/>
<dataDependencies/>
<legend type="default-vector"/>
<expressionfields/>
<map-layer-style-manager current="default">
<map-layer-style name="default"/>
</map-layer-style-manager>
<auxiliaryLayer/>
<flags>
<Identifiable>1</Identifiable>
<Removable>1</Removable>
<Searchable>1</Searchable>
</flags>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<renderer-v2 forceraster="0" type="singleSymbol" symbollevels="0" enableorderby="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<symbols>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="fill" clip_to_extent="1" force_rhr="0" name="0">
<layer class="SimpleFill" locked="0" pass="0" enabled="1">
<prop k="border_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="color" v="183,72,75,255"/>
<prop k="joinstyle" v="bevel"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="35,35,35,255"/>
<prop k="outline_style" v="solid"/>
<prop k="outline_width" v="0.26"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="style" v="solid"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
</symbols>
<rotation/>
<sizescale/>
</renderer-v2>
<customproperties/>
<blendMode>0</blendMode>
<featureBlendMode>0</featureBlendMode>
<layerOpacity>1</layerOpacity>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<geometryOptions geometryPrecision="0" removeDuplicateNodes="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<activeChecks/>
<checkConfiguration/>
</geometryOptions>
<fieldConfiguration>
<field name="fid">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="gid">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="datum">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="bearbeiter">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="veranstaltung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="beschriftung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="name">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="flaechentyp">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="farbe">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="schraff_width">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="schraff_width_prt">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="schraff_size">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="schraff_size_prt">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="schraff_winkel">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="umrissfarbe">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="umrisstyp">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="umrissstaerke">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="umrissstaerke_prt">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="umfang">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="flaeche">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="bemerkung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="last_change">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
</fieldConfiguration>
<aliases>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<alias index="0" field="fid" name=""/>
<alias index="1" field="gid" name=""/>
<alias index="2" field="datum" name=""/>
<alias index="3" field="bearbeiter" name=""/>
<alias index="4" field="veranstaltung" name=""/>
<alias index="5" field="beschriftung" name=""/>
<alias index="6" field="name" name=""/>
<alias index="7" field="flaechentyp" name=""/>
<alias index="8" field="farbe" name=""/>
<alias index="9" field="schraff_width" name=""/>
<alias index="10" field="schraff_width_prt" name=""/>
<alias index="11" field="schraff_size" name=""/>
<alias index="12" field="schraff_size_prt" name=""/>
<alias index="13" field="schraff_winkel" name=""/>
<alias index="14" field="umrissfarbe" name=""/>
<alias index="15" field="umrisstyp" name=""/>
<alias index="16" field="umrissstaerke" name=""/>
<alias index="17" field="umrissstaerke_prt" name=""/>
<alias index="18" field="umfang" name=""/>
<alias index="19" field="flaeche" name=""/>
<alias index="20" field="bemerkung" name=""/>
<alias index="21" field="last_change" name=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</aliases>
<excludeAttributesWMS/>
<excludeAttributesWFS/>
<defaults>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<default applyOnUpdate="0" expression="" field="fid"/>
<default applyOnUpdate="0" expression="" field="gid"/>
<default applyOnUpdate="0" expression="" field="datum"/>
<default applyOnUpdate="0" expression="" field="bearbeiter"/>
<default applyOnUpdate="0" expression="" field="veranstaltung"/>
<default applyOnUpdate="0" expression="" field="beschriftung"/>
<default applyOnUpdate="0" expression="" field="name"/>
<default applyOnUpdate="0" expression="" field="flaechentyp"/>
<default applyOnUpdate="0" expression="" field="farbe"/>
<default applyOnUpdate="0" expression="" field="schraff_width"/>
<default applyOnUpdate="0" expression="" field="schraff_width_prt"/>
<default applyOnUpdate="0" expression="" field="schraff_size"/>
<default applyOnUpdate="0" expression="" field="schraff_size_prt"/>
<default applyOnUpdate="0" expression="" field="schraff_winkel"/>
<default applyOnUpdate="0" expression="" field="umrissfarbe"/>
<default applyOnUpdate="0" expression="" field="umrisstyp"/>
<default applyOnUpdate="0" expression="" field="umrissstaerke"/>
<default applyOnUpdate="0" expression="" field="umrissstaerke_prt"/>
<default applyOnUpdate="0" expression="" field="umfang"/>
<default applyOnUpdate="0" expression="" field="flaeche"/>
<default applyOnUpdate="0" expression="" field="bemerkung"/>
<default applyOnUpdate="0" expression="" field="last_change"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</defaults>
<constraints>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp_strength="0" unique_strength="1" field="fid" notnull_strength="1" constraints="3"/>
<constraint exp_strength="0" unique_strength="0" field="gid" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="datum" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="bearbeiter" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="veranstaltung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="beschriftung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="name" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="flaechentyp" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="farbe" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="schraff_width" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="schraff_width_prt" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="schraff_size" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="schraff_size_prt" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="schraff_winkel" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="umrissfarbe" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="umrisstyp" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="umrissstaerke" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="umrissstaerke_prt" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="umfang" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="flaeche" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="bemerkung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="last_change" notnull_strength="0" constraints="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraints>
<constraintExpressions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp="" field="fid" desc=""/>
<constraint exp="" field="gid" desc=""/>
<constraint exp="" field="datum" desc=""/>
<constraint exp="" field="bearbeiter" desc=""/>
<constraint exp="" field="veranstaltung" desc=""/>
<constraint exp="" field="beschriftung" desc=""/>
<constraint exp="" field="name" desc=""/>
<constraint exp="" field="flaechentyp" desc=""/>
<constraint exp="" field="farbe" desc=""/>
<constraint exp="" field="schraff_width" desc=""/>
<constraint exp="" field="schraff_width_prt" desc=""/>
<constraint exp="" field="schraff_size" desc=""/>
<constraint exp="" field="schraff_size_prt" desc=""/>
<constraint exp="" field="schraff_winkel" desc=""/>
<constraint exp="" field="umrissfarbe" desc=""/>
<constraint exp="" field="umrisstyp" desc=""/>
<constraint exp="" field="umrissstaerke" desc=""/>
<constraint exp="" field="umrissstaerke_prt" desc=""/>
<constraint exp="" field="umfang" desc=""/>
<constraint exp="" field="flaeche" desc=""/>
<constraint exp="" field="bemerkung" desc=""/>
<constraint exp="" field="last_change" desc=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraintExpressions>
<expressionfields/>
<attributeactions>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<defaultAction key="Canvas" value="{00000000-0000-0000-0000-000000000000}"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</attributeactions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<attributetableconfig sortExpression="" actionWidgetStyle="dropDown" sortOrder="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<columns/>
</attributetableconfig>
<conditionalstyles>
<rowstyles/>
<fieldstyles/>
</conditionalstyles>
<editform tolerant="1"></editform>
<editforminit/>
<editforminitcodesource>0</editforminitcodesource>
<editforminitfilepath></editforminitfilepath>
<editforminitcode><![CDATA[]]></editforminitcode>
<featformsuppress>0</featformsuppress>
<editorlayout>generatedlayout</editorlayout>
<editable/>
<labelOnTop/>
<widgets/>
<previewExpression></previewExpression>
<mapTip></mapTip>
</maplayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<maplayer geometry="Point" simplifyDrawingTol="1" simplifyAlgorithm="0" simplifyMaxScale="1" styleCategories="AllStyleCategories" minScale="1e+08" maxScale="0" simplifyLocal="1" type="vector" labelsEnabled="0" readOnly="0" refreshOnNotifyEnabled="0" simplifyDrawingHints="1" autoRefreshTime="0" refreshOnNotifyMessage="" hasScaleBasedVisibilityFlag="0" autoRefreshEnabled="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<extent>
<xmin>613845.1875</xmin>
<ymin>5810420</ymin>
<xmax>620800</xmax>
<ymax>5813900</ymax>
</extent>
<id>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</id>
<datasource>./test_project_wms_grouped_layers.gpkg|layername=as_symbols</datasource>
<keywordList>
<value></value>
</keywordList>
<layername>as_symbols</layername>
<srs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</srs>
<resourceMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title></title>
<abstract></abstract>
<links/>
<fees></fees>
<encoding></encoding>
<crs>
<spatialrefsys>
<proj4></proj4>
<srsid>0</srsid>
<srid>0</srid>
<authid></authid>
<description></description>
<projectionacronym></projectionacronym>
<ellipsoidacronym></ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</crs>
<extent/>
</resourceMetadata>
<provider encoding="UTF-8">ogr</provider>
<vectorjoins/>
<layerDependencies/>
<dataDependencies/>
<legend type="default-vector"/>
<expressionfields/>
<map-layer-style-manager current="default">
<map-layer-style name="default"/>
</map-layer-style-manager>
<auxiliaryLayer/>
<flags>
<Identifiable>1</Identifiable>
<Removable>1</Removable>
<Searchable>1</Searchable>
</flags>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<renderer-v2 forceraster="0" type="singleSymbol" symbollevels="0" enableorderby="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<symbols>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="marker" clip_to_extent="1" force_rhr="0" name="0">
<layer class="SimpleMarker" locked="0" pass="0" enabled="1">
<prop k="angle" v="0"/>
<prop k="color" v="0,192,0,255"/>
<prop k="horizontal_anchor_point" v="1"/>
<prop k="joinstyle" v="bevel"/>
<prop k="name" v="star"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="0,0,0,255"/>
<prop k="outline_style" v="solid"/>
<prop k="outline_width" v="0"/>
<prop k="outline_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="scale_method" v="area"/>
<prop k="size" v="4"/>
<prop k="size_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="size_unit" v="MM"/>
<prop k="vertical_anchor_point" v="1"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
</symbols>
<rotation/>
<sizescale/>
</renderer-v2>
<customproperties/>
<blendMode>0</blendMode>
<featureBlendMode>0</featureBlendMode>
<layerOpacity>1</layerOpacity>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<geometryOptions geometryPrecision="0" removeDuplicateNodes="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<activeChecks/>
<checkConfiguration/>
</geometryOptions>
<fieldConfiguration>
<field name="fid">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="gid">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="datum">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="bearbeiter">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="veranstaltung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="beschriftung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="name">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="form">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="groesse">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="groesse_red">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="winkel">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="farbe">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="bemerkung">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="last_change">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
</fieldConfiguration>
<aliases>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<alias index="0" field="fid" name=""/>
<alias index="1" field="gid" name=""/>
<alias index="2" field="datum" name=""/>
<alias index="3" field="bearbeiter" name=""/>
<alias index="4" field="veranstaltung" name=""/>
<alias index="5" field="beschriftung" name=""/>
<alias index="6" field="name" name=""/>
<alias index="7" field="form" name=""/>
<alias index="8" field="groesse" name=""/>
<alias index="9" field="groesse_red" name=""/>
<alias index="10" field="winkel" name=""/>
<alias index="11" field="farbe" name=""/>
<alias index="12" field="bemerkung" name=""/>
<alias index="13" field="last_change" name=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</aliases>
<excludeAttributesWMS/>
<excludeAttributesWFS/>
<defaults>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<default applyOnUpdate="0" expression="" field="fid"/>
<default applyOnUpdate="0" expression="" field="gid"/>
<default applyOnUpdate="0" expression="" field="datum"/>
<default applyOnUpdate="0" expression="" field="bearbeiter"/>
<default applyOnUpdate="0" expression="" field="veranstaltung"/>
<default applyOnUpdate="0" expression="" field="beschriftung"/>
<default applyOnUpdate="0" expression="" field="name"/>
<default applyOnUpdate="0" expression="" field="form"/>
<default applyOnUpdate="0" expression="" field="groesse"/>
<default applyOnUpdate="0" expression="" field="groesse_red"/>
<default applyOnUpdate="0" expression="" field="winkel"/>
<default applyOnUpdate="0" expression="" field="farbe"/>
<default applyOnUpdate="0" expression="" field="bemerkung"/>
<default applyOnUpdate="0" expression="" field="last_change"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</defaults>
<constraints>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp_strength="0" unique_strength="1" field="fid" notnull_strength="1" constraints="3"/>
<constraint exp_strength="0" unique_strength="0" field="gid" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="datum" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="bearbeiter" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="veranstaltung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="beschriftung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="name" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="form" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="groesse" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="groesse_red" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="winkel" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="farbe" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="bemerkung" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="last_change" notnull_strength="0" constraints="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraints>
<constraintExpressions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp="" field="fid" desc=""/>
<constraint exp="" field="gid" desc=""/>
<constraint exp="" field="datum" desc=""/>
<constraint exp="" field="bearbeiter" desc=""/>
<constraint exp="" field="veranstaltung" desc=""/>
<constraint exp="" field="beschriftung" desc=""/>
<constraint exp="" field="name" desc=""/>
<constraint exp="" field="form" desc=""/>
<constraint exp="" field="groesse" desc=""/>
<constraint exp="" field="groesse_red" desc=""/>
<constraint exp="" field="winkel" desc=""/>
<constraint exp="" field="farbe" desc=""/>
<constraint exp="" field="bemerkung" desc=""/>
<constraint exp="" field="last_change" desc=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraintExpressions>
<expressionfields/>
<attributeactions>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<defaultAction key="Canvas" value="{00000000-0000-0000-0000-000000000000}"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</attributeactions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<attributetableconfig sortExpression="" actionWidgetStyle="dropDown" sortOrder="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<columns/>
</attributetableconfig>
<conditionalstyles>
<rowstyles/>
<fieldstyles/>
</conditionalstyles>
<editform tolerant="1"></editform>
<editforminit/>
<editforminitcodesource>0</editforminitcodesource>
<editforminitfilepath></editforminitfilepath>
<editforminitcode><![CDATA[]]></editforminitcode>
<featformsuppress>0</featformsuppress>
<editorlayout>generatedlayout</editorlayout>
<editable/>
<labelOnTop/>
<widgets/>
<previewExpression></previewExpression>
<mapTip></mapTip>
</maplayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<maplayer geometry="Point" simplifyDrawingTol="1" simplifyAlgorithm="0" simplifyMaxScale="1" styleCategories="AllStyleCategories" minScale="1e+08" maxScale="0" simplifyLocal="1" type="vector" labelsEnabled="1" readOnly="0" refreshOnNotifyEnabled="0" simplifyDrawingHints="0" autoRefreshTime="0" refreshOnNotifyMessage="" hasScaleBasedVisibilityFlag="0" autoRefreshEnabled="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<extent>
<xmin>613794.8125</xmin>
<ymin>5800447</ymin>
<xmax>626894.25</xmax>
<ymax>5815374.5</ymax>
</extent>
<id>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</id>
<datasource>./test_project_wms_grouped_layers.gpkg|layername=cdb_labels</datasource>
<keywordList>
<value></value>
</keywordList>
<layername>cdb_labels</layername>
<srs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</srs>
<resourceMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title></title>
<abstract></abstract>
<links/>
<fees></fees>
<encoding></encoding>
<crs>
<spatialrefsys>
<proj4></proj4>
<srsid>0</srsid>
<srid>0</srid>
<authid></authid>
<description></description>
<projectionacronym></projectionacronym>
<ellipsoidacronym></ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</crs>
<extent/>
</resourceMetadata>
<provider encoding="UTF-8">ogr</provider>
<vectorjoins/>
<layerDependencies/>
<dataDependencies/>
<legend type="default-vector"/>
<expressionfields/>
<map-layer-style-manager current="default">
<map-layer-style name="default"/>
</map-layer-style-manager>
<auxiliaryLayer/>
<flags>
<Identifiable>1</Identifiable>
<Removable>1</Removable>
<Searchable>1</Searchable>
</flags>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<renderer-v2 forceraster="0" type="singleSymbol" symbollevels="0" enableorderby="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<symbols>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="marker" clip_to_extent="1" force_rhr="0" name="0">
<layer class="SimpleMarker" locked="0" pass="0" enabled="1">
<prop k="angle" v="0"/>
<prop k="color" v="225,89,137,255"/>
<prop k="horizontal_anchor_point" v="1"/>
<prop k="joinstyle" v="bevel"/>
<prop k="name" v="circle"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="35,35,35,255"/>
<prop k="outline_style" v="no"/>
<prop k="outline_width" v="0"/>
<prop k="outline_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="scale_method" v="diameter"/>
<prop k="size" v="0"/>
<prop k="size_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="size_unit" v="MM"/>
<prop k="vertical_anchor_point" v="1"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
</symbols>
<rotation/>
<sizescale/>
</renderer-v2>
<labeling type="simple">
<settings>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<text-style fieldName="NAME" useSubstitutions="0" fontSize="14" textColor="0,0,149,255" fontUnderline="0" textOpacity="1" fontFamily="Sans Serif" fontLetterSpacing="0" blendMode="0" fontWeight="75" fontStrikeout="0" fontWordSpacing="0" fontCapitals="0" isExpression="0" fontSizeUnit="Point" fontSizeMapUnitScale="3x:0,0,0,0,0,0" namedStyle="Bold" previewBkgrdColor="#ffffff" fontItalic="0" multilineHeight="1">
<text-buffer bufferJoinStyle="64" bufferDraw="1" bufferColor="255,255,255,255" bufferNoFill="0" bufferSizeMapUnitScale="3x:0,0,0,0,0,0" bufferOpacity="1" bufferSize="0.75" bufferBlendMode="0" bufferSizeUnits="MM"/>
<background shapeSizeMapUnitScale="3x:0,0,0,0,0,0" shapeOffsetX="0" shapeRadiiX="0" shapeSizeX="0" shapeSizeUnit="MM" shapeRadiiMapUnitScale="3x:0,0,0,0,0,0" shapeDraw="0" shapeJoinStyle="64" shapeRadiiY="0" shapeOpacity="1" shapeOffsetY="0" shapeBorderColor="128,128,128,255" shapeBlendMode="0" shapeOffsetMapUnitScale="3x:0,0,0,0,0,0" shapeBorderWidthUnit="MM" shapeFillColor="255,255,255,255" shapeBorderWidthMapUnitScale="3x:0,0,0,0,0,0" shapeSizeType="0" shapeType="0" shapeRadiiUnit="MM" shapeBorderWidth="0" shapeSVGFile="" shapeRotationType="0" shapeOffsetUnit="MM" shapeRotation="0" shapeSizeY="0"/>
<shadow shadowOffsetUnit="MM" shadowOffsetAngle="135" shadowDraw="0" shadowUnder="0" shadowRadiusAlphaOnly="0" shadowScale="100" shadowColor="0,0,0,255" shadowOffsetGlobal="1" shadowRadius="1.5" shadowBlendMode="6" shadowRadiusUnit="MM" shadowOffsetMapUnitScale="3x:0,0,0,0,0,0" shadowOpacity="0.7" shadowRadiusMapUnitScale="3x:0,0,0,0,0,0" shadowOffsetDist="1"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<substitutions/>
</text-style>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<text-format addDirectionSymbol="0" leftDirectionSymbol="&lt;" multilineAlign="0" useMaxLineLengthForAutoWrap="1" plussign="0" wrapChar="" rightDirectionSymbol=">" reverseDirectionSymbol="0" decimals="3" formatNumbers="0" autoWrapLength="0" placeDirectionSymbol="0"/>
<placement fitInPolygonOnly="0" xOffset="0" maxCurvedCharAngleIn="20" centroidWhole="0" yOffset="0" placementFlags="0" preserveRotation="1" labelOffsetMapUnitScale="3x:0,0,0,0,0,0" repeatDistanceUnits="MM" distUnits="MM" offsetType="0" priority="5" predefinedPositionOrder="TR,TL,BR,BL,R,L,TSR,BSR" centroidInside="1" rotationAngle="0" repeatDistance="0" dist="0" quadOffset="4" maxCurvedCharAngleOut="-20" offsetUnits="MM" placement="1" distMapUnitScale="3x:0,0,0,0,0,0" repeatDistanceMapUnitScale="3x:0,0,0,0,0,0"/>
<rendering fontMinPixelSize="3" upsidedownLabels="0" limitNumLabels="0" scaleMax="10000000" obstacle="1" fontMaxPixelSize="10000" drawLabels="1" displayAll="1" mergeLines="0" minFeatureSize="0" obstacleFactor="1" fontLimitPixelSize="0" zIndex="0" labelPerPart="0" obstacleType="0" scaleVisibility="0" scaleMin="1" maxNumLabels="2000"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<dd_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</dd_properties>
</settings>
</labeling>
<customproperties>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<property key="embeddedWidgets/count" value="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<property key="variableNames"/>
<property key="variableValues"/>
</customproperties>
<blendMode>0</blendMode>
<featureBlendMode>0</featureBlendMode>
<layerOpacity>1</layerOpacity>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<SingleCategoryDiagramRenderer diagramType="Histogram" attributeLegend="1">
<DiagramCategory labelPlacementMethod="XHeight" diagramOrientation="Up" opacity="1" enabled="0" penAlpha="255" height="15" minScaleDenominator="0" minimumSize="0" lineSizeScale="3x:0,0,0,0,0,0" barWidth="5" backgroundAlpha="255" penColor="#000000" sizeType="MM" sizeScale="3x:0,0,0,0,0,0" penWidth="0" maxScaleDenominator="1e+08" rotationOffset="270" backgroundColor="#ffffff" scaleDependency="Area" width="15" lineSizeType="MM" scaleBasedVisibility="0">
<fontProperties description="Noto Sans,9,-1,5,50,0,0,0,0,0" style=""/>
<attribute label="" color="#000000" field=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</DiagramCategory>
</SingleCategoryDiagramRenderer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<DiagramLayerSettings placement="0" obstacle="0" dist="0" linePlacementFlags="18" priority="0" showAll="1" zIndex="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</properties>
</DiagramLayerSettings>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<geometryOptions geometryPrecision="0" removeDuplicateNodes="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<activeChecks/>
<checkConfiguration/>
</geometryOptions>
<fieldConfiguration>
<field name="fid">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="AREA">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="PERIMETER">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="STADTTEILE">
<editWidget type="Range">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="STADTTEI_1">
<editWidget type="Range">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="S_A_">
<editWidget type="Range">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="S_A_ID">
<editWidget type="Range">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="O_NAME">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="ORTSTEIL">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="STADTTEIL">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="OT_SCHL">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="GEM_SCHL">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="ZVS">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="NAME">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="PLZ">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="KERNSTADT_">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="ORTSRATSBE">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="PLG_KITA">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="PLG_BERATU">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="PLG_JUFOE">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="VERFLECHTU">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="FUNKTIONSB">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="T_DATUM">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="Impfbez_Nr">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="Impfzentru">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
</fieldConfiguration>
<aliases>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<alias index="0" field="fid" name=""/>
<alias index="1" field="AREA" name=""/>
<alias index="2" field="PERIMETER" name=""/>
<alias index="3" field="STADTTEILE" name=""/>
<alias index="4" field="STADTTEI_1" name=""/>
<alias index="5" field="S_A_" name=""/>
<alias index="6" field="S_A_ID" name=""/>
<alias index="7" field="O_NAME" name=""/>
<alias index="8" field="ORTSTEIL" name=""/>
<alias index="9" field="STADTTEIL" name=""/>
<alias index="10" field="OT_SCHL" name=""/>
<alias index="11" field="GEM_SCHL" name=""/>
<alias index="12" field="ZVS" name=""/>
<alias index="13" field="NAME" name=""/>
<alias index="14" field="PLZ" name=""/>
<alias index="15" field="KERNSTADT_" name=""/>
<alias index="16" field="ORTSRATSBE" name=""/>
<alias index="17" field="PLG_KITA" name=""/>
<alias index="18" field="PLG_BERATU" name=""/>
<alias index="19" field="PLG_JUFOE" name=""/>
<alias index="20" field="VERFLECHTU" name=""/>
<alias index="21" field="FUNKTIONSB" name=""/>
<alias index="22" field="T_DATUM" name=""/>
<alias index="23" field="Impfbez_Nr" name=""/>
<alias index="24" field="Impfzentru" name=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</aliases>
<excludeAttributesWMS/>
<excludeAttributesWFS/>
<defaults>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<default applyOnUpdate="0" expression="" field="fid"/>
<default applyOnUpdate="0" expression="" field="AREA"/>
<default applyOnUpdate="0" expression="" field="PERIMETER"/>
<default applyOnUpdate="0" expression="" field="STADTTEILE"/>
<default applyOnUpdate="0" expression="" field="STADTTEI_1"/>
<default applyOnUpdate="0" expression="" field="S_A_"/>
<default applyOnUpdate="0" expression="" field="S_A_ID"/>
<default applyOnUpdate="0" expression="" field="O_NAME"/>
<default applyOnUpdate="0" expression="" field="ORTSTEIL"/>
<default applyOnUpdate="0" expression="" field="STADTTEIL"/>
<default applyOnUpdate="0" expression="" field="OT_SCHL"/>
<default applyOnUpdate="0" expression="" field="GEM_SCHL"/>
<default applyOnUpdate="0" expression="" field="ZVS"/>
<default applyOnUpdate="0" expression="" field="NAME"/>
<default applyOnUpdate="0" expression="" field="PLZ"/>
<default applyOnUpdate="0" expression="" field="KERNSTADT_"/>
<default applyOnUpdate="0" expression="" field="ORTSRATSBE"/>
<default applyOnUpdate="0" expression="" field="PLG_KITA"/>
<default applyOnUpdate="0" expression="" field="PLG_BERATU"/>
<default applyOnUpdate="0" expression="" field="PLG_JUFOE"/>
<default applyOnUpdate="0" expression="" field="VERFLECHTU"/>
<default applyOnUpdate="0" expression="" field="FUNKTIONSB"/>
<default applyOnUpdate="0" expression="" field="T_DATUM"/>
<default applyOnUpdate="0" expression="" field="Impfbez_Nr"/>
<default applyOnUpdate="0" expression="" field="Impfzentru"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</defaults>
<constraints>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp_strength="0" unique_strength="1" field="fid" notnull_strength="1" constraints="3"/>
<constraint exp_strength="0" unique_strength="0" field="AREA" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="PERIMETER" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="STADTTEILE" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="STADTTEI_1" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="S_A_" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="S_A_ID" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="O_NAME" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="ORTSTEIL" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="STADTTEIL" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="OT_SCHL" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="GEM_SCHL" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="ZVS" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="NAME" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="PLZ" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="KERNSTADT_" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="ORTSRATSBE" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="PLG_KITA" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="PLG_BERATU" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="PLG_JUFOE" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="VERFLECHTU" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="FUNKTIONSB" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="T_DATUM" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="Impfbez_Nr" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="Impfzentru" notnull_strength="0" constraints="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraints>
<constraintExpressions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp="" field="fid" desc=""/>
<constraint exp="" field="AREA" desc=""/>
<constraint exp="" field="PERIMETER" desc=""/>
<constraint exp="" field="STADTTEILE" desc=""/>
<constraint exp="" field="STADTTEI_1" desc=""/>
<constraint exp="" field="S_A_" desc=""/>
<constraint exp="" field="S_A_ID" desc=""/>
<constraint exp="" field="O_NAME" desc=""/>
<constraint exp="" field="ORTSTEIL" desc=""/>
<constraint exp="" field="STADTTEIL" desc=""/>
<constraint exp="" field="OT_SCHL" desc=""/>
<constraint exp="" field="GEM_SCHL" desc=""/>
<constraint exp="" field="ZVS" desc=""/>
<constraint exp="" field="NAME" desc=""/>
<constraint exp="" field="PLZ" desc=""/>
<constraint exp="" field="KERNSTADT_" desc=""/>
<constraint exp="" field="ORTSRATSBE" desc=""/>
<constraint exp="" field="PLG_KITA" desc=""/>
<constraint exp="" field="PLG_BERATU" desc=""/>
<constraint exp="" field="PLG_JUFOE" desc=""/>
<constraint exp="" field="VERFLECHTU" desc=""/>
<constraint exp="" field="FUNKTIONSB" desc=""/>
<constraint exp="" field="T_DATUM" desc=""/>
<constraint exp="" field="Impfbez_Nr" desc=""/>
<constraint exp="" field="Impfzentru" desc=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraintExpressions>
<expressionfields/>
<attributeactions>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<defaultAction key="Canvas" value="{00000000-0000-0000-0000-000000000000}"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</attributeactions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<attributetableconfig sortExpression="" actionWidgetStyle="dropDown" sortOrder="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<columns>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<column width="-1" type="field" name="fid" hidden="0"/>
<column width="-1" type="field" name="AREA" hidden="0"/>
<column width="-1" type="field" name="PERIMETER" hidden="0"/>
<column width="-1" type="field" name="STADTTEILE" hidden="0"/>
<column width="-1" type="field" name="STADTTEI_1" hidden="0"/>
<column width="-1" type="field" name="S_A_" hidden="0"/>
<column width="-1" type="field" name="S_A_ID" hidden="0"/>
<column width="-1" type="field" name="O_NAME" hidden="0"/>
<column width="-1" type="field" name="ORTSTEIL" hidden="0"/>
<column width="-1" type="field" name="STADTTEIL" hidden="0"/>
<column width="-1" type="field" name="OT_SCHL" hidden="0"/>
<column width="-1" type="field" name="GEM_SCHL" hidden="0"/>
<column width="-1" type="field" name="ZVS" hidden="0"/>
<column width="-1" type="field" name="NAME" hidden="0"/>
<column width="-1" type="field" name="PLZ" hidden="0"/>
<column width="-1" type="field" name="KERNSTADT_" hidden="0"/>
<column width="-1" type="field" name="ORTSRATSBE" hidden="0"/>
<column width="-1" type="field" name="PLG_KITA" hidden="0"/>
<column width="-1" type="field" name="PLG_BERATU" hidden="0"/>
<column width="-1" type="field" name="PLG_JUFOE" hidden="0"/>
<column width="-1" type="field" name="VERFLECHTU" hidden="0"/>
<column width="-1" type="field" name="FUNKTIONSB" hidden="0"/>
<column width="-1" type="field" name="T_DATUM" hidden="0"/>
<column width="-1" type="field" name="Impfbez_Nr" hidden="0"/>
<column width="-1" type="field" name="Impfzentru" hidden="0"/>
<column width="-1" type="actions" hidden="1"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</columns>
</attributetableconfig>
<conditionalstyles>
<rowstyles/>
<fieldstyles/>
</conditionalstyles>
<editform tolerant="1"></editform>
<editforminit/>
<editforminitcodesource>0</editforminitcodesource>
<editforminitfilepath></editforminitfilepath>
<editforminitcode><![CDATA[# -*- coding: utf-8 -*-
"""
QGIS forms can have a Python function that is called when the form is
opened.
Use this function to add extra logic to your forms.
Enter the name of the function in the "Python Init function"
field.
An example follows:
"""
from qgis.PyQt.QtWidgets import QWidget
def my_form_open(dialog, layer, feature):
geom = feature.geometry()
control = dialog.findChild(QWidget, "MyLineEdit")
]]></editforminitcode>
<featformsuppress>0</featformsuppress>
<editorlayout>generatedlayout</editorlayout>
<editable>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<field editable="1" name="AREA"/>
<field editable="1" name="FUNKTIONSB"/>
<field editable="1" name="GEM_SCHL"/>
<field editable="1" name="Impfbez_Nr"/>
<field editable="1" name="Impfzentru"/>
<field editable="1" name="KERNSTADT_"/>
<field editable="1" name="NAME"/>
<field editable="1" name="ORTSRATSBE"/>
<field editable="1" name="ORTSTEIL"/>
<field editable="1" name="OT_SCHL"/>
<field editable="1" name="O_NAME"/>
<field editable="1" name="PERIMETER"/>
<field editable="1" name="PLG_BERATU"/>
<field editable="1" name="PLG_JUFOE"/>
<field editable="1" name="PLG_KITA"/>
<field editable="1" name="PLZ"/>
<field editable="1" name="STADTTEIL"/>
<field editable="1" name="STADTTEILE"/>
<field editable="1" name="STADTTEI_1"/>
<field editable="1" name="S_A_"/>
<field editable="1" name="S_A_ID"/>
<field editable="1" name="T_DATUM"/>
<field editable="1" name="VERFLECHTU"/>
<field editable="1" name="ZVS"/>
<field editable="1" name="fid"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</editable>
<labelOnTop>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<field labelOnTop="0" name="AREA"/>
<field labelOnTop="0" name="FUNKTIONSB"/>
<field labelOnTop="0" name="GEM_SCHL"/>
<field labelOnTop="0" name="Impfbez_Nr"/>
<field labelOnTop="0" name="Impfzentru"/>
<field labelOnTop="0" name="KERNSTADT_"/>
<field labelOnTop="0" name="NAME"/>
<field labelOnTop="0" name="ORTSRATSBE"/>
<field labelOnTop="0" name="ORTSTEIL"/>
<field labelOnTop="0" name="OT_SCHL"/>
<field labelOnTop="0" name="O_NAME"/>
<field labelOnTop="0" name="PERIMETER"/>
<field labelOnTop="0" name="PLG_BERATU"/>
<field labelOnTop="0" name="PLG_JUFOE"/>
<field labelOnTop="0" name="PLG_KITA"/>
<field labelOnTop="0" name="PLZ"/>
<field labelOnTop="0" name="STADTTEIL"/>
<field labelOnTop="0" name="STADTTEILE"/>
<field labelOnTop="0" name="STADTTEI_1"/>
<field labelOnTop="0" name="S_A_"/>
<field labelOnTop="0" name="S_A_ID"/>
<field labelOnTop="0" name="T_DATUM"/>
<field labelOnTop="0" name="VERFLECHTU"/>
<field labelOnTop="0" name="ZVS"/>
<field labelOnTop="0" name="fid"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</labelOnTop>
<widgets/>
<previewExpression>fid</previewExpression>
<mapTip></mapTip>
</maplayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<maplayer geometry="Polygon" simplifyDrawingTol="1" simplifyAlgorithm="0" simplifyMaxScale="1" styleCategories="AllStyleCategories" minScale="1e+08" maxScale="0" simplifyLocal="1" type="vector" labelsEnabled="0" readOnly="0" refreshOnNotifyEnabled="0" simplifyDrawingHints="1" autoRefreshTime="0" refreshOnNotifyMessage="" hasScaleBasedVisibilityFlag="0" autoRefreshEnabled="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<extent>
<xmin>611951</xmin>
<ymin>5797784.5</ymin>
<xmax>629677.25</xmax>
<ymax>5817605</ymax>
</extent>
<id>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</id>
<datasource>./test_project_wms_grouped_layers.gpkg|layername=cdb_lines</datasource>
<keywordList>
<value></value>
</keywordList>
<layername>cdb_lines</layername>
<srs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</srs>
<resourceMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title></title>
<abstract></abstract>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<contact>
<name></name>
<organization></organization>
<position></position>
<voice></voice>
<fax></fax>
<email></email>
<role></role>
</contact>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<links/>
<fees></fees>
<encoding></encoding>
<crs>
<spatialrefsys>
<proj4></proj4>
<srsid>0</srsid>
<srid>0</srid>
<authid></authid>
<description></description>
<projectionacronym></projectionacronym>
<ellipsoidacronym></ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</crs>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<extent>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<spatial maxx="0" maxz="0" minx="0" maxy="0" dimensions="2" miny="0" crs="" minz="0"/>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<temporal>
<period>
<start></start>
<end></end>
</period>
</temporal>
</extent>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</resourceMetadata>
<provider encoding="UTF-8">ogr</provider>
<vectorjoins/>
<layerDependencies/>
<dataDependencies/>
<legend type="default-vector"/>
<expressionfields/>
<map-layer-style-manager current="default">
<map-layer-style name="default"/>
</map-layer-style-manager>
<auxiliaryLayer/>
<flags>
<Identifiable>1</Identifiable>
<Removable>1</Removable>
<Searchable>1</Searchable>
</flags>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<renderer-v2 forceraster="0" type="categorizedSymbol" symbollevels="0" attr="typ" enableorderby="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<categories>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<category label="Ortsteil" symbol="0" value="Ortsteil" render="true"/>
<category label="Stadtteil" symbol="1" value="Stadtteil" render="true"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</categories>
<symbols>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="fill" clip_to_extent="1" force_rhr="0" name="0">
<layer class="SimpleFill" locked="0" pass="0" enabled="1">
<prop k="border_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="color" v="207,94,42,255"/>
<prop k="joinstyle" v="bevel"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="78,70,255,255"/>
<prop k="outline_style" v="solid"/>
<prop k="outline_width" v="0.5"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="style" v="no"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="fill" clip_to_extent="1" force_rhr="0" name="1">
<layer class="SimpleFill" locked="0" pass="0" enabled="1">
<prop k="border_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="color" v="153,148,255,255"/>
<prop k="joinstyle" v="bevel"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="153,148,255,255"/>
<prop k="outline_style" v="solid"/>
<prop k="outline_width" v="0.5"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="style" v="no"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
</symbols>
<source-symbol>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<symbol alpha="1" type="fill" clip_to_extent="1" force_rhr="0" name="0">
<layer class="SimpleFill" locked="0" pass="0" enabled="1">
<prop k="border_width_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="color" v="145,82,45,255"/>
<prop k="joinstyle" v="bevel"/>
<prop k="offset" v="0,0"/>
<prop k="offset_map_unit_scale" v="3x:0,0,0,0,0,0"/>
<prop k="offset_unit" v="MM"/>
<prop k="outline_color" v="35,35,35,255"/>
<prop k="outline_style" v="solid"/>
<prop k="outline_width" v="0.26"/>
<prop k="outline_width_unit" v="MM"/>
<prop k="style" v="solid"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<data_defined_properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</data_defined_properties>
</layer>
</symbol>
</source-symbol>
<rotation/>
<sizescale/>
</renderer-v2>
<customproperties>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<property key="dualview/previewExpressions" value="&quot;id&quot;"/>
<property key="embeddedWidgets/count" value="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<property key="variableNames"/>
<property key="variableValues"/>
</customproperties>
<blendMode>0</blendMode>
<featureBlendMode>0</featureBlendMode>
<layerOpacity>1</layerOpacity>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<SingleCategoryDiagramRenderer diagramType="Histogram" attributeLegend="1">
<DiagramCategory labelPlacementMethod="XHeight" diagramOrientation="Up" opacity="1" enabled="0" penAlpha="255" height="15" minScaleDenominator="0" minimumSize="0" lineSizeScale="3x:0,0,0,0,0,0" barWidth="5" backgroundAlpha="255" penColor="#000000" sizeType="MM" sizeScale="3x:0,0,0,0,0,0" penWidth="0" maxScaleDenominator="1e+08" rotationOffset="270" backgroundColor="#ffffff" scaleDependency="Area" width="15" lineSizeType="MM" scaleBasedVisibility="0">
<fontProperties description="Noto Sans,9,-1,5,50,0,0,0,0,0" style=""/>
<attribute label="" color="#000000" field=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</DiagramCategory>
</SingleCategoryDiagramRenderer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<DiagramLayerSettings placement="1" obstacle="0" dist="0" linePlacementFlags="18" priority="0" showAll="1" zIndex="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<properties>
<Option type="Map">
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="name" value=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<Option name="properties"/>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Option type="QString" name="type" value="collection"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</Option>
</properties>
</DiagramLayerSettings>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<geometryOptions geometryPrecision="0" removeDuplicateNodes="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<activeChecks/>
<checkConfiguration/>
</geometryOptions>
<fieldConfiguration>
<field name="fid">
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<editWidget type="TextEdit">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="id">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="typ">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="name">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
<field name="ortsrat">
<editWidget type="TextEdit">
<config>
<Option/>
</config>
</editWidget>
</field>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<field name="id_long">
<editWidget type="">
<config>
<Option/>
</config>
</editWidget>
</field>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</fieldConfiguration>
<aliases>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<alias index="0" field="fid" name=""/>
<alias index="1" field="id" name=""/>
<alias index="2" field="typ" name=""/>
<alias index="3" field="name" name=""/>
<alias index="4" field="ortsrat" name=""/>
<alias index="5" field="id_long" name=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</aliases>
<excludeAttributesWMS/>
<excludeAttributesWFS/>
<defaults>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<default applyOnUpdate="0" expression="" field="fid"/>
<default applyOnUpdate="0" expression="" field="id"/>
<default applyOnUpdate="0" expression="" field="typ"/>
<default applyOnUpdate="0" expression="" field="name"/>
<default applyOnUpdate="0" expression="" field="ortsrat"/>
<default applyOnUpdate="0" expression="" field="id_long"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</defaults>
<constraints>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp_strength="0" unique_strength="1" field="fid" notnull_strength="1" constraints="3"/>
<constraint exp_strength="0" unique_strength="1" field="id" notnull_strength="1" constraints="3"/>
<constraint exp_strength="0" unique_strength="0" field="typ" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="name" notnull_strength="1" constraints="1"/>
<constraint exp_strength="0" unique_strength="0" field="ortsrat" notnull_strength="0" constraints="0"/>
<constraint exp_strength="0" unique_strength="0" field="id_long" notnull_strength="0" constraints="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraints>
<constraintExpressions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<constraint exp="" field="fid" desc=""/>
<constraint exp="" field="id" desc=""/>
<constraint exp="" field="typ" desc=""/>
<constraint exp="" field="name" desc=""/>
<constraint exp="" field="ortsrat" desc=""/>
<constraint exp="" field="id_long" desc=""/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</constraintExpressions>
<expressionfields/>
<attributeactions>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<defaultAction key="Canvas" value="{00000000-0000-0000-0000-000000000000}"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</attributeactions>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<attributetableconfig sortExpression="" actionWidgetStyle="dropDown" sortOrder="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<columns>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<column width="-1" type="field" name="id" hidden="0"/>
<column width="-1" type="field" name="typ" hidden="0"/>
<column width="-1" type="field" name="name" hidden="0"/>
<column width="-1" type="field" name="ortsrat" hidden="0"/>
<column width="-1" type="actions" hidden="1"/>
<column width="-1" type="field" name="fid" hidden="0"/>
<column width="-1" type="field" name="id_long" hidden="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</columns>
</attributetableconfig>
<conditionalstyles>
<rowstyles/>
<fieldstyles/>
</conditionalstyles>
<editform tolerant="1"></editform>
<editforminit/>
<editforminitcodesource>0</editforminitcodesource>
<editforminitfilepath></editforminitfilepath>
<editforminitcode><![CDATA[# -*- coding: utf-8 -*-
"""
QGIS forms can have a Python function that is called when the form is
opened.
Use this function to add extra logic to your forms.
Enter the name of the function in the "Python Init function"
field.
An example follows:
"""
from qgis.PyQt.QtWidgets import QWidget
def my_form_open(dialog, layer, feature):
geom = feature.geometry()
control = dialog.findChild(QWidget, "MyLineEdit")
]]></editforminitcode>
<featformsuppress>0</featformsuppress>
<editorlayout>generatedlayout</editorlayout>
<editable>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<field editable="1" name="fid"/>
<field editable="1" name="id"/>
<field editable="1" name="name"/>
<field editable="1" name="ortsrat"/>
<field editable="1" name="typ"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</editable>
<labelOnTop>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<field labelOnTop="0" name="fid"/>
<field labelOnTop="0" name="id"/>
<field labelOnTop="0" name="name"/>
<field labelOnTop="0" name="ortsrat"/>
<field labelOnTop="0" name="typ"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</labelOnTop>
<widgets/>
<previewExpression>id</previewExpression>
<mapTip></mapTip>
</maplayer>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<maplayer styleCategories="AllStyleCategories" minScale="1e+08" maxScale="0" type="raster" refreshOnNotifyEnabled="0" autoRefreshTime="0" refreshOnNotifyMessage="" hasScaleBasedVisibilityFlag="0" autoRefreshEnabled="0">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<extent>
<xmin>611425.600499999942258</xmin>
<ymin>5808334.13232080265879631</ymin>
<xmax>623219.587000000057742</xmax>
<ymax>5814172.86767920013517141</ymax>
</extent>
<id>osm_85c8eb94_b6fa_437b_b91a_7816ef2e2243</id>
<datasource>GPKG:./test_project_wms_grouped_layers.gpkg:osm</datasource>
<keywordList>
<value></value>
</keywordList>
<layername>osm</layername>
<srs>
<spatialrefsys>
<proj4>+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
<srsid>2105</srsid>
<srid>25832</srid>
<authid>EPSG:25832</authid>
<description>ETRS89 / UTM zone 32N</description>
<projectionacronym>utm</projectionacronym>
<ellipsoidacronym>GRS80</ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</srs>
<resourceMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title></title>
<abstract></abstract>
<links/>
<fees></fees>
<encoding></encoding>
<crs>
<spatialrefsys>
<proj4></proj4>
<srsid>0</srsid>
<srid>0</srid>
<authid></authid>
<description></description>
<projectionacronym></projectionacronym>
<ellipsoidacronym></ellipsoidacronym>
<geographicflag>false</geographicflag>
</spatialrefsys>
</crs>
<extent/>
</resourceMetadata>
<provider>gdal</provider>
<noData>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
<noDataList bandNo="1" useSrcNoData="0"/>
<noDataList bandNo="2" useSrcNoData="0"/>
<noDataList bandNo="3" useSrcNoData="0"/>
<noDataList bandNo="4" useSrcNoData="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</noData>
<map-layer-style-manager current="default">
<map-layer-style name="default"/>
</map-layer-style-manager>
<flags>
<Identifiable>1</Identifiable>
<Removable>1</Removable>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
<Searchable>0</Searchable>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</flags>
<customproperties>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<property key="identify/format" value="Value"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</customproperties>
<pipe>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<rasterrenderer redBand="1" greenBand="2" opacity="1" type="multibandcolor" blueBand="3" alphaBand="4">
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<rasterTransparency/>
<minMaxOrigin>
<limits>MinMax</limits>
<extent>WholeRaster</extent>
<statAccuracy>Estimated</statAccuracy>
<cumulativeCutLower>0.02</cumulativeCutLower>
<cumulativeCutUpper>0.98</cumulativeCutUpper>
<stdDevFactor>2</stdDevFactor>
</minMaxOrigin>
<redContrastEnhancement>
<minValue>0</minValue>
<maxValue>255</maxValue>
<algorithm>NoEnhancement</algorithm>
</redContrastEnhancement>
<greenContrastEnhancement>
<minValue>0</minValue>
<maxValue>255</maxValue>
<algorithm>NoEnhancement</algorithm>
</greenContrastEnhancement>
<blueContrastEnhancement>
<minValue>0</minValue>
<maxValue>255</maxValue>
<algorithm>NoEnhancement</algorithm>
</blueContrastEnhancement>
</rasterrenderer>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<brightnesscontrast brightness="0" contrast="0"/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<huesaturation saturation="0" colorizeBlue="128" colorizeStrength="100" grayscaleMode="0" colorizeRed="255" colorizeGreen="128" colorizeOn="0"/>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
<rasterresampler maxOversampling="2"/>
</pipe>
<blendMode>0</blendMode>
</maplayer>
</projectlayers>
<layerorder>
<layer id="osm_85c8eb94_b6fa_437b_b91a_7816ef2e2243"/>
<layer id="cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf"/>
<layer id="cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b"/>
<layer id="as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467"/>
<layer id="as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76"/>
</layerorder>
<properties>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<WFSTLayers>
<Insert type="QStringList">
<value>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</value>
<value>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</value>
<value>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</value>
<value>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</value>
</Insert>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<Delete type="QStringList">
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<value>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</value>
<value>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</value>
<value>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</value>
<value>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</value>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
</Delete>
<Update type="QStringList">
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<value>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</value>
<value>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</value>
<value>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</value>
<value>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</value>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
</Update>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
</WFSTLayers>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<Gui>
<SelectionColorGreenPart type="int">255</SelectionColorGreenPart>
<CanvasColorGreenPart type="int">255</CanvasColorGreenPart>
<CanvasColorBluePart type="int">255</CanvasColorBluePart>
<CanvasColorRedPart type="int">255</CanvasColorRedPart>
<SelectionColorAlphaPart type="int">255</SelectionColorAlphaPart>
<SelectionColorBluePart type="int">0</SelectionColorBluePart>
<SelectionColorRedPart type="int">255</SelectionColorRedPart>
</Gui>
<WMSRootName type="QString"></WMSRootName>
<WMSAccessConstraints type="QString">None</WMSAccessConstraints>
<WMSFees type="QString">conditions unknown</WMSFees>
<Measure>
<Ellipsoid type="QString">GRS80</Ellipsoid>
</Measure>
<WMTSUrl type="QString"></WMTSUrl>
<WMSContactPhone type="QString"></WMSContactPhone>
<WMTSGrids>
<Config type="QStringList"/>
<CRS type="QStringList"/>
</WMTSGrids>
<WMSOnlineResource type="QString"></WMSOnlineResource>
<WMSKeywordList type="QStringList">
<value></value>
</WMSKeywordList>
<WCSUrl type="QString"></WCSUrl>
<WMTSPngLayers>
<Layer type="QStringList"/>
<Project type="bool">false</Project>
<Group type="QStringList"/>
</WMTSPngLayers>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
<WFSLayersPrecision>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf type="int">8</cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
<as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76 type="int">8</as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b type="int">8</cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b>
<as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467 type="int">8</as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467>
Fix server WFS TYPENAME filter in describeFeatureType Fixes #20198 with tests
2019-01-22 14:28:36 +01:00
</WFSLayersPrecision>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<WMSServiceAbstract type="QString"></WMSServiceAbstract>
<WFSLayers type="QStringList">
<value>as_areas_bbe3c71b_356c_49f5_9fc2_ae771bcdd467</value>
<value>as_symbols_3a1cdeef_9082_4d07_be5c_47c956bd7e76</value>
<value>cdb_labels_8ee74af8_e7ba_4d80_9e0d_5b0b956d3daf</value>
<value>cdb_lines_3f5c3c6d_db6d_4681_9291_7109f8d69f8b</value>
</WFSLayers>
<WMSRequestDefinedDataSources type="bool">false</WMSRequestDefinedDataSources>
<SpatialRefSys>
<ProjectionsEnabled type="int">1</ProjectionsEnabled>
</SpatialRefSys>
<WMTSJpegLayers>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Layer type="QStringList"/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<Project type="bool">false</Project>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Group type="QStringList"/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
</WMTSJpegLayers>
<WMSMaxAtlasFeatures type="int">1</WMSMaxAtlasFeatures>
<WMSContactOrganization type="QString"></WMSContactOrganization>
<Macros>
<pythonCode type="QString"></pythonCode>
</Macros>
<WFSUrl type="QString"></WFSUrl>
<Legend>
<filterByMap type="bool">false</filterByMap>
</Legend>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<PAL>
<CandidatesPolygon type="int">30</CandidatesPolygon>
<TextFormat type="int">0</TextFormat>
<DrawOutlineLabels type="bool">true</DrawOutlineLabels>
<SearchMethod type="int">0</SearchMethod>
<DrawRectOnly type="bool">false</DrawRectOnly>
<CandidatesLine type="int">50</CandidatesLine>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<ShowingAllLabels type="bool">false</ShowingAllLabels>
<ShowingCandidates type="bool">false</ShowingCandidates>
<ShowingPartialsLabels type="bool">true</ShowingPartialsLabels>
<CandidatesPoint type="int">16</CandidatesPoint>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
</PAL>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<Measurement>
<AreaUnits type="QString">m2</AreaUnits>
<DistanceUnits type="QString">meters</DistanceUnits>
</Measurement>
<DefaultStyles>
<Opacity type="double">1</Opacity>
<ColorRamp type="QString"></ColorRamp>
<Marker type="QString"></Marker>
<Line type="QString"></Line>
<Fill type="QString"></Fill>
<RandomColors type="bool">true</RandomColors>
</DefaultStyles>
<WMSServiceCapabilities type="bool">false</WMSServiceCapabilities>
<WMSContactPerson type="QString"></WMSContactPerson>
<WMTSMinScale type="int">5000</WMTSMinScale>
<WMTSLayers>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Layer type="QStringList"/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<Project type="bool">false</Project>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<Group type="QStringList"/>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
</WMTSLayers>
<Paths>
<Absolute type="bool">false</Absolute>
</Paths>
<WMSUrl type="QString"></WMSUrl>
<WMSPrecision type="QString">8</WMSPrecision>
<WMSAddWktGeometry type="bool">false</WMSAddWktGeometry>
<WCSLayers type="QStringList"/>
<WMSContactPosition type="QString"></WMSContactPosition>
<WMSImageQuality type="int">90</WMSImageQuality>
GML parser set NULL values when parsing empty tags This is part of a bigger fix to support NULL values in WFS client and server components.
2019-01-23 17:51:01 +01:00
<WMSServiceTitle type="QString"></WMSServiceTitle>
Fix OWS project property issue: couldn't unset project title This is the right behavior, btw there are other issues in the server component that ignores the main bool setting WMSServiceCapabilities completely.
2019-01-24 10:15:11 +01:00
<PositionPrecision>
<Automatic type="bool">true</Automatic>
<DegreeFormat type="QString">MU</DegreeFormat>
<DecimalPlaces type="int">2</DecimalPlaces>
</PositionPrecision>
<WMSSegmentizeFeatureInfoGeometry type="bool">false</WMSSegmentizeFeatureInfoGeometry>
<WMSContactMail type="QString"></WMSContactMail>
Fix typo in error message (and related tests)
2019-01-24 09:08:37 +01:00
<WMSUseLayerIDs type="bool">false</WMSUseLayerIDs>
[server] Fix layer order rendering when layers are in groups (#8796) * [server] Fix layer order rendering when layers are in groups Fixes #20810 * Update test images * [server] Fix order of layers in subgroups basically: layers in WMS is specified in a comma separated list where leftmost layer is drawn first (it's at the bottom) and QGIS layer order is exactly the opposite: first layer in the TOP (topmost) is drawn last (it is at the top). For this reason the server reverses the list before passing it to the renderer. * Fix order of layers in test * Update src/server/services/wms/qgswmsrenderer.cpp
2019-01-07 13:13:30 +01:00
</properties>
<visibility-presets/>
<transformContext/>
<projectMetadata>
<identifier></identifier>
<parentidentifier></parentidentifier>
<language></language>
<type></type>
<title>QGIS Server - Grouped Layer</title>
<abstract></abstract>
<contact>
<name></name>
<organization></organization>
<position></position>
<voice></voice>
<fax></fax>
<email></email>
<role></role>
</contact>
<links/>
<author>Burghardt Scholle</author>
<creation>2018-12-11T10:39:23</creation>
</projectMetadata>
<Annotations/>
<Layouts/>
</qgis>
Reference in New Issue Copy Permalink