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

Describe Polygon Handling? #4

Closed
pramsey opened this issue Apr 14, 2014 · 3 comments
Closed

Describe Polygon Handling? #4

pramsey opened this issue Apr 14, 2014 · 3 comments

Comments

@pramsey
Copy link

pramsey commented Apr 14, 2014

Describing the implications of polygon handling in a tile setup would be useful, I think. Presumably users will want to transport polygons twice, once as a closed path, for filling, and once as an unclosed path for rendering the boundary.

@fredmorin
Copy link

I share the same concern, how do a polygon span accross multiple tiles? 👍

@kkaefer
Copy link
Contributor

kkaefer commented May 8, 2014

@pramsey I am not sure I fully understand that question. We are currently using one instance of a feature to render both a filled polygon as well as the perimeter as a separate line. The consuming implementation can derive appropriate geometries that it needs for the type of renderer it is using.

As for closed paths, the geometry format defines the ClosePath operation. Your implementation can either use this and pass it on to the rendering system (e.g. when using HTML5 canvas, you just call .closePath()), or manually track the initial starting position of this feature and create a new line segment to the beginning.

@kkaefer kkaefer closed this as completed May 8, 2014
@kkaefer
Copy link
Contributor

kkaefer commented May 8, 2014

@fredmorin Your question is being tracked in #8.

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

3 participants