/
290.txt
66 lines (45 loc) · 2.75 KB
/
290.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
[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>