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.

Sign up for GitHub

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

Jump to bottom

Possible fix for complex geoms #218

Merged
merged 1 commit into from
Oct 7, 2021
Merged

Possible fix for complex geoms #218

merged 1 commit into from
Oct 7, 2021

Conversation

christianversloot
Copy link
Contributor

As far as I can see this fixes #215 out-of-the-box for complex geometries (CURVEPOLYGON, MULTISURFACE, ...) without spatial inequality for simple types (POINT, LINESTRING, ...) occurring because of it (see #215).

stepankuzmin
stepankuzmin approved these changes Oct 7, 2021
View reviewed changes
Copy link
Collaborator

@stepankuzmin stepankuzmin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @christianversloot

Sorry for the extended response, and thanks a lot for the contribution. I've checked this, and everything seems to work like a charm.

@stepankuzmin stepankuzmin added this to the 0.6.0 milestone Oct 7, 2021
@stepankuzmin stepankuzmin merged commit 8b5fbf9 into maplibre:master Oct 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@stepankuzmin stepankuzmin stepankuzmin approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.6.0
Development

Successfully merging this pull request may close these issues.

Martin throwing HTTP 500 on complex geometry types
2 participants
@christianversloot @stepankuzmin