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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
the native iOS client seem to have issues rendering certain polygons. We can't really identify why or under which circumstances it triggers, but it is a bug not found in the web client. Here are some screenshots, description below.
The red layer is our land-layer from a custom data source. The data is initially stored in a postGIS db, and validated with ST_IsValid.
The poly should cover all the brown areas, which is the map background color. The first screenshot in each pair is from the native client, the other is from the web client covering the same location. Style and source is identical.
As you can see, a lot of red polys are missing in the native client. The web client has no issues rendering these polys.
The straight lines that cut through large polys are cutting lines in the custom dataset, which leads us to believe that the iOS client is dropping certain polys all together.
We don't have more information than this to go on, we'll start experimenting with various preprocessing steps such as cutting and merging the polys before building the pbf-tiles.
The data is custom, but we'll be more than happy to provide pbf samples, styles and postGIS db-extracts in private.
The text was updated successfully, but these errors were encountered:
Which in turn causes the native client to completely drop rendering certain polygons:
We then meged the polygons to a single multipolygon before exporting to mbtiles:
Which in turn led to proper rendering:
The layer contains only geometry, no attributes fields are passed through the MBS export in either case, so it seems like a pure geometry issue. We can share both sources if you need debug material. Again, the js-client has no issues rendering either data source.
I'd be interested in the sample material. Can you please send them to konstantin (at) mapbox.com? The JS renderer uses different approach to polygon rendering which doesn't involve tessellation. However, that will change soon since rendering is faster with properly tessellated polygons.
Hello,
the native iOS client seem to have issues rendering certain polygons. We can't really identify why or under which circumstances it triggers, but it is a bug not found in the web client. Here are some screenshots, description below.
The red layer is our land-layer from a custom data source. The data is initially stored in a postGIS db, and validated with ST_IsValid.
The poly should cover all the brown areas, which is the map background color. The first screenshot in each pair is from the native client, the other is from the web client covering the same location. Style and source is identical.
As you can see, a lot of red polys are missing in the native client. The web client has no issues rendering these polys.
The straight lines that cut through large polys are cutting lines in the custom dataset, which leads us to believe that the iOS client is dropping certain polys all together.
We don't have more information than this to go on, we'll start experimenting with various preprocessing steps such as cutting and merging the polys before building the pbf-tiles.
The data is custom, but we'll be more than happy to provide pbf samples, styles and postGIS db-extracts in private.
The text was updated successfully, but these errors were encountered: