+1...
On Fri, Jun 7, 2013 at 7:32 AM, Joe White <[email protected]> wrote: > +1 as well. > Joe > On Jun 6, 2013, at 11:45 PM, "Mattmann, Chris A (398J)" < > [email protected]> wrote: > > > +1 to all bullets below. > > > > Cheers, > > Chris > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Chris Mattmann, Ph.D. > > Senior Computer Scientist > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 171-266B, Mailstop: 171-246 > > Email: [email protected] > > WWW: http://sunset.usc.edu/~mattmann/ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Adjunct Assistant Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > > > > > > > > -----Original Message----- > > From: Martin Desruisseaux <[email protected]> > > Organization: Geomatys > > Reply-To: "[email protected]" <[email protected]> > > Date: Thursday, June 6, 2013 12:05 PM > > To: Apache SIS <[email protected]> > > Subject: Proposal to move GeoHashUtils to org.apache.sis.index > > > >> Hello all > >> > >> Following on the move of QuadTree related classes to the > >> "org.apache.index.tree" package, I realized that GeoHashUtils could also > >> be seen as a kind of index. Would it be okay to do the following? > >> > >> * Move it to the "org.apache.sis.index" package. > >> * Move it from "sis-referencing" to "sis-storage" module, together > >> with QuadTree. > >> * Rename it as "GeoHashCoder" by analogy with the "geocoding" process > >> [1]. > >> * Make the methods non-static, for allowing configuration (precision, > >> 32 vs 36 bits variants) > >> > >> > >> Other ideas are welcome if "...sis.index" seems weird for that class. > >> > >> > >> Martin > >> > >> > >> [1] http://en.wikipedia.org/wiki/Geocoding > >> > > > >
