[1] The GeoJSON Format Specification ( 版) http://geojson.org/geojson-spec.html
[2] GeoJSON -- JSON Geometry and Feature Description ( 版) http://geojson.org/
[3] The GeoJSON Format Specification ( 版) http://geojson.org/geojson-spec.html
[4] The GeoJSON Format Specification ( ( 版)) http://geojson.org/geojson-spec.html
[5] The GeoJSON Format Specification ( ( 版)) http://geojson.org/geojson-spec.html
[6] ( ( 版)) http://www.iana.org/assignments/media-types/application/vnd.geo+json
[7] GeoJSON Specification ( 版) http://geojson.org/geojson-spec.html
[8] Mapping geoJSON files on GitHub - User Documentation ( 版) https://help.github.com/articles/mapping-geojson-files-on-github/
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] }
[10] RFC 7946 - The GeoJSON Format () https://tools.ietf.org/html/rfc7946
[11] RFC 8142 - GeoJSON Text Sequences () https://tools.ietf.org/html/rfc8142
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.
[12] ST_AsGeoJSON () https://postgis.net/docs/ST_AsGeoJSON.html
[13] RFC 8142 をベクトルストリームのワイヤフォーマットに使う理由 - Qiita () https://qiita.com/hfu/items/8e88561788063ec3624a
application/vnd.geo+json