Geophile cutover

- Added maven dependency on geophile.

- com.foundationdb.server.geophile has been mostly gutted, and
  replaced by com.foundationdb.server.spatial, which serves as glue to
  geophile. Due to this change, unit tests of
  com.foundationdb.server.spatial have been removed. (There are
  similar and more thorough tests in the open-source version.)

- Relying on geophile for Space and spatial objects.

- Changed the coordinate system. The obsolete, internal version of
  geophile used integer coordinates, scaled by 1e6, which was suitable
  for lat/lon spaces. The open-source version of geophile uses double
  coordinates.

- Modified estimated rows and costs in spatial ITs. By going to double
  coordinates, and avoiding the fixed 1e6 scaling, the z-values of
  spatial objects have changed, and cost estimates of z-order indexes
  change too.
Yes, I noticed that after I submitted. I have a revised comment in a new branch.

On Oct 9, 2014, at 2:44 PM, Mike McMahon <notifications@github.com> wrote:

> In src/main/java/com/foundationdb/server/spatial/Spatial.java:
> 
> > + * along with this program.  If not, see <http://www.gnu.org/licenses/>.
> > + */
> > +
> > +package com.foundationdb.server.spatial;
> > +
> > +import com.geophile.z.Space;
> > +import com.geophile.z.spatialobject.d2.Point;
> > +
> > +/*
> > +
> > +The lat/lon coordinate system is
> > +
> > +- latitude: -90 to +90
> > +- longitude: -180 to 180 with wraparound
> > +
> > +These coordinates are typically given in fixed-point columns, so the interface is in terms of BigDecimal.
> Does this comment need some updating? Or more discussion of how doubles are used?
> 
> —
> Reply to this email directly or view it on GitHub.
>