Replies: 2 comments
-
While not intuitive, this is the expected results. |
Beta Was this translation helpful? Give feedback.
-
I understand some of the rationale. However, as you say, this is really counter-intuitive and therefore not what one would expect. If I wanted a single symbol I would just use another layer with a single point, with total control on where to put it. Similarly if I needed multiple points, probably with different symbols, I would use a collection. However, in the case of a unique symbol for all points the use is very similar (if not the same) as using circles. The same layer data could be reused. If not, what is the point then of showing just the first symbol if the data is a LineString? Isn't it also arbitrary or perhaps considered buggy? It feels wasteful to me to add another layer with exactly the same data points and classifying it as MultiPoint just to achieve the same intuitive behavior. Unless there is another way to reuse the same data array in the GeoJSON declaration that I am not aware of? Many thanks. |
Beta Was this translation helpful? Give feedback.
-
When displaying a layer using GeoJSON LineString data, the behavior of displaying symbols and circles is not consistent.
For example, if specifying the layer style using:
The output result with some GeoJSON example application looks like:
As could be expected, each point is shown with a circle. This similar to displaying GeoJSON MultiPoint data. The example image also shows a line layer using the same source data.
However, if a symbol layer is used instead:
The output result is then:
Where, unlike the circle style, only one symbol icon is shown at the first data point. This also happens if using a constant text-field symbol.
maplibre-gl-js version: 4.1.1
browser: Tested in Edge, Chrome and Firefox
Beta Was this translation helpful? Give feedback.
All reactions