[SERVER-30522] TopoJSON Support! Created: 04/Aug/17 Updated: 27/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Victor Stewart | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | qi-geo | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
For very complex shapes, GeoJSON becomes almost unusable because the representation is so unnecessarily explicit. Expressing GeoJSON data in TopoJSON can express these complex shapes in a fraction of the size! Beyond the initial size reduction, TopoJSON also lends itself much better to simplification methods. For example, all of the world's timezones in GeoJSON is some 120MB! Converting to TopoJSON and applying some simplification methods, this can be reduced to some 30MB easily. This also facilitates must quicker computations, in a performance critical live environment. (Like locating users within a timezone). https://github.com/topojson/topojson |
| Comments |
| Comment by Ian Whalen (Inactive) [ 14/Aug/17 ] |
|
asya could you please link this as related to any other requests for alternate geo representations? |
| Comment by Kelsey Schubert [ 05/Aug/17 ] |
|
Thanks for the feature request, victorstewart. I've marked this ticket for consideration by Query Team – please continue to watch for updates. |