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

Don't union out boundaries between features #30

Open
ericsoco opened this issue Sep 16, 2016 · 2 comments
Open

Don't union out boundaries between features #30

ericsoco opened this issue Sep 16, 2016 · 2 comments
Assignees
@ericsoco
Labels
pre-launch

Comments

@ericsoco
Copy link
Contributor

ericsoco commented Sep 16, 2016 •
edited
Loading

Difference between:

screen shot 2016-09-16 at 4 07 02 pm

and:

screen shot 2016-09-16 at 4 07 44 pm
@ericsoco ericsoco changed the title Don Don't union out boundaries between features Sep 16, 2016
@ericsoco
Copy link
Contributor Author

See: 95dad97

This was referenced Sep 20, 2016
Open
Open
@ericsoco ericsoco self-assigned this Nov 15, 2016
@ericsoco
Copy link
Contributor Author

The way GitHub's geojson-diff handles this is to first iterate over all features and check for matches, then diff only those that don't match.

Then, any new features (by index) appear as adds, and any absent features appear as deletes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ericsoco ericsoco

Labels
pre-launch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ericsoco