RFC 8142: GeoJSON Text Sequences
In plain English — editorial summary, not part of the RFC
This document describes the GeoJSON text sequence format and "application/geo+json-seq" media type. This format is based on JavaScript Object Notation (JSON) text sequences and GeoJSON, and it makes arbitrarily large geographic datasets incrementally parseable without restricting the form of GeoJSON texts within a sequence.
Document record
- Document ID
- RFC8142
- Published
- April 2017
- Authors
- S. Gillies
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7946The GeoJSON FormatCurrent
August 2016
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
- RFC 7638JSON Web Key (JWK) ThumbprintCurrent
September 2015
- RFC 7520Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE)Current
May 2015
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 7517JSON Web Key (JWK)Current
May 2015
- RFC 7516JSON Web Encryption (JWE)Current
May 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?