-
Notifications
You must be signed in to change notification settings - Fork 3
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
Foreground 3D extrusions missing in output tiles #4
Comments
JTS has no winding requirement. If you need to reverse a ring, there is a way to extract the coordinate sequence from a polygon (and, I presume, its holes) and reverse it and build a new poly from the result. This gets to be non-trivial, though, if there are "islands" inside holes (i.e., a polygon with a hole with another positive area inside the negative space). You'll have to build the hierarchy of rings yourself and then check them for winding manually (assuming valid geometry, this should just be a bunch of |
Oof, that certainly seems like the cause. The MapBox Vector Tile spec states:
Thinking about this more generally, and we can move the conversation, does an option to re-wind ring geometries make sense as something that the new VectorPipe API provides? Otherwise it appears that any attempt to use extrusion will render poorly. |
It makes sense. I've always wondered why JTS isn't picky about winding order, since it's very common throughout computer graphics that polygons have CCW winding. (Come to think of it, it's weird that the VT spec wants a CW exterior winding...) At any rate, this is a thing VP should provide. Go ahead and create an issue for it? Include that quote from the spec, if you would. |
👍 |
Issue is the same as experienced in mapbox/mapbox-gl-js#7767:
We aren't generating tiles with PostGIS so we're likely experiencing a similar issue somewhere in the JTS + GeoTrellis + GenerateVT. The linked issue notes that:
Might be a good first place to look, and ensure that our tiles are exporting geometries that are correctly wound clockwise.
We'd require further testing to determine if this issue is present in the new VectorPipe RC2+ releases.
The text was updated successfully, but these errors were encountered: