Geometry errors at various zoom levels

[allspatial]

I am getting geometry errors in several polygon and line layers at various zoom levels. The higher the zoom level the more errors appear (screenshot 2). I am using tegola_darwin_amd64 (v 0.3.0) from the release page. I can provide sample data in Shapefile format or as PostgreSQL dump if required.

Many thanks,

Michael

[ARolek]

@allspatial thanks for the report. What client side library are you using? If you're using Mapbox then we have seen this issue and it should be fixed in our 0.4 release which comes with geometry clipping (and is nearing completion!).

If you're using OpenLayers then this is a new issue and your shapefile would be helpful.

[allspatial]

Hi @ARolek! Many thanks for your swift reply! I am indeed using mapbox (mapbox-gl-js v 0.29.0). I wouldn't mind using OpenLayers but I did a few tests about three months back and the performance of OL when labelling thousands of features was significantly lower than with mabbox-gl-js. However, that might have improved meanwhile. I am very much looking forward to your 0.4 release then.

[ARolek]

@allspatial I agree, OL support for labeling with MVT still needs some love. Once we have clipping merged into master, would you mind helping us test the pre release?

[allspatial]

I would be glad to test the pre-release, I really want to use Tegola for quite an important government project. Are there any instructions on how to build the binary (I haven't done anything with Go so far)?

[ARolek]

@allspatial I can put together some instructions in the Readme.md for building. Do you have go installed? If so, you can clone the repo, and then navigate to the cmd/ directory and run the following:

go build -o tegola *.go
./tegola --config=path/to/config.toml

For additional details on the config file check out our docs.

[allspatial]

I installed Go via Homebrew. Building the tegola binary went smoothly. I had to cd to cmd/tegola/ though, not just cmd/. Many thanks!!!

[ARolek]

@allspatial good catch. I have added the building instructions to the Readme file here. We will let you know when clipping is ready for you to test.

[allspatial]

@ARolek, perfect. I am looking forward to that. Many thanks again!

[gdey]

Moving this to #56; as I believe these errors are related to clipping. (As pointed out by @allspatial )