anchor.diff:  <<<
   == Jace JNI Proxies
   
  -Using Jace, we are able to create JNI proxy classes for GeoWave which can be used in C/C++ applications.
  -
  -=== Prepackaged RPM Setup
  -
  -Coming Soon...
  -
  -For a quick and easy setup, you can grab one of our prepackaged RPMs.
  -
  -
  -=== Manual Setup
  -
  -If you want to integrate with the latest version of GeoWave or perhaps a specific branch, you can build the Jace proxies yourself.
  -
  -==== Step 1 - Checkout GeoWave
  -
  -First, we need to clone GeoWave.
  -
  -[source, bash]
  -----
  +Using Jace, we are able to create JNI proxy classes for GeoWave which can be used in C/C++ applications.  
  +
  +Boost is required when using the Jace bindings.  
  +
  +=== Prepackaged Source and Binaries
  +
  +There is a public http://ngageoint.github.io/geowave/packages.html[GeoWave RPM Repo] where you can download a tarball for the GeoWave Jace bindings for your desired platform.  If your platform is not available, there is a source tarball which can be used in conjunction with CMake to build the GeoWave Jace bindings for your desired platform.  
  +
  +=== Generate Proxies and Build from Source
  +
  +If you want, you can generate and build the Jace proxies yourself.  
  +
  +==== Step 1 - Checkout Jace and GeoWave
  +
  +First, we need to clone Jace and GeoWave.
  +
  +[source, bash]
  +----
  +$ git clone git@github.com:jwomeara/jace.git
   $ git clone git@github.com:ngageoint/geowave.git
   ----
   
  -==== Step 2 - Build GeoWave
  -
  -In order to generate the Jace proxies, we need to build GeoWave using Maven.
  -
  -We will also specify two Maven profiles; one which specifies our target platform, and another to specify that we are building Jace proxies.
  +Note: We are using a non-standard Jace implementation.
  +
  +==== Step 2 - Install Jace
  +
  +First, we need to install Jace v1.3.0.  This is the software which is used to generate the C++ proxy classes.
  +
  +[source, bash]
  +----
  +$ cd jace
  +$ git checkout tags/v1.3.0
  +$ mvn clean install -Dsources
  +----
  +
  +==== Step 3 - Build GeoWave
  +
  +Here, we will specify two Maven profiles; one which specifies that we are building jace proxies, and another to specify our target platform.
   
   [source, bash]
   ----
  
positive.code: and manipulating point cloud data of various formats.  GeoWave is supported as a plugin for PDAL for both reading
  and writing data to Accumulo.  
  
  ==== Configure CMake for PDAL
  
  Using the manual process described above, you will have generated all of the required artifacts for running GeoWave as a PDAL plugin.  The artifacts can be found in the target folder within geowave-deploy.
  
  Now that the GeoWave plugin artifacts have been generated, we need to use CMake to configure PDAL to build with our plugin.
  
  To configure PDAL to run with GeoWave, there are a few CMake options which need to be configured.  While some of the options (namely the JAVA options) may configure automatically, some will need to be set manually.  Refer to the table below to get an idea for how these options would be configured using GeoWave v0.8.5 on Ubuntu 14.04 LTS.
  
  [cols="3*", options="header"]
  |===
  
negative.code: 
  [source, bash]
  ----
  $ export GEOWAVE_RUNTIME_JAR=/path/to/geowave/geowave-jace.jar
  $ export GEOWAVE_INGEST_JAR=/path/to/geowave/geowave-ingest.jar
  ----
  
  Note: The geowave-ingest jar included in the tarball only works for the geotools-vector format.
  
  === PDAL Plugin Configuration
  
  