Live data from Hacker News

Redis 3.2.0 is out

antirez.com

1–10 of 69 posts

Re: Redis 3.2.0 is out

#3
I like their new GEO sorted set with latitude and longitude. Can someone point me to a [reasonably priced] geocoding database to display nearest Town, Region (only where appropriate), Country (in English) based on latitude and longitude?

Re: Redis 3.2.0 is out

#4

The geo API seems rather... specific. Is there really a demand for it?

Back 5 years ago, this would have helped us at our company. We were doing realtime data analytics and we had to dump our data to Postgres to run any geo queries.

Re: Redis 3.2.0 is out

#5
post #3

I like their new GEO sorted set with latitude and longitude. Can someone point me to a [reasonably priced] geocoding database to display nearest Town, Region (only where appropriate), Country (in English) based on latitude and longitude?

I've used GeoNames (geonames.org) for a few projects.

Re: Redis 3.2.0 is out

#6

The geo API seems rather... specific. Is there really a demand for it?

If you think to geo-aware mobile applications, many are of the kind "show me XYZ near me". So that's the main use case basically. According to the fact a lot of people switched to 3.2 while it was yet not stable in order to use this feature I believe there is a big demand.

Re: Redis 3.2.0 is out

#7
post #3

I like their new GEO sorted set with latitude and longitude. Can someone point me to a [reasonably priced] geocoding database to display nearest Town, Region (only where appropriate), Country (in English) based on latitude and longitude?

I've used GeoNames (geonames.org) for a few projects.

I was turned off by their blurp that their US zip codes database contains only 21k zips out of 41.5k. Are they sufficiently complete for small towns?

Re: Redis 3.2.0 is out

#8

The geo API seems rather... specific. Is there really a demand for it?

Geo is insanely useful when you're after stuff within x miles of a known location - so a lot of mobile apps.

My problem with many existing geo implementations is they assume that a circular radius is the query type I care about, and longitude and latitude is sufficient to know where I actually am in terms of jurisdiction, etc.

Being able to add fine grained polygons to represent national, state, county or town boundaries and being able to identify the relationships between my co-ordinates and those entities is still far more complex than I would like.

Adding polygon support might be an interesting exercise, actually.

Re: Redis 3.2.0 is out

#9

The geo API seems rather... specific. Is there really a demand for it?

Geo is insanely useful when you're after stuff within x miles of a known location - so a lot of mobile apps. My problem with many existing geo implementations is they assume that a circular radius is the query type I care about, and longitude and latitude is sufficient to know where I actually am in terms of jurisdiction, etc. Being able to add fine grained polygons to represent national, state, county or town bounda…

Hey Paul, we have this feature added as a Lua script, but adding it in a native way could be interesting actually. Itamar Haber wrote the Lua script and was pushing for adding it in a native way, I wanted to check after the release the actual demand for it.
Post reply on HN