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

featuresAt() should expose layers that were laid out via "ref" #847

Closed
peterqliu opened this issue Nov 20, 2014 · 0 comments
Closed

featuresAt() should expose layers that were laid out via "ref" #847

peterqliu opened this issue Nov 20, 2014 · 0 comments

Comments

@peterqliu
Copy link
Contributor

For example, I'm making a map where I define a road casing in the traditional manner, and then define the road itself via a ref to its casing.

When I featuresAt() at that position, only the casing shows up. I want to get both, while enjoying the performance benefits of ref
lbud pushed a commit that referenced this issue Dec 20, 2014
Return ref layers in featuresAt, refs #847
2ca21d5
@lbud lbud mentioned this issue Dec 20, 2014
Merged
jfirebaugh added a commit that referenced this issue Jan 5, 2015
@jfirebaugh
Merge pull request #901 from mapbox/featuresAtRefs
2f334b8 
Return ref layers in featuresAt, refs #847
jfirebaugh added a commit that referenced this issue Jan 21, 2015
@jfirebaugh
Reimplement ref layer support in featuresAt (#847)
0dee48f 
This is a blend of #901 and #939.

The format for featuresAt results changed again. Instead of
result-per-geometry-cross-layer, each result has a `layers`
array with all layers that contain the feature. Thus avoiding
duplication of geometry and properties in the result set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfirebaugh @peterqliu