[1] [CITE@en[The GeoJSON Format Specification]] ([TIME[2008-06-17 00:41:30 +09:00]] 版) <http://geojson.org/geojson-spec.html>

[2] [CITE@en[GeoJSON -- JSON Geometry and Feature Description]] ([TIME[2008-06-17 00:41:24 +09:00]] 版) <http://geojson.org/>

[3] [CITE@en[The GeoJSON Format Specification]]
([TIME[2008-06-17 00:41:30 +09:00]] 版)
<http://geojson.org/geojson-spec.html>

[4] [CITE@en[The GeoJSON Format Specification]]
( ([TIME[2008-06-16 15:41:30 +09:00]] 版))
<http://geojson.org/geojson-spec.html>

[5] [CITE@en[The GeoJSON Format Specification]]
( ([TIME[2008-06-16 15:41:30 +09:00]] 版))
<http://geojson.org/geojson-spec.html>

[6] ( ([TIME[2014-05-21 05:34:47 +09:00]] 版))
<http://www.iana.org/assignments/media-types/application/vnd.geo+json>

[7] [CITE[GeoJSON Specification]]
([TIME[2015-03-15 10:38:01 +09:00]] 版)
<http://geojson.org/geojson-spec.html>

[8] [CITE[Mapping geoJSON files on GitHub - User Documentation]]
([TIME[2015-05-20 18:36:45 +09:00]] 版)
<https://help.github.com/articles/mapping-geojson-files-on-github/>

[FIG(quote)[
[FIGCAPTION[
[9] [CITE@en[GET statuses/show/:id | Twitter Developers]]
([TIME[2015-10-04 11:16:38 +09:00]] 版)
<https://dev.twitter.com/rest/reference/get/statuses/show/%3Aid>
]FIGCAPTION]

> The JSON response mostly uses conventions laid out in GeoJSON. Unfortunately, the coordinates that Twitter renders are reversed from the GeoJSON specification (GeoJSON specifies a longitude then a latitude, whereas we are currently representing it as a latitude then a longitude). Our JSON renders as: "geo": { "type":"Point", "coordinates":'''['''37.78029, -122.39697''']''' }

]FIG]


[10] [CITE@en[RFC 7946 - The GeoJSON Format]]
([TIME[2016-08-19 22:23:34 +09:00]])
<https://tools.ietf.org/html/rfc7946>

[11] [CITE@en[RFC 8142 - GeoJSON Text Sequences]]
([TIME[2017-05-07 22:41:08 +09:00]])
<https://tools.ietf.org/html/rfc8142>


[FIG(quote)[
[FIGCAPTION[
[18] [CITE@en[geojson/geojson-text-sequences: GeoJSON feature sequences]]
([TIME[2016-03-23 12:00:13 +09:00]] 版)
<https://github.com/geojson/geojson-text-sequences>
]FIGCAPTION]

> GeoJSON Feature Sequences are a straightforward adaptation of JSON Text Sequences. A GeoJSON Feature Sequence is a document containing, instead of a single GeoJSON Feature Collection, multiple GeoJSON Feature texts that can be parsed and produced incrementally.


> RFC 7464 (JSON Text Sequences) defines how parsers should behave on encountering malformed JSON records and allows for pretty-printed records, while approaches such as the ones described in https://en.wikipedia.org/wiki/JSON_Streaming#Line_delimited_JSON do not.

]FIG]


[12] [CITE[ST_AsGeoJSON]]
([TIME[2018-07-05 06:28:49 +09:00]])
<https://postgis.net/docs/ST_AsGeoJSON.html>

[13] [CITE[RFC 8142 をベクトルストリームのワイヤフォーマットに使う理由 - Qiita]]
([TIME[2019-03-28 20:32:22 +09:00]])
<https://qiita.com/hfu/items/8e88561788063ec3624a>

[FIG(quote)[
[FIGCAPTION[
[14] [CITE[Geomark Developer Guide]]
([TIME[2022-08-12T10:55:24.000Z]], [TIME[2024-04-23T11:52:51.909Z]])
<https://apps.gov.bc.ca/pub/geomark/docs/fileFormats.html>
]FIGCAPTION]

> 	application/vnd.geo+json

]FIG]


-[15] [CITE@en[GitHub - mapbox/geojson-vt: Slice GeoJSON into vector tiles on the fly in the browser]], [TIME[2025-10-07T13:57:11.000Z]] <https://github.com/mapbox/geojson-vt>
- [16] [CITE@ja[MapLibre で GeoJSON タイルを読む #JavaScript - Qiita]], [TIME[2025-10-09T05:13:05.000Z]] <https://qiita.com/mg_kudo/items/832ee30ed39b6c25df60>
- [17] [CITE@en[GitHub - mghs15/maplibre-geojson-tile: MapLibre で GeoJSON タイルを読み込む実装]], [TIME[2025-10-09T05:13:19.000Z]] <https://github.com/mghs15/maplibre-geojson-tile>