[Maps] Vector tile layer with only line features shows Polygon styling in Layer Style UI

[kindsun]

Currently tracks layers default to polygon styling which is confusing for the user since "fill color" won't really apply, but it's the first option listed when you go to style the tracks layer

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[kindsun]

Actually this is a user error. Closing!

[kindsun]

Reopening, this is valid for Geo lines using the following instructions:

1. Use GeoJSON uploader to upload this file
2. Follow through the normal layer adding process

[nreese]

Closing.

In the description screen shot, the icon is a vector tile layer icon meaning the Documents layer has scaling set to "Use vector tiles". There is no feature meta data available for vector tile layers so the styling UI does not know that the source is only lines.

If you set scaling to "Limit" then the form correctly selects lines displaying the styling UI. The only caveat to this is if the layer panel is opened before the layer has finished syncing data. Then the UI defaults to showing polygon styling because feature meta data not yet available.

[kindsun]

There is no feature meta data available for vector tile layers so the styling UI does not know that the source is only lines.

Point well taken, and I understand the solution isn't so straightforward with vector tiles, but I believe this should be captured as a UX issue. The solution might be as simple as swapping the locations of the Fill color and Border color adjustments and possibly renaming Border color. As it stands right now, when you have a vector tile line layer and go to adjust what appears to be the first valid adjustment, nothing happens and it's confusing.

We might also consider disabling Lines and Points and just having one well thought out style menu that has a logical flow for covering data we don't entirely know the shape of.

[nreese]

We might also consider disabling Lines and Points and just having one well thought out style menu that has a logical flow for covering data we don't entirely know the shape of.

I still recommend closing this issue. This is not something I see us addressing in the next 6 months and is a minor UX issue. I think it would be best to close this issue to try and keep our issue list only containing issue that will likely get addressed.

[thomasneirynck]

It's ok to keep this open I think. There's a backend issue on the ES-side that is blocking this. elastic/elasticsearch#49569

Given that all .mvt work is in flux right now (potentially having mvt generation pushed down into the ES-layer - elastic/elasticsearch#58696), I agree that this is a hard one to prioritize.

[thomasneirynck]

#92672 closes this for ES-data. The effort to solve this for 3rd party services, which do not provide any metadata about the geometries in the tile is likely not worth the benefit.

i