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

T-Rex errors on specific zoon level #271

Open
dmitrykinakh opened this issue Nov 19, 2021 · 0 comments
Open

T-Rex errors on specific zoon level #271

dmitrykinakh opened this issue Nov 19, 2021 · 0 comments

Comments

@dmitrykinakh
Copy link

dmitrykinakh commented Nov 19, 2021

We are using https://github.com/t-rex-tileserver/t-rex/releases/tag/v0.14.1 version to do tiling. However, we have noticed that on some zoom levels. For this particular layer, it happens only on zoom level 11 (I've tried to generate up to z16)

docker-compose run --name TL_01 --rm trex-master sh -c 't_rex generate --tileset municipal_zoning_code --overwrite true --minzoom 10 --maxzoom 12 --extent -81.658619,28.346742,-80.863155,28.786278 --config /storage/trex/config.toml;'
2021-11-19 07:15:10.832 INFO Reading configuration from '/storage/trex/gridics.toml'
2021-11-19 07:15:11.005 INFO Tile cache s3: https://s3.us-east-1.amazonaws.com/MY-BACKET
Generating tileset 'municipal_zoning_code'...
Level 11: 5 / 20 [==================================================>----------------------------------------]  
2021-11-19 07:15:27.526 ERROR Layer 'municipal_zoning_code': error deserializing column 0: a Postgres value was `NULL`
2021-11-19 07:15:27.526 ERROR Row { columns: [Column { name: "geom", type: Other(Other { name: "geometry", oid: 16413, kind: Simple, schema: "public" }) }, Column { name: "id", type: Varchar }, Column { name: "title", type: Varchar }, Column { name: "land_use_type", type: Varchar }, Column { name: "place", type: VarcharArray }, Column { name: "jurisdiction", type: Varchar }, Column { name: "uniqueid", type: Int4 }, Column { name: "color", type: Varchar }] }
Level 12: 70 / 70 [==========================================================================]  

Not sure that the problem is somewhere in data since in that case, that should be a problem on all zoom levels and not on a specific one. Looking for any recommendation on what to check in configs to prevent this.

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

1 participant