support current ST_ASMVT parameters #9

Open
skylarmt wants to merge 3 commits from smellman/dev-postgis-2.5.1 into master
Owner

Author: @smellman

@sk1p comment me in https://github.com/openmaptiles/postgis/pull/10#issuecomment-464446991

I just make PR for postgis docker image and I update postserve to support current ST_ASMVT.
I will test with planet (importing time over 32hours).

Author: @smellman @sk1p comment me in https://github.com/openmaptiles/postgis/pull/10#issuecomment-464446991 I just make [PR for postgis docker image](https://github.com/openmaptiles/postgis/pull/11) and I update postserve to support current ST_ASMVT. I will test with planet (importing time over 32hours).
Poster
Owner

Author: @nyurik

@smellman I actually had to do a full rewrite of this tool, see #11 -- it is far cleaner now,
without any locally done modifications. I won't merge it until I merge the proper SQL generation
into the openmaptiles repo.

Author: @nyurik @smellman I actually had to do a full rewrite of this tool, see #11 -- it is far cleaner now, without any locally done modifications. I won't merge it until I merge the proper SQL generation into the openmaptiles repo.
Poster
Owner

Author: @smellman

I will close this PR and I will make new PR with support buffer-size property. Also, I have other problem so I research it now.

Author: @smellman I will close this PR and I will make new PR with support buffer-size property. Also, I have other problem so I research it now.
Poster
Owner

Author: @nyurik

@smellman what do you mean by the buffer-size property? The buffer sizes are generated as part of the SQL generation -- because each layer has its own settings for the buffer sizes.

Author: @nyurik @smellman what do you mean by the buffer-size property? The buffer sizes are generated as part of the [SQL generation](https://github.com/openmaptiles/openmaptiles-tools/pull/34/files#diff-547b229652e18895a3c7488e08d66ac5R93) -- because each layer has its own settings for the buffer sizes.
Poster
Owner

Author: @smellman

Yes, I just upload my WIP branch.
I found 0/0/0 problem when I test this branch.

Author: @smellman Yes, I just upload my [WIP branch](https://github.com/smellman/postserve/tree/dev-postgis-2.5.1-buffer-size-support). I found 0/0/0 problem when I test this branch.
Poster
Owner

Author: @nyurik

@smellman could you paste your generated query to a gist? (as printed by your postserve when it starts) . This way it will be easier to compare just the SQL, and how it executes.

Author: @nyurik @smellman could you paste your generated query to a gist? (as printed by your postserve when it starts) . This way it will be easier to compare just the SQL, and how it executes.
This pull request has changes conflicting with the target branch.
  • server.py
  • Dockerfile
  • requirements.txt
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b smellman/dev-postgis-2.5.1 master
git pull origin smellman/dev-postgis-2.5.1

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff smellman/dev-postgis-2.5.1
git push origin master
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: skylarmt/postserve#9
Loading…
There is no content yet.