hmeme is obsolete
hgs can now allow for spaces in query entries
hgsp and hgss are based on hgs so i deleted them
hmse is based on hyema
hmssi is based on hysima
hmssu is based on hysuma
hmst is based on hytma
so I deleted hmse, hmssi hmssu and hmst , people can manipulate the hy- tables to extract what they need

hyfm is unchanged but it gives the latest message in a group
new table geo.geohash.neighbors
new table geo.geohash.neighbors
new table geo.geohash.neighbors
new table geo.geohash.neighbors
new table geo.geohash.neighbors
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
new table geo.geohash
adding feature to geo.geohash table to support latitude longitude pairs as input
embedding xml output of geo.geohash in <item/> to allow 'select geohash' statement in YQL
switching from geo.places to google.geocoding to support street addresses in Belgium
switching from geo.places to google.geocoding to support street addresses in Belgium
added 'use' statement for community table google.geocoding, otherwise the REST call won't work unless adding &env=store%3A%2F%2Fdatatables.org%2Falltableswithkeys