Forum Discussion
Which visual for polylines and points
Hello FoolzRailer1,
You are absolutely right when rivers are placed in the Position layer, Azure Maps aggregates the latitude/longitude values, which is why the geometry collapses into single points.
This happens because Azure Maps treats the Position layer as point data unless you provide WKT geometry. By putting the river WKT directly into the Location (WKT) field, the full line geometry is preserved and remains interactive.
So in short:
-
Reference Layer → correct river display, but static (no tooltips/filtering).
-
Data Layer (WKT) → keeps rivers dynamic and interactive, avoiding the averaging issue.
That’s the tradeoff depending on whether you need static background context or interactive visuals.
we’re glad the issue is now resolved after you added the rivers as a reference layer.
Really appreciate the effort you put into testing different approaches and sharing the screenshots back here. it helps make the discussion clearer and useful for others who may face a similar scenario.
Best regards,
Ganesh Singamshetty-
Community SupportHello FoolzRailer1,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
Hello v-ssriganesh
Thank you for the reply and followup!
I've tried opening your PowerBI but this is what I get when opening:
As I see it (and feel free to correct me), the points are averaged when adding a Position layer, which isn't really the look that is needed. When adding the rivers as a referencelayer, everything looks correct, but you loose the dynamic of the rivers in the visual.
When adding as a reference layer I get the below, rivers are blue and points showing with tooltips etc:
Appreciate the help!
- v-ssriganesh
Hello FoolzRailer1,
You are absolutely right when rivers are placed in the Position layer, Azure Maps aggregates the latitude/longitude values, which is why the geometry collapses into single points.
This happens because Azure Maps treats the Position layer as point data unless you provide WKT geometry. By putting the river WKT directly into the Location (WKT) field, the full line geometry is preserved and remains interactive.
So in short:
-
Reference Layer → correct river display, but static (no tooltips/filtering).
-
Data Layer (WKT) → keeps rivers dynamic and interactive, avoiding the averaging issue.
That’s the tradeoff depending on whether you need static background context or interactive visuals.
we’re glad the issue is now resolved after you added the rivers as a reference layer.
Really appreciate the effort you put into testing different approaches and sharing the screenshots back here. it helps make the discussion clearer and useful for others who may face a similar scenario.
Best regards,
Ganesh Singamshetty -
