Hi Harley, See: http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4 In SOLR-2155 you had to explicitly specify the prefix encoding length, whereas in Solr 4 you specify how much precision you need and it figures out what the length is that satisfies that. When you first use the field, it'll log what the derived levels figure is (if you care). The units are decimal degrees (0-180 from no distance to reverse side of the globe -- aka latitudinal degrees).
You can name the field type whatever you want, but I don't recommend "geohash" because this conflates it with an actual GeoHashField, and also it's more of an internal detail. You said you're having trouble with the migration... but what is the trouble? ~ David Harley wrote > I'm having trouble migrating the geohash fields from my Solr 3.4 schema > to the Solr 4 schema. > > this is the 3.4 type and class: > <fieldType name="geohash" class="solr2155.solr.schema.GeoHashField" > length="12"/> > is the below Solr 4 spatial type the right configuration to implement > data being stored in fields once using the "geohash" type and class in > the above solr 3.4 field type? > <fieldType name="geohash" > class="solr.SpatialRecursivePrefixTreeFieldType" > geo="true" distErrPct="0.025" maxDistErr="0.000009" units="degrees" > prefixTree="geohash" /> > is the units="degrees" degree decimal? example: 21.0345 > > > > Harley Powers Parks, GISP ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Migrate-Solr-3-4-w-solr-1255-GeoHash-to-Solr-4-tp4045416p4045470.html Sent from the Solr - User mailing list archive at Nabble.com.
