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

ST_AsMVT: Proper handling of id column #303

Closed
wants to merge 2 commits into from

Conversation

@Algunenano
Copy link
Member

commented Sep 17, 2018

Trac: https://trac.osgeo.org/postgis/ticket/4128

Missing documentation update

@strk strk closed this in 429d77a Sep 17, 2018

@Komzpa

This comment has been minimized.

Copy link
Member

commented Sep 17, 2018

@Algunenano thanks for getting this polished! :)

@Algunenano

This comment has been minimized.

Copy link
Member Author

commented Sep 17, 2018

Np, I've been looking into the MVT code lately so I knew where to look.

@joedjc

This comment has been minimized.

Copy link

commented Oct 19, 2018

@Algunenano This is great! It will be really useful in combination with the new feature-state mapbox feature. Do you have an idea when this will be available to use? I notice it's listed as part of the 3.0 release, but according to the roadmap that could be a year away? Would be great if it can make the next release if it's ready

@Komzpa

This comment has been minimized.

Copy link
Member

commented Oct 19, 2018

@joedjc it will be around next september, PostGIS 2.5.0 just went out. You can use development builds for now.

@joedjc

This comment has been minimized.

Copy link

commented Oct 19, 2018

@Komzpa Thank you for the quick reply. Ok I will try that as it would be a shame not to be able to use this now as it's going to offer significant new functionality. I've not used a dev build before so if you have any reference on how to use (and if it's possible to use with a AWS managed RDS) i'd be very grateful.

Edit: It does seem like using a development build in AWS may not be possible. It seems a shame to wait nearly a year to release functionality which has already been finalised. Is there a chance it could be added to an interim release?

@Komzpa

This comment has been minimized.

Copy link
Member

commented Oct 24, 2018

@joedjc dev release functionality happens to be rewritten multiple times before release (and id code was rewritten twice already). Features in 2.5 are frozen for almost half a year already, and it is not expected to change.

If you are looking for commercial help, you can contact some vendor who will handle all the intermediate releases hassle faster for you. RDS is known for lagging too far behind, anyway.

https://postgrespro.com/contacts provides development builds and managed installations of postgres, as one option, drop them a line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.