Data.Geospatial.Internal.CRS

See Section 3 Coordinate Reference System Objects in the GeoJSON Spec

Types

data CRSObject

See Section 3 Coordinate Reference System Objects in the GeoJSON Spec NoCRS is required because no crs attribute in a GeoJSON feature is NOT the same thing as a null crs attribute. no crs value implies the default CRS, while a null CRS means you cannot assume a CRS, null will mapped to NoCRS while a non-existent attribute will be mapped to a Nothing Maybe value

Constructors

NoCRS

NamedCRS !Name

EPSG Code

LinkedCRS !Href !FormatString

Instances

Eq CRSObject

Defined in Data.Geospatial.Internal.CRS

Methods

(==) :: CRSObject -> CRSObject -> Bool

(/=) :: CRSObject -> CRSObject -> Bool

Show CRSObject

Defined in Data.Geospatial.Internal.CRS

Methods

showsPrec :: Int -> CRSObject -> ShowS

show :: CRSObject -> String

showList :: [CRSObject] -> ShowS

ToJSON CRSObject

encode CRS Objects to GeoJSON

Defined in Data.Geospatial.Internal.CRS

Methods

toJSON :: CRSObject -> Value

toEncoding :: CRSObject -> Encoding

toJSONList :: [CRSObject] -> Value

toEncodingList :: [CRSObject] -> Encoding

FromJSON CRSObject

decode CRS Objects from GeoJSON

Aeson doesnt decode "null" to Null unfortunately

Defined in Data.Geospatial.Internal.CRS

Methods

parseJSON :: Value -> Parser CRSObject

parseJSONList :: Value -> Parser [CRSObject]

Functions

defaultCRS :: CRSObject

The default CRS according to Section 3 Coordinate Reference System Objects is WGS84 which I believe, from http://spatialreference.org/ref/epsg/4326/ which translates to this in JSON: http://spatialreference.org/ref/epsg/4326/json/) is represented thus:

Prisms

_NoCRS :: Prism' CRSObject ()

_NamedCRS :: Prism' CRSObject Name

_EPSG :: Prism' CRSObject Code

_LinkedCRS :: Prism' CRSObject (Href, FormatString)