blocks|key|164891|text|对于像行政区域这样相互“捕捉”的整洁功能，TopoJSON是理想的，但对于更杂乱或有机的数据无济于事。如果您的数据仅仅是点，那么TopoJSON一点帮助都没有。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164892|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

TopoJSON is ideal for tidy features that "snap" to each other, like administrative regions, but doesn't help with more messy or organic data. If your data is simply points, then TopoJSON is no help at all.

blocks|key|382814|text|这取决于许多考虑因素。其中包括：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|382815|1)你想要表示的一个或多个特征的性质(数据模型)+2)你希望与这些特征相关联的任何属性3)你希望这些特征在页面上的表现(静态与动态)|382816|然而，这是一个很难从抽象上回答的问题。关于一些细节，如果你有一个连续的多边形覆盖或其他情况，其中特征共享边界，topojson的模型允许你利用冗余并将其纳入模型中。|382817|阅读文档，剖析示例(例如，bl.ocks.org)，然后获取一些数据并在geojson和topojson中表示它，然后创建您自己的可视化。|382818|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It depends on many considerations. Among them are the following:

1) The nature (data model) of the feature or features you'd like to represent
2) Any attributes you'd like to have associated with those features
3) How you'd like these features to behave on the page (static vs dynamic)

However, this is a tough question to answer in the abstract. Regarding some specifics, if you have a contiguous polygon coverage or another situation where features are sharing boundaries, topojson's model allows you to exploit the redundancy and factor that into the model.

Read the documentation, dissect examples (e.g, bl.ocks.org), and then get some data and represent it in both geojson and topojson and create your own visualizations.

blocks|key|382851|text|如果您关心文件大小或拓扑，则使用TopoJSON。如果您不关心这两者，那么为了简单起见，请使用GeoJSON。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|382852|TopoJSON的主要优势是大小。通过消除冗余并使用更有效的固定精度整数坐标编码，TopoJSON文件通常比GeoJSON文件小一个数量级。TopoJSON文件的第二个优点是，对拓扑进行编码具有有用的应用程序，例如拓扑保留简化(类似于MapShaper)和自动网格生成(如this+example+choropleth中的状态-状态边界)。|offset|length|382853|这些优点是有代价的:更复杂的文件格式。例如，在JavaScript中，通常使用TopoJSON+client+library将TopoJSON转换为GeoJSON，以便与d3.geoPath等标准工具一起使用。(在Python中，您可以使用topojson.py。)此外，TopoJSON的整数格式需要量化坐标，这意味着如果您不小心，它可能会引入舍入误差。(请参阅topojson+-q的文档。)|style|CODE|382854|对于不需要拓扑的服务器端几何操作，GeoJSON可能是更简单的选择。否则，如果需要拓扑或希望通过网络将几何体发送到客户端，则使用TopoJSON。|382855|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cartogis.org/docs/proceedings/2006/bloch_harrower.pdf|1|http://bl.ocks.org/4060606|2|https://github.com/topojson/topojson/|3|https://github.com/d3/d3-geo/blob/master/README.md#geoPath|4|https://github.com/sgillies/topojson/blob/master/topojson.py^0|0|39|9|0|3S|N|1|0|52|B|13|N|2|2D|A|3|3C|B|4|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]|$D|16|E|17|1|18]]|A|$]]|$1|F|3|G|5|6|7|19|8|@$D|1A|E|1B|H|I]]|9|@$D|1C|E|1D|1|1E]|$D|1F|E|1G|1|1H]|$D|1I|E|1J|1|1K]]|A|$]]|$1|J|3|K|5|6|7|1L|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]|X|$5|O|P|Q|A|$R|Y]]|Z|$5|O|P|Q|A|$R|10]]]]

If you care about file size or topology, then use TopoJSON. If you don’t care about either, then use GeoJSON for simplicity’s sake.

The primary advantage of TopoJSON is size. By eliminating redundancy and using a more efficent fixed-precision integer encoding of coordinates, TopoJSON files are often an order of magnitude smaller than GeoJSON files. The secondary advantage of TopoJSON files is that encoding the topology has useful applications, such as topology-preserving simplification (similar to <a href="http://www.cartogis.org/docs/proceedings/2006/bloch_harrower.pdf" rel="noreferrer">MapShaper</a>) and automatic mesh generation (as in the state-state boundaries in <a href="http://bl.ocks.org/4060606" rel="noreferrer">this example choropleth</a>).

These advantages come at a cost: a more complex file format. In JavaScript, for example, you’d typically use the <a href="https://github.com/topojson/topojson/" rel="noreferrer">TopoJSON client library</a> to convert TopoJSON to GeoJSON for use with standard tools such as <a href="https://github.com/d3/d3-geo/blob/master/README.md#geoPath" rel="noreferrer">d3.geoPath</a>. (In Python, you can use <a href="https://github.com/sgillies/topojson/blob/master/topojson.py" rel="noreferrer">topojson.py</a>.) Also, TopoJSON’s integer format requires quantizing coordinates, which means that it can introduce rounding error if you’re not careful. (See the documentation for <code>topojson -q</code>.)

For server-side manipulation of geometries that does not require topology, then GeoJSON is probably the simpler choice. Otherwise, if you need topology or want to send the geometry over the wire to a client, then use TopoJSON.

What is the difference between GeoJSON and TopoJSON and when would I use one over the other?

The <a href="https://github.com/mbostock/topojson/" rel="noreferrer">description of TopoJSON on GitHub</a> implies the TopoJSON files are 80% smaller. So why not just use TopoJSON all the time?

Difference between GeoJSON and TopoJSON

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

GeoJSON和TopoJSON之间的区别是什么?什么时候我应该使用一个而不是另一个？意味着TopoJSON文件要小80%。那么为什么不一直使用TopoJSON呢？

问GeoJSON与TopoJSON的区别
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GeoJSON与TopoJSON的区别EN