geojson: A thin GeoJSON Layer above the aeson library

[ bsd3, data, library ] [ Propose Tags ]

A thin GeoJSON Layer above the aeson library.

It currently conforms to version 1.0 of the GeoJSON spec which can be found here:

[Skip to Readme]
Versions [faq] 0.0.1, 0.0.2, 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 2.0.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4
Change log
Dependencies aeson (>=0.8), base (==4.*), containers (>=, deepseq (>=1.4), lens (>=4.11), scientific (>=0.2.0), semigroups (>=0.16), text (>=1.2), transformers (>=0.3), validation (>=1) [details]
License BSD-3-Clause
Copyright Copyright (C) 2013-2018
Author Dom De Re
Maintainer Andrew Newman
Category Data
Home page
Bug tracker
Source repo head: git clone
this: git clone 3.0.4)
Uploaded by newmana at Sat Oct 6 12:03:45 UTC 2018
Distributions LTSHaskell:3.0.4, NixOS:3.0.4, Stackage:3.0.4
Downloads 3646 total (85 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2018-10-06 [all 1 reports]


[Index] [Quick Jump]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for geojson-3.0.4

[back to package description]

geojson Build Status Hackage

A thin GeoJSON Layer above the aeson library

Building the project

Install the dependencies with:

cabal install --only-dependencies

Optionally add --enable-tests if you intend to run the unit tests

The project must be "configured" at least once everytime geojson.cabal changes, this can be done with:

cabal configure

If you wish to run the unit tests you will have to run:

cabal configure --enable-tests

Then finally build it with:

cabal build

See cabal build --help for more build options.

Running Unit Tests

After running cabal build, you can run the unit tests with the command:

cabal test

Development: Cabal Dependency Hell?

Cabal's great, but when you are developing a few different projects with their own dependency chains, sometimes installing all your libraries to the same place causes problems,

Consider trying cabal-dev. In terms of using it, all thats required is replacing cabal with cabal-dev in all the above command lines.

It will download and install all the dependencies for your project and install them in a cabal-dev/ directory in your project directory, and they will only be used for this project.

Those with newer versions of cabal (>= 1.18 I think) can skip cabal-dev and instead run cabal sandbox init, and just start runnign the above instructions as is from cabal install --only-dependencies