Georeferencing

[wkearn]

The main thing that makes geospatial data different from other kinds of data is georeferencing. Currently, RasterIO.jl just pulls the georeferencing information from GDAL and sticks it in the Raster type. This means it's rather hard to do anything useful with the geospatial information, and a Raster is just a glorified array carrying around some metadata.

We need to extract the geospatial data contained in a Raster so that it can be used by other packages down the pipeline.

[yeesian]

@garborg, is there a preferred way of representing projections that you'd like, for Geodesy.jl? GeoJSON.jl doesn't do very much with the coordinate reference systems too

[yeesian]

For future reference:

• https://github.com/aparo/django-nonrel/blob/master/django/contrib/gis/gdal/srs.py
• http://gis.stackexchange.com/questions/20298/is-it-possible-to-get-the-epsg-value-from-an-osr-spatialreference-class-using-th

[garborg]

@yeesian I've got a local branch with a Datum type, but it was basically inserted as a placeholder (just has an Ellipsoid and not other parameters usually needed for transformations). I'll try to wrap up other work on that branch enough to push it and post here when I do. I'm sure other people on the team have as much or more experience here, so hopefully we'll have some discussion around the design then.