You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use clustering in a layer in our mapservice. This works fine. But if we ask for the capabilities through the WMS we get only a part of the capabilities.
We use the following lines in our mapfile in the LAYER section:
LAYER
NAME 'xxx'
STATUS ON
PROJECTION
'init=epsg:4326'
END
...
CLUSTER
MAXDISTANCE 15
BUFFER 10
REGION "ellipse" # This line is responsible for not being able to get the capabilities
END
LABELITEM "Cluster_FeatureCount"
CLASSITEM "Cluster_FeatureCount"
CLASS
NAME 'xxx'
EXPRESSION "1"
STYLE
COLOR 240 228 66
OUTLINECOLOR 0 0 0
SYMBOL "square"
MINSIZE 16
MAXSIZE 120
END
END
CLASS
NAME 'xxx (geclusterd)'
EXPRESSION ("[Cluster_FeatureCount]" != "1")
STYLE
COLOR 240 228 66
OUTLINECOLOR 0 0 0
SYMBOL "square"
MINSIZE 16
MAXSIZE 120
END
LABEL
SIZE 8
COLOR 0 0 0
ALIGN CENTER
PRIORITY 10
BUFFER 1
PARTIALS TRUE
POSITION cc
FORCE TRUE
END
END
END
If we comment out the line REGION “ellipse” we can get the complete capabilities. If the line is not commented out we get the partial capabilities.
The WMS version number is not important. If the line REGION "ellipse" is not commented out the GetCapabilities request for every WMS version goes wrong.
Steps to reproduce the problem.
Create a mapfile with a layer based on the layer information above. Use a points layer from an Oracle database (our data is saved in an Oracle database). Use the GetCapabilities request to get the error.
Comment out the line REGION "ellipse" and use again the GetCapabilities request to get the capabilities.
Solution/Workaround
If I add an extent in the layer the GetCapabilities request works. With of without commenting out the line REGION "ellipse".
So to get everything working I added the line EXTENT -100000 200000 650000 950000 beyond the PROJECTION
Expected behavior and actual behavior.
We use clustering in a layer in our mapservice. This works fine. But if we ask for the capabilities through the WMS we get only a part of the capabilities.
We use the following lines in our mapfile in the LAYER section:
LAYER
NAME 'xxx'
STATUS ON
PROJECTION
'init=epsg:4326'
END
...
CLUSTER
MAXDISTANCE 15
BUFFER 10
REGION "ellipse" # This line is responsible for not being able to get the capabilities
END
LABELITEM "Cluster_FeatureCount"
CLASSITEM "Cluster_FeatureCount"
CLASS
NAME 'xxx'
EXPRESSION "1"
STYLE
COLOR 240 228 66
OUTLINECOLOR 0 0 0
SYMBOL "square"
MINSIZE 16
MAXSIZE 120
END
END
CLASS
NAME 'xxx (geclusterd)'
EXPRESSION ("[Cluster_FeatureCount]" != "1")
STYLE
COLOR 240 228 66
OUTLINECOLOR 0 0 0
SYMBOL "square"
MINSIZE 16
MAXSIZE 120
END
LABEL
SIZE 8
COLOR 0 0 0
ALIGN CENTER
PRIORITY 10
BUFFER 1
PARTIALS TRUE
POSITION cc
FORCE TRUE
END
END
END
If we comment out the line REGION “ellipse” we can get the complete capabilities. If the line is not commented out we get the partial capabilities.
For example (please modify !!!):
I expected the following request to work:
http://localhost:6080/cgi-bin/mapserv.exe?map=/ms4w/apps/local-demo/services.map&version=1.0.9&service=WMS&request=GetCapabilities
The WMS version number is not important. If the line REGION "ellipse" is not commented out the GetCapabilities request for every WMS version goes wrong.
Steps to reproduce the problem.
Create a mapfile with a layer based on the layer information above. Use a points layer from an Oracle database (our data is saved in an Oracle database). Use the GetCapabilities request to get the error.
Comment out the line REGION "ellipse" and use again the GetCapabilities request to get the capabilities.
Solution/Workaround
If I add an extent in the layer the GetCapabilities request works. With of without commenting out the line REGION "ellipse".
So to get everything working I added the line EXTENT -100000 200000 650000 950000 beyond the PROJECTION
Attach simple test case (drag/drop it here)
Uploading test-data.zip…
Operating system
Windows
RHEL Linux (running container in podman)
MapServer version and installation method
MS4W 4.0.5 with Mapserver 7.7.0-dev
Mapserver 8 build from source for Linux with Oracle support
The text was updated successfully, but these errors were encountered: