ArbNation Join free

GIS basics for arborists: coordinates and the shapefile, GeoPackage and GeoJSON formats

A GIS ties data to a location. A shapefile is three linked files, a GeoPackage is one SQLite database, and GeoJSON is plain JSON in WGS 84 with longitude first.

Checked against the sources at the bottom of this page on October 21, 2026. Rules, fees and pay change: the source has the last word.

The U.S. Geological Survey, the Open Geospatial Consortium (OGC), the Internet Engineering Task Force (IETF) and Esri each publish a piece of the picture. The USGS defines a geographic information system. The other three publish the specifications for the shapefile, GeoPackage and GeoJSON formats that carry point and area data between systems.

What a GIS is

The USGS defines a geographic information system as a computer system that analyzes and displays geographically referenced information. It uses data attached to a unique location. The USGS notes that most information about the world carries a location reference, and its examples include where streamgages are and where all of a city's fire hydrants stand.

Its worked example combines several kinds of data. If a rare plant is seen in three places, GIS analysis might show all three on north-facing slopes above 1,000 feet that get more than ten inches of rain a year. The map can then show every location with similar conditions. Another USGS example joins the locations of farms using a specific fertilizer, stream locations, elevation and rainfall to show which streams are likely to carry that fertilizer downstream.

Flat maps and projections

The USGS defines a map projection as the method of portraying part of the spherical Earth on a flat surface, on paper or on a screen. No flat map can rival a globe, so every flat map misrepresents the surface in some way.

The USGS also records that its modern topographic maps are made from GIS data sets and distributed as PDF files for non-specialist users. It treats them as the output of a GIS, not the input, and adds that many GIS programs cannot read a PDF. GeoPDF files for historical, US Topo and OnDemand maps carry an attached XML metadata file.

Coordinates in GeoJSON

GeoJSON is defined in IETF RFC 7946, a Standards Track document of August 2016. It is a data interchange format based on JavaScript Object Notation (JSON) for geographic features, their properties and their spatial extents.

In GeoJSON a position is an array of numbers. The first two elements are longitude and latitude, or easting and northing, in that order, written as decimal numbers. An altitude or elevation can be added as an optional third element. The standard gives the coordinate reference system for all coordinates as the World Geodetic System 1984 (WGS 84) datum, in decimal degrees. It notes that the older 2008 version allowed other reference systems and that this one removed them. Altitude is the height in metres above or below the WGS 84 ellipsoid.

The RFC also fixes how polygons are wound. A linear ring is a closed line with four or more positions, the first and last identical. Exterior rings run counterclockwise and holes run clockwise, though parsers should not reject polygons that break the rule. The number of digits in a coordinate must not be read as a sign of how certain the position is.

Three formats compared

Three open formats for location data
FormatFormWhat it stores
ShapefileThree files with one name: .shp, .shx, .dbfPoints, lines and areas, with attributes in a dBASE table
GeoPackageOne SQLite database fileVector features, image and raster map tiles at several scales, extensions and non-spatial tables
GeoJSONOne JSON textGeometry, features and feature collections, in WGS 84

Shapefile

The Esri white paper of July 1998 defines the shapefile. A shapefile stores non-topological geometry and attribute information for the features in a data set. The geometry of a feature is a shape made of vector coordinates, and the format supports point, line and area features. Area features are closed-loop polygons.

The white paper says a shapefile consists of three files with the same prefix: the main file (.shp) holding the shapes, an index file (.shx), and a dBASE table (.dbf) holding the attributes. Each attribute record matches one shape record by record number, and the dBASE records must be in the same order as the main file. File names follow the 8.3 convention.

All the non-null shapes in one shapefile must be of the same shape type. The types include null, point, polyline, polygon and multipoint, each with variants that add elevation or a measure. The paper adds that data streams such as GPS receiver output can be stored as shapefiles or as X,Y event tables.

GeoPackage

OGC describes a GeoPackage as an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. The container is a SQLite database. The standard governs the tables, integrity rules, format limits and content constraints inside it.

Because it is a database, a GeoPackage supports direct use, so data can be read and updated in its native storage without translation. OGC adds that packages that comply with the standard and do not implement vendor-specific extensions are interoperable across all enterprise and personal computing environments, and that they are particularly useful on mobile devices with limited connectivity and bandwidth. The OGC page lists versions from 1.0 to 1.4.0, with 1.4.0 filed as document 12-128r19.

Sources