tegola | Tegola is a Mapbox Vector Tile server written in Go | Map library

by go-spatial Go Version: v0.16.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | tegola Summary

tegola is a Go library typically used in Geo, Map applications. tegola has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Tegola is a vector tile server delivering Mapbox Vector Tiles with support for PostGIS and GeoPackage data providers. User documentation can be found at tegola.io.

Support

Quality

Security

License

Reuse

Support

tegola has a medium active ecosystem.

It has 1088 star(s) with 177 fork(s). There are 51 watchers for this library.

It had no major release in the last 12 months.

There are 153 open issues and 398 have been closed. On average issues are closed in 69 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of tegola is v0.16.0

Quality

tegola has 0 bugs and 0 code smells.

Security

tegola has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

tegola code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

tegola is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

tegola releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of tegola

Get all kandi verified functions for this library.

tegola Key Features

No Key Features are available at this moment for tegola.

tegola Examples and Code Snippets

No Code Snippets are available at this moment for tegola.

Community Discussions

Trending Discussions on tegola

Vector Tiles (tegola) / WMS overlay problem on OpenLayers 6.22

Why do points from vector tiles at lower zoom levels not match source data?

QUESTION

Vector Tiles (tegola) / WMS overlay problem on OpenLayers 6.22

Asked 2020-Jun-13 at 11:43

I am trying to understand some of the vector tile logic and implementation on openlayers (6.3.1). I have 2 layers that simply don't overlay, resulting on the screenshoot below. I have looked into multiple example but they just increase my technical doubts, and confusion here is the system:

Vector tile server

Tegola server (gospatial/tegola:v0.10.4) , using default options (tiles at 256 pixel? size source data srid=4326 and SQL SQL:FROM XXX.XXX WHERE geom && !BBOX!)

Server layer description is here: http://tiles.isric.org/capabilities/wosis.json

WMS service

WMS service: http://maps.isric.org/mapserv?map=/map/soc.map

Running example

Full code example in jsfiddle: https://jsfiddle.net/jorgejesus/vt6qndrw/1/

Code parts:

So for the tegola server I have something like this:

...

ANSWER

Answered 2020-Jun-04 at 14:08

Your vector tile source is EPSG:3857 and vector tiles cannot be reprojected. You will need to display both layers in EPSG:3857 (or find an alternative EPSG:4326 source for the vector tile data)

Source https://stackoverflow.com/questions/62195008

QUESTION

Why do points from vector tiles at lower zoom levels not match source data?

Asked 2020-Apr-27 at 10:17

I am querying raw vector tiles from zoom level 8 from tiles created to zoom level 11. I then convert the point features in these tiles to geojson. The converted feature geometries do not match the tile geometry at zoom level 11, or tiles from zoom level 11 converted to geojson. I have created the tiles with two different programs (tegola and geojson-vt). I am converting the tiles with vt2geojson. I am trying to determine at what stage in the conversion process the geometry is being manipulated - tile creation, tile conversion back to geojson, or in mapbox gl js. As far as I can tell the coordinates are not being trimmed in the creation or conversion process, but am not 100% positive on that. I get the reason for the simplification of lines and polygons at lower zoom levels, but I do not see any reason to manipulate point geometry.

As can be seen in the image, the points start to drift apart after the max zoom level of the original tiles. One workaround is to simply filter the vector tiles to only show the features in the resulting geojson features as the properties are still intact or store the coordinates in the properties, but this is not ideal.

Bottom line - if I want to view points as close to the original data as possible, what max tile zoom level should I use (i.e., 11, 12, 13, 14), and at what stage does the geometry get manipulated?

...

ANSWER

Answered 2020-Apr-27 at 10:17

It's a bit hard to tell what your exact question is, but if I'm understanding correctly it is essentially: "Why do I lose spatial accuracy when I overzoom my vector tiles" and the answer is "because you're overzooming them". It's inherent in the way they work.

Your original data probably had 10 significant figures of precision. Each offset for a point in a vector tile is usually encoded as an integer between 1 and 4096.

Your options are basically:

increase the spatial accuracy of the generated tiles (eg, tippecanoe's -d flag)
generate tiles to a higher zoom level
don't overzoom them so much

Source https://stackoverflow.com/questions/61444264

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install tegola

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: