Changelog

1.2.1

2018 Jan 3

Fixes

1.2.0

2017 Nov 6

This release cycle saw a regular contributor Simeon Fitch elevated to official Committer status within GeoTrellis.

The team would like to thank him, along with our newest contributors Aaron Santos, Austin Heyne, Christos Charmatzis, Jessica Austin, and @mteldridge for helping make this release possible.

API Changes

  • geotrellis.raster
    • Deprecation: GridBounds.size in favor of GridBounds.sizeLong.
    • Deprecation: GridBounds.coords in favor of GridBounds.coordsIter.
    • New: GridBounds.offset and GridBounds.buffer for creating a modified GridBounds from an existing one.
    • New: ColorRamps.greyscale: Int => ColorRamp, which will generate a ramp when given some number of stops.
    • New: ConstantTile.fromBytes to create any type of ConstantTile from an Array[Byte].
    • New: Tile.rotate90: Int => Tile, Tile.flipVertical: Tile and Tile.flipHorizontal: Tile.
  • geotrellis.vector
    • New: Geometry.isEmpty: Boolean. This incurs much less overhead than previous ways of determining emptiness.
    • New: Line.head and Line.last for efficiently grabbing the first or last Point in the Line.
  • geotrellis.spark
    • Deprecation: The LayerUpdater trait hierarchy. Use LayerWriter.update or LayerWriter.overwrite instead.
    • Deprecation: Every cache provided by geotrellis.spark.util.cache. These will be removed in favor of a pluggable cache in 2.0.
    • New: SpatialKey.extent: LayoutDefinition => Extent
    • New: ValueReader.attributeStore: AttributeStore
    • New: TileLayerRDD.toSpatialReduce: ((V, V) => V) => TileLayerRDD[SpatialKey] for smarter folding of 3D tile layers into 2D tile layers.
    • The often-used apply method overloads in MapKeyTransform have been given more descriptive aliases.
  • geotrellis.vectortile (experimental)
    • New: VectorTile.toGeoJson and VectorTile.toIterable.
    • Library simplified by assuming the codec backend will always be Protobuf.

New Features

Finally, the full marriage of the vector, raster, and spark packages! You can now transform an RDD[Geometry] into a writable GeoTrellis layer of (SpatialKey, Tile)!

val geoms: RDD[Geometry] = ...
val celltype: CellType = ...
val layout: LayoutDefinition = ...
val value: Double = ...  /* Value to fill the intersecting pixels with */

val layer: RDD[(SpatialKey, Tile)] with Metadata[LayoutDefinition] =
  geoms.rasterize(value, celltype, layout)

In a similar vein to the above, you can now transform an arbitrarily large collection of Geometries into a proper GeoTrellis layer, where the sections of each Geometry are clipped to fit inside their enclosing Extents.

_images/cliptogrid.png

Here we can see a large Line being clipped into nine sublines. It’s one method call:

import geotrellis.spark._

val layout: LayoutDefinition = ...  /* The definition of your grid */
val geoms: RDD[Geometry] = ...      /* Result of some previous work */

/* There are likely many clipped Geometries per SpatialKey... */
val layer: RDD[(SpatialKey, Geometry)] = geoms.clipToGrid(layout)

/* ... so we can group them! */
val grouped: RDD[(SpatialKey, Iterable[Geometry])] = layer.groupByKey

If clipping on the Extent boundaries is not what you want, there are ways to customize this. See the ClipToGrid entry in our Scaladocs.

A Viewshed shows “visibility” from some set vantage point, given an Elevation raster. Prior to GeoTrellis 1.2 this was possible at the individual Tile level but not the Layer (RDD) level. Now it is.

First, we need to think about the Viewpoint type:

import geotrellis.spark.viewshed._

val point: Viewpoint(
  x = ...,                    // some coordinate.
  y = ...,                    // some coordinate.
  viewHeight = 4000,          // 4 kilometres above the surface.
  angle = Math.PI / 2,        // direction that the "camera" faces (in radians). 0 == east.
  fieldOfView = Math.PI / 2,  // angular width of the "view port".
  altitude = 0                // the height of points you're interested in seeing.
)

In other words:

  • x, y, viewHeight: where are we?
  • angle: what direction are we looking?
  • fieldOfView: how wide are we looking?
  • altitude: how high/low is the “target” of our viewing?

Given a Seq[Viewpoint] (the algorithm supports multiple simultaneous view points), we can do:

// Recall this common alias:
//   type TileLayerRDD[K] = RDD[(K, Tile)] with Metadata[TileLayerMetadata[K]]

val layer: TileLayerRDD[SpatialKey] = ...  /* Result of previous work */

val viewshed: TileLayerRDD[SpatialKey] = layer.viewshed(Seq(point))

We use Euclidean Distance to render a collection of points into a heatmap of proximities of some area. Say, of two roads crossing:

_images/euclid.png

Prior to GeoTrellis 1.2, this was possible at the individual Tile level but not the Layer (RDD) level. Now it is.

/* Result of previous work. Potentially millions of points per SpatialKey. */
val points: RDD[(SpatialKey, Array[Coordinate])] = ...
val layout: LayoutDefinition = ...  /* The definition of your grid */

val layer: RDD[(SpatialKey, Tile)] = points.euclideanDistance(layout)

The following was possible prior to GeoTrellis 1.2:

val layer: TileLayerRDD[SpatialKey] = ...
val polygon: Polgyon = ...

/* The maximum value within some Polygon overlaid on a Tile layer */
val summary: Double = layer.polygonalMaxDouble(polygon)

The above is also now possible for layers keyed by SpaceTimeKey to form a “time series”:

val layer: TileLayerRDD[SpaceTimeKey] = ...
val polygon: MultiPolygon = ...

/* The maximum value within some Polygonal area at each time slice */
val summary: Map[ZonedDateTime, Double] = layer.maxSeries(polygon)

A GeoTrellis ValueReader connects to some layer catalog and lets you read individual values (usually Tiles):

import geotrellis.spark.io.s3._

val store: AttributeStore = ...
val reader: Reader[SpatialKey, Tile] = S3ValueReader(store).reader(LayerId("my-catalog", 10))

val tile: Tile = reader.read(SpatialKey(10, 10))

However .reader is limited to zoom levels that actually exist for the given layer. Now you can use .overzoomingReader to go as deep as you like:

import geotrellis.raster.resample._

val reader: Reader[SpatialKey, Tile] =
  S3ValueReader(store).overzoomingReader(LayerId("my-catalog", 20), Average)

val tile: Tile = reader.read(SpatialKey(1000, 1000))

Have you ever wanted to “redraw” a grid over an established GeoTrellis layer? Say, this 16-tile Layer into a 4-tile one, both of 1024x1024 total pixels:

_images/regrid.png

Prior to GeoTrellis 1.2, there was no official way to do this. Now you can use .regrid:

/* The result of some previous work. Say each Tile is 256x256. */
val layer: TileLayerRDD[SpatialKey] = ...

/* "Recut" the tiles so that each one is now 512x512.
 * No pixels are gained or lost, save some NODATA on the bottom
 * and right edges that may appear for padding purposes.
 */
val regridded: TileLayerRDD[SpatialKey] = layer.regrid(512)

You can also regrid to non-rectangular sizes:

val regridded: TileLayerRDD[SpatialKey] = layer.regrid(tileCols = 100, tileRows = 300)

It’s common to find a subset of Tiles in a layer that are touched by some given Polygon:

val poly: Polygon = ???

val rdd: TileLayerRDD[SpatialKey] =
 layerReader
    .query[SpatialKey, Tile, TileLayerMetadata[SpatialKey]](Layer("name", zoom))
    .where(Intersects(poly))
    .result

Now you can perform this same operation with Line, MultiLine, and even (Polygon, CRS) to ensure that your Layer and Geometry always exist in the same projection.

Sometimes you just want to visualize a Tile without going through the song-and-dance of rendering it to a .png. The existing Tile.asciiDraw method kind of does that, except its output is all in numbers.

The new Tile.renderAscii: Palette => String method fulfills your heart’s desire:

import geotrellis.raster._
import geotrellis.raster.io.geotiff._
import geotrellis.raster.render.ascii._

val tile: Tile = SinglebandGeoTiff("path/to/tiff.tiff").tile

// println(tile.renderAscii())  // the default
println(tile.renderAscii(AsciiArtEncoder.Palette.STIPLED))
           ▚▖
           ▚▚▜▚▚
           ▚▖▚▜▚▖▚▚
          ▜▚▚▚▜▚█▚▜▚█▚
          █▚▜▖▜▖▚▚█▚▚▜▚█▖
          ▚▚█▚▜▚▚▚▚▚▚▚▜▚▚▚▚▚
         ▚▚▖▚▚▚▚▚█▜▚▚▜▚▚▖▚▖▚▖▚
         ▚▚▚▚█▚▚▚▚▚██▚▚▚▜▖▖██▚▚▜▚
         ▚▚█▚▚▚▚▚▚▚▜▚▚▚▚▚▚▜▚█▚▚▚▚▚▚▚
        █▚▚▖▚█▚▜▚▚▚▚▖▚▚▚▚▚▚▚▚▚▚▜▚▚▚▚▚▚▖
        █▚▚▚▜▚▖▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚██▖▜▚█▚▚▚
        █▚▚██▚▚▚▚▚▚▚▚▖▚▚▚▚▚▚▚▚█▚▚▚▚▚▚▖▖▖▚▚▚▚
       █▜▚▚██▜▚▚▚▜▖▚▚▜▚█▜▚▚▚▜▚▖▚▜▚█▚▚▖▚▚▖▚▚▖▖▚▚
       ▚▚█▚▚▚█▚██▚▚▚▚▚▚▚▚▜▚▚█▜▚▖█▚▚▚▜▚▚▚▚▚▚▜▚█▚█
       █▚▜▚▜▚█▚▜▚▚▜▚█▚▚▚▚▚▚▚▚▚▚▚▖▚▖▚▚▖▚█▚█▚▚▚▖█▚
       ████▚███▚▚▚▚██▚▚▚█▜▚▚▖▚▚▚▖▖▚▚▚▚▚▚▚▚█▚▜▖█
      ▖█▜▚█▚██▜▖▜▜█▜▜█▜▚▚▚▚▚█▖▚▚▚▚█▚▚▚▚▚▚▜▚▚█▖▜
      ▚▖██▚▜▚█▚▚▜▜█▜▜▜██▚▚▚▚█▚▚▚▜▖▚▚█▚▖▚▜▚▚▚▖▚█
      █▚▚▚▚▜▚██▖██▜▚▚█▚▚▖▚▚▜▚▖▚▖▚▚▚▚▚▖▚▚▖▖▖▚▖▚
     ▚▚▚█▚▚▚▚▚█▜▚▚████▚█▚▚▚█▚▖▚▚▚▖▚▚█▚▚▖▚▚▚▖▖▖
     ▚▚▚█▚▚▚▖▖▚▜█▜██▜██▚▚▖██▜▚▜▚█▚▚▚▚▚▚▚▚▖▖▜██
     ▚▚▚▚▜█▚▚▚▚▚█████▚▜██▚██▚▚▚▚▜▚▖▚█▚▚▖▚▖▚▚█
    ▚▚▜▚▚▚▚▜▚▜▚▚▚▚▜▚█▚▜█▚██▚██▚▚▚▚▖▚▚▚▚▖▖▚▚▖█
    ▚▜▚▜▚▚▚▚▚▚█▚▚▚▚▚██▜▜▜███▖▚▚▜█▚▚▖▚█▚▚█▚▖▚
    ▚▜▚▚▚▚▚▚▚▚▚▚▜▜▜▚▚▖▚▖▚▚▜▜██▜▚██▚▚▚▚▚▚▖▜█▚
   ▚▚▖▚▚█▚█▚▚▚█▚▖▚▚▚█▚▚▚▚▚▜██▚█▜▚█▚▜▚▚███▜█▜
   ▚▚▚▜▚▚▚▚▚▚▚▚▚▚▚▖█▚█▚▚▜█▜█▜█▜▚▖▚▚▚██▜▜█▚▜
   ▚▚▚▚▜▚▚▚▚▚▚▜▚▚▚▚▚▚▖▚█▜▖▖█▚▖▜▖▚▖█▚▖█▚▚▜▚█
   ▚▚█▚▚█▚▚▜▚▚▚▚▜▚▚▚▚▚▜▚▖▚█▜█▚▜▜▚█▖▜███▜▚▚
  ▚▚▚▚▚▚▖▜▚█▚▚▚▖▚▚▚▚▚▚▚▚▚▚▚▜█▖▜▜▜█▚▚▚▖▚█▚█
  ▜▚▚▚█▚▖▚█▚█▚▚█▚▚▚▚▚▚▚▖▚▚▚▜▚▚▚▜▚▖▚▖▚▚▚▚▜▚
  ▚▚▚▚▖▚█▖█▜▚▚▚▚▚▚▚▚▖▚▚▖▖█▚▜▚▖▚▚▚▚▖▖▚█▚▚▚
 ▚▚▚▚▚▚▚▚▚█▚▚▚▖▚▚▚█▚▜▚█▚▚▖▜██▚▖▚▚▚▚▚▚▚▚▚▖
 ▚▚▚▚▚▚▚▖▚▚██▚▚▚▚▚▚▚▚▜▚▚█▚██▚▚▚▚▖▚▚▖▚▚█▜▖
 ▚▚▚▚▚▚▚▚▚▚▚▚▚█▚▜▚▚▚▜▚▚▖▚▚▚▚▚▜▚▚▚▚▖▚▚▚▚▚
▚██▖▚▚▚▚▚▚▚▚▜▚▚█▚▚▚▚▜▚▚▚▚█▜▖▚▚█▜▜█▜█▚▖▚▖
▚▚▚▖▚▚█▚▚▜███▚▚▚▜▚▚▚▚▚█▚▖▖█▖▚████▜███▚██
▚█▚▚▚▚██▜▚▜▚▜▜▜█▜▚█▚▜▖▜▚▚▚█▚▜█▚▜▚▚▚▚▚▖▖
   █▜█▚▚▜▚▜▚▜▜▜▚▚▚▚██▖▖▖▚██▖█▚▜▜▚▚▚▚▚▚▖
      ▚█▜▜▜▜▜██▚▜▚▚▚▚▚▚▖▜▚▜▚▚▚▜▚█▚▚▖▖▖
         ██▚▚▚▚▚▚▚▜▚▜▖▚██▜▜▚▖▚▚█▚▚▚▖▜▜
            ▜▚▚▖▚▚▚▖▚▜▜██▜▜▚█▚▚▜▚▚▜██▚
               ▚▚█▚▜▚▚█▖▜▚▚▚▖█▚▚█▚▚█▚
                  █▜▜▚▚▜▜▚▚▚▜█▚▚▚▜█▜█
                     ▚▚▖▚█▖▚▖▜▚▖▚▖▜▚
                        ███▖██▚▖▚▚▚▚
                           ▜▚▚█▚▚▖▖█
                             ▚▖▜█▜▚
                                ▖█▚

Gorgious.

By adding some additional configuration, you can now use our HDFS Layer Backend to read and write GeoTrellis layers to Microsoft Azure’s blob storage.

It’s now possible to customize how our S3 backend communicates with S3.

GeoTrellis uses the Java Topology Suite for its vector processing. By default, JTS uses a “floating” PrecisionModel. When writing code that needs to be numerically robust, this default can lead to Topology Exceptions.

You can now use Typesafe Config to configure this to your application’s needs. See here for the specifics.

Features

Fixes

API Changes

While we are trying to stick strictly to SemVer, there are slight API changes in this release. We felt that while this does break SemVer in the strictest sense, the change were not enough to warrant a 2.0 release. Our hope is in the future to be more cognizant of API changes for future releases.

  • Made EPSG capatilization consistent in method names:

    • In geotrellis.proj4.CRS, changed getEPSGCode to getEpsgCode
    • In geotrellis.proj4.io.wkt.WKT, changed fromEPSGCode to fromEpsgCode and getEPSGCode to getEpsgCode
  • Changed some internal but publicly visible classes dealing with GeoTiff reading

    • Changed size to length in ArraySegmentBytes
    • Replaced foreach on SegmentBytes with getSegments, which the caller can iterate over themselves
    • Changed getDecompressedBytes to decompressGeoTiffSegment
  • Changed some interal but publicly visible implicit classes and read methods around TiffTagReader
    • Added as an implicit parameter to multiple locations, most publicly in TiffTagReader.read(byteReader: ByteReader, tagsStartPosition: Long)(implicit ttos: TiffTagOffsetSize). Also changed that method from being generic to always taking a Long offset.
  • Moved some misplaced implicit JsonFormats

    • Moved CellTypeFormat and CellSizeFormat from `` geotrellis.spark.etl.config.json`` in the spark-etl subproject to geotrellis.raster.io.json.Implicits in the raster subproject.
  • Changed LazyLogger from the com.typesafe.scalalogging version to our own version

    • This shouldn’t break any code, but technically is an API change.

1.0.0

Major Features

  • GeoTools support
    • Add Support for GeoTools SimpleFeature #1495
    • Conversions between GeoTools GridCoverage2D and GeoTrellis Raster types #1502
  • Streaming GeoTiff reading #1559
  • Windowed GeoTiff ingests into GeoTrellis layers, allowing users to ingest large GeoTiffs #1763
    • Reading TiffTags via MappedByteBuffer #1541
    • Cropped Windowed GeoTiff Reading #1559
    • Added documentation to the GeoTiff* files #1560
    • Windowed GeoTiff Docs #1616
  • GeoWave Raster/Vector support (experimental)
    • Create GeoWave Subproject #1542
    • Add vector capabilities to GeoWave support #1581
    • Fix GeoWave Tests #1665
  • GeoMesa Vector support (experimental)
    • Create GeoMesa suproject #1621
  • Moved to a JSON-configuration ETL process
    • ETL Refactor #1553
    • ETL Improvements and other issues fixes #1647
  • Vector Tile reading and writing, file-based and as GeoTrellis layers in RDDs. #1622
  • File Backends
  • Collections API #1606
    • Collections polygonal summary functions #1614
    • Collections mapalgebra focal functions #1619
  • Add TileFeature Type #1429
  • Added Focal calculation target type #1601
  • Triangulation
    • Voronoi diagrams and Delaunay triangulations #1545, #1699
    • Conforming Delaunay Triangulation #1848
  • Euclidean distance tiles #1552
  • Spark, Scala and Java version version support
    • Move to Spark 2; Scala 2.10 deprecation #1628
    • Java 7 deprecation #1640
  • Color correction features:
    • Histogram Equalization #1668
    • Sigmoidal Contrast #1681
    • Histogram matching #1769
  • CollectNeighbors feature, allowing users to group arbitrary values by the neighbor keys according to their SpatialComponent #1860
  • Documentation: We moved to ReadTheDocs, and put a lot of work into making our docs significantly better. See them here.

Minor Additions

  • Documentation improvements
    • Quickstart
    • Examples
      • Added example for translating from SpaceTimeKey to SpatialKey #1549
      • doc-examples subproject; example for tiling to GeoTiff #1564
      • Added example for focal operation on multiband layer. #1577
      • Projections, Extents, and Layout Definitions doc #1608
      • Added example of turning a list of features into GeoJson #1609
      • Example: ShardingKeyIndex[K] #1633
      • Example: VoxelKey #1639
  • Introduce ADR concept
    • ADR: HDFS Raster Layers #1582
    • [ADR] Readers / Writers Multithreading #1613
  • Fixes
    • Fixed some markdown docs #1625
    • parseGeoJson lives in geotrellis.vector.io #1649
  • Parallelize reads for S3, File, and Cassandra backends #1607
  • Kernel Density in Spark
  • k-Nearest Neighbors
  • Updated slick
  • Added GeoTiff read/write support of TIFFTAG_PHOTOMETRIC via GeoTiffOptions. #1667
  • Added ability to read/write color tables for GeoTIFFs encoded with palette photometric interpretation #1802
  • Added ColorMap to String conversion #1512
  • Add split by cols/rows to SplitMethods #1538
  • Improved HDFS support #1556
  • Added Vector Join operation for Spark #1610
  • Added Histograms Over Fractions of RDDs of Tiles #1692
  • Add interpretAs and withNoData methods to Tile #1702
  • Changed GeoTiff reader to handle BigTiff #1753
  • Added BreakMap for reclassification based on range values. #1760
  • Allow custom save actions on ETL #1764
  • Multiband histogram methods #1784
  • DelayedConvert feature, allowing users to delay conversions on tiles until a map or combine operation, so that tiles are not iterated over unnecessarily #1797
  • Add convenience overloads to GeoTiff companion object #1840

Fixes / Optimizations

  • Fixed GeoTiff bug in reading NoData value if len = 4 #1490
  • Add detail to avro exception message #1505
  • Fix: The toSpatial Method gives metadata of type TileLayerMetadata[SpaceTimeKey]
    • Custom Functor Typeclass #1643
  • Allow Intersects(polygon: Polygon) in layer query #1644
  • Optimize ColorMap #1648
  • Make regex for s3 URLs handle s3/s3a/s3n #1652
  • Fixed metadata handling on surface calculation for tile layer RDDs #1684
  • Fixed reading GeoJson with 3d values #1704
  • Fix to Bicubic Interpolation #1708
  • Fixed: Band tags with values of length > 31 have additional white space added to them #1756
  • Fixed NoData bug in tile merging logic #1793
  • Fixed Non-Point Pixel + Partial Cell Rasterizer Bug #1804

New Committers

  • metasim
  • lokifacio
  • aeffrig
  • jpolchlo
  • jbouffard
  • vsimko
  • longcmu
  • miafg

0.10.3

  • PR #1611 Any RDD of Tiles can utilize Polygonal Summary methods. (@fosskers)
  • PR #1573 New foreach for MultibandTile which maps over each band at once. (@hjaekel)
  • PR #1600 New mapBands method to map more cleanly over the bands of a MultibandTile.

0.10.2

  • PR #1561 Fix to polygon sequence union, account that it can result in NoResult. (1)
  • PR #1585 Removed warnings; add proper subtyping to GetComponent and SetComponent identity implicits; fix jai travis breakage. (1)
  • PR #1569 Moved RDDLayoutMergeMethods functionality to object. (1)
  • PR #1494 Add ETL option to specify upper zoom limit for raster layer ingestion (@mbertrand)
  • PR #1571 Fix scallop upgrade issue in spark-etl (@pomadchin)
  • PR #1543 Fix to Hadoop LayerMover (@pomadchin)

Special thanks to new contributor @mbertrand!

0.10.1

  • PR #1451 Optimize reading from compressed Bit geotiffs (@shiraeeshi)
  • PR #1454 Fix issues with IDW interpolation (@lokifacio)
  • PR #1457 Store FastMapHistogram counts as longs (@jpolchlo)
  • PR #1460 Fixes to user defined float/double CellType parsing (@echeipesh)
  • PR #1461 Pass resampling method argument to merge in CutTiles (1)
  • PR #1466 Handle Special Characters in proj4j (@jamesmcclain)
  • PR #1468 Fix nodata values in codecs (@shiraeeshi)
  • PR #1472 Fix typo in MultibandIngest.scala (@timothymschier)
  • PR #1478 Fix month and year calculations (@shiraeeshi)
  • PR #1483 Fix Rasterizer Bug (@jamesmcclain)
  • PR #1485 Upgrade dependencies as part of our LocationTech CQ process (1)
  • PR #1487 Handle entire layers of NODATA (@fosskers)
  • PR #1493 Added support for int32raw cell types in CellType.fromString (@jpolchlo)
  • PR #1496 Update slick (@adamkozuch, @moradology)
  • PR #1498 Add ability to specify number of streaming buckets (@moradology)
  • PR #1500 Add logic to ensure use of minval/avoid repetition of breaks (@moradology)
  • PR #1501 SparkContext temporal GeoTiff format args (@echeipesh)
  • PR #1510 Remove dep on cellType when specifying layoutExtent (@fosskers)
  • PR #1529 LayerUpdater fix (@pomadchin)

Special thanks to new contributors @fosskers, @adamkozuch, @jpolchlo, @shiraeeshi, @lokifacio!

0.10.0

The long awaited GeoTrellis 0.10 release is here!

It’s been a while since the 0.9 release of GeoTrellis, and there are many significant changes and improvements in this release. GeoTrellis has become an expansive suite of modular components that aide users in the building of geospatial application in Scala, and as always we’ve focused specifically on high performance and distributed computing. This is the first official release that supports working with Apache Spark, and we are very pleased with the results that have come out of the decision to support Spark as our main distributed processing engine. Those of you who have been tuned in for a while know we started with a custom built processing engine based on Akka actors; this original execution engine still exists in 0.10 but is in a deprecated state in the geotrellis-engine subproject. Along with upgrading GeoTrellis to support Spark and handle arbitrarily-sized raster data sets, we’ve been making improvements and additions to core functionality, including adding vector and projection support.

It’s been long enough that release notes, stating what has changed since 0.9, would be quite unwieldy. Instead I put together a list of features that GeoTrellis 0.10 supports. This is included in the README on the GeoTrellis Github, but I will put them here as well. It is organized by subproject, with more basic and core subprojects higher in the list, and the subprojects that rely on that core functionality later in the list, along with a high level description of each subproject.

geotrellis-proj4

  • Represent a Coordinate Reference System (CRS) based on Ellipsoid, Datum, and Projection.
  • Translate CRSs to and from proj4 string representations.
  • Lookup CRS’s based on EPSG and other codes.
  • Transform (x, y) coordinates from one CRS to another.

geotrellis-vector

  • Provides a scala idiomatic wrapper around JTS types: Point, Line (LineString in JTS), Polygon, MultiPoint, MultiLine (MultiLineString in JTS), MultiPolygon, GeometryCollection
  • Methods for geometric operations supported in JTS, with results that provide a type-safe way to match over possible results of geometries.
  • Provides a Feature type that is the composition of a geometry and a generic data type.
  • Read and write geometries and features to and from GeoJSON.
  • Read and write geometries to and from WKT and WKB.
  • Reproject geometries between two CRSs.
  • Geometric operations: Convex Hull, Densification, Simplification
  • Perform Kriging interpolation on point values.
  • Perform affine transformations of geometries

geotrellis-vector-testkit

  • GeometryBuilder for building test geometries
  • GeometryMatcher for scalatest unit tests, which aides in testing equality in geometries with an optional threshold.

geotrellis-raster

  • Provides types to represent single- and multi-band rasters, supporting Bit, Byte, UByte, Short, UShort, Int, Float, and Double data, with either a constant NoData value (which improves performance) or a user defined NoData value.
  • Treat a tile as a collection of values, by calling “map” and “foreach”, along with floating point valued versions of those methods (separated out for performance).
  • Combine raster data in generic ways.
  • Render rasters via color ramps and color maps to PNG and JPG images.
  • Read GeoTiffs with DEFLATE, LZW, and PackBits compression, including horizontal and floating point prediction for LZW and DEFLATE.
  • Write GeoTiffs with DEFLATE or no compression.
  • Reproject rasters from one CRS to another.
  • Resample of raster data.
  • Mask and Crop rasters.
  • Split rasters into smaller tiles, and stitch tiles into larger rasters.
  • Derive histograms from rasters in order to represent the distribution of values and create quantile breaks.
  • Local Map Algebra operations: Abs, Acos, Add, And, Asin, Atan, Atan2, Ceil, Cos, Cosh, Defined, Divide, Equal, Floor, Greater, GreaterOrEqual, InverseMask, Less, LessOrEqual, Log, Majority, Mask, Max, MaxN, Mean, Min, MinN, Minority, Multiply, Negate, Not, Or, Pow, Round, Sin, Sinh, Sqrt, Subtract, Tan, Tanh, Undefined, Unequal, Variance, Variety, Xor, If
  • Focal Map Algebra operations: Hillshade, Aspect, Slope, Convolve, Conway’s Game of Life, Max, Mean, Median, Mode, Min, MoransI, StandardDeviation, Sum
  • Zonal Map Algebra operations: ZonalHistogram, ZonalPercentage
  • Operations that summarize raster data intersecting polygons: Min, Mean, Max, Sum.
  • Cost distance operation based on a set of starting points and a friction raster.
  • Hydrology operations: Accumulation, Fill, and FlowDirection.
  • Rasterization of geometries and the ability to iterate over cell values covered by geometries.
  • Vectorization of raster data.
  • Kriging Interpolation of point data into rasters.
  • Viewshed operation.
  • RegionGroup operation.

geotrellis-raster-testkit

  • Build test raster data.
  • Assert raster data matches Array data or other rasters in scalatest.

geotrellis-spark

  • Generic way to represent key value RDDs as layers, where the key represents a coordinate in space based on some uniform grid layout, optionally with a temporal component.
  • Represent spatial or spatiotemporal raster data as an RDD of raster tiles.
  • Generic architecture for saving/loading layers RDD data and metadata to/from various backends, using Spark’s IO API with Space Filling Curve indexing to optimize storage retrieval (support for Hilbert curve and Z order curve SFCs). HDFS and local file system are supported backends by default, S3 and Accumulo are supported backends by the geotrellis-s3 and geotrellis-accumulo projects, respectively.
  • Query architecture that allows for simple querying of layer data by spatial or spatiotemporal bounds.
  • Perform map algebra operations on layers of raster data, including all supported Map Algebra operations mentioned in the geotrellis-raster feature list.
  • Perform seamless reprojection on raster layers, using neighboring tile information in the reprojection to avoid unwanted NoData cells.
  • Pyramid up layers through zoom levels using various resampling methods.
  • Types to reason about tiled raster layouts in various CRS’s and schemes.
  • Perform operations on raster RDD layers: crop, filter, join, mask, merge, partition, pyramid, render, resample, split, stitch, and tile.
  • Polygonal summary over raster layers: Min, Mean, Max, Sum.
  • Save spatially keyed RDDs of byte arrays to z/x/y files into HDFS or the local file system. Useful for saving PNGs off for use as map layers in web maps or for accessing GeoTiffs through z/x/y tile coordinates.
  • Utilities around creating spark contexts for applications using GeoTrellis, including a Kryo registrator that registers most types.

geotrellis-spark-testkit

  • Utility code to create test RDDs of raster data.
  • Matching methods to test equality of RDDs of raster data in scalatest unit tests.

geotrellis-accumulo

  • Save and load layers to and from Accumulo. Query large layers efficiently using the layer query API.

geotrellis-cassandra

Save and load layers to and from Casandra. Query large layers efficiently using the layer query API.

geotrellis-s3

  • Save/load raster layers to/from the local filesystem or HDFS using Spark’s IO API.
  • Save spatially keyed RDDs of byte arrays to z/x/y files in S3. Useful for saving PNGs off for use as map layers in web maps.

geotrellis-etl

  • Parse command line options for input and output of ETL (Extract, Transform, and Load) applications
  • Utility methods that make ETL applications easier for the user to build.
  • Work with input rasters from the local file system, HDFS, or S3
  • Reproject input rasters using a per-tile reproject or a seamless reprojection that takes into account neighboring tiles.
  • Transform input rasters into layers based on a ZXY layout scheme
  • Save layers into Accumulo, S3, HDFS or the local file system.

geotrellis-shapefile

  • Read geometry and feature data from shapefiles into GeoTrellis types using GeoTools.

geotrellis-slick

  • Save and load geometry and feature data to and from PostGIS using the slick scala database library.
  • Perform PostGIS ST_ operations in PostGIS through scala.