Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering artifacts, square tiles #54

Closed
skinkie opened this issue Aug 21, 2017 · 7 comments
Closed

Rendering artifacts, square tiles #54

skinkie opened this issue Aug 21, 2017 · 7 comments

Comments

@skinkie
Copy link

skinkie commented Aug 21, 2017

I noticed that I get rendering artifacts in MapBox GL and OpenLayers. Is there a setting to prevent the "square tiles" here I mean the edge around them?

Mapbox GL
bla

OpenLayers
bla1

@pka
Copy link
Member

pka commented Aug 21, 2017

I remember seeing these tile borders before, but actually never investigated their cause. Can you give more information about your configuration? I think, I saw them with custom projections only.

@skinkie
Copy link
Author

skinkie commented Aug 21, 2017

Hi @pka thanks for your fast feedback. I am basically evaluating multiple vector tile solutions, after tegola I tried t-rex (first couldn't get t-rex it to work, then was impressed by the webbased gui, and understood more). For tegola I created some materialized views with 3857 as projection. Which I resused in t-rex. My problems with tegola were basically rendering artifacts when zooming in Mapbox GL, which the Mapbox GL people referred as 'buffer-size' issues. My current problem with t-rex (next to the tiling borders) is that the generation is relatively slow, but when the browser is not in developer mode, the client doesn't fetch / or is extremely slow in fetching the pbf files.

Part of the configuration is:

[service.mvt]
viewer = true

[datasource]
type = "postgis"
url = "postgresql://openov:s k i p p e d@localhost/openov"

[grid]
# Predefined grids: web_mercator, wgs84
predefined = "web_mercator"

[[tileset]]
name = "zoning"
#extent = [-180.0,-90.0,180.0,90.0]
[[tileset.layer]]
name = "zones"
table_name = "zones"
geometry_field = "wkb_geometry"
geometry_type = "POLYGON"
srid = 3857
fid_field = "zone_id"
simplify = true
buffer_size = 10
query_limit = 100000
[[tileset.layer.query]]
sql = """SELECT "wkb_geometry","zonenr","zone_id","zonenaam","nulzones" FROM ovzones_3857 WHERE wkb_geometry && !bbox!"""

The data is open, so if you want to have a pg_dump and the complete config to reproduce, I am happy to provide it.

@pka
Copy link
Member

pka commented Sep 13, 2017

Sorry, I needed a break, but now back working on t-rex.

I've imported test data from http://data.openov.nl/zones/ like this:
ogr2ogr -t_srs EPSG:3857 -unsetFieldWidth -nln ovzones_3857 -f PostgreSQL PG:dbname=natural_earth_vectors ovzones/ovzones01022016.shp

I also get some artifacts, but my result is quite different. Can you describe your import or send me a dump (pg_dump -Fc) and the full config?

grafik

@skinkie
Copy link
Author

skinkie commented Sep 13, 2017

@pka
Copy link
Member

pka commented Sep 13, 2017

Looks better here:

grafik

Are you sure, that there isn't a polygon layer with buffer_size = 0 in your configuration? Because this would explain a border caused by polygon clipping.

@skinkie
Copy link
Author

skinkie commented Sep 13, 2017

I do have an other configuration which has buffer_size = 0, what should that be?

@pka
Copy link
Member

pka commented Sep 13, 2017

buffer_size is the additional pixel border around a tile. When clipping a polygon this buffer hides the clipped polygon outline.

tileschema

Maybe you've filled the cache with the other configuration?

@pka pka closed this as completed Jul 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants