RFC 7946 on The GeoJSON Format

rfc-editor@rfc-editor.org Thu, 11 August 2016 00:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C1112D54D; Wed, 10 Aug 2016 17:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qMy5UYJXvqpi; Wed, 10 Aug 2016 17:22:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 512F612B02C; Wed, 10 Aug 2016 17:22:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A3C0B80F6C; Wed, 10 Aug 2016 17:22:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7946 on The GeoJSON Format
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160811002208.4A3C0B80F6C@rfc-editor.org>
Date: Wed, 10 Aug 2016 17:22:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/V14nKgPPPaMFBscyZo_UvpTZang>
Cc: drafts-update-ref@iana.org, geojson@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2016 00:22:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7946

        Title:      The GeoJSON Format 
        Author:     H. Butler, M. Daly,
                    A. Doyle, S. Gillies,
                    S. Hagen, T. Schaub
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2016
        Mailbox:    howard@hobu.co, 
                    martin.daly@cadcorp.com, 
                    adoyle@intl-interfaces.com,
                    sean.gillies@gmail.com, 
                    stefan@hagen.link, 
                    tim.schaub@gmail.com
        Pages:      28
        Characters: 49143
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geojson-04.txt

        URL:        https://www.rfc-editor.org/info/rfc7946

        DOI:        http://dx.doi.org/10.17487/RFC7946

GeoJSON is a geospatial data interchange format based on JavaScript
Object Notation (JSON).  It defines several types of JSON objects and
the manner in which they are combined to represent data about
geographic features, their properties, and their spatial extents.
GeoJSON uses a geographic coordinate reference system, World Geodetic
System 1984, and units of decimal degrees.

This document is a product of the Geographic JSON Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC