search

geigercrowd / geigercrowd_on_rails

crowd-sourcing radiation sensor data
http://www.geigercrowd.net
19 stars 7 forks source link

RFC: Locations data #8

Closed nullisnil closed 13 years ago

nullisnil commented 13 years ago

Locations data has now:

t.string   "name"
t.float    "latitude"
t.float    "longitude"
t.integer  "user_id"

The data on geonames looks like:

  t.string :country_code
  t.string :postal_code
  t.string :name
  t.string :admin_name_1
  t.string :admin_code_1
  t.string :admin_name_2
  t.string :admin_code_2
  t.string :admin_name_3
  t.string :admin_code_3
  t.float :latitude
  t.float :longitude
  t.integer :accuracy

Any reasons why to drop the data?

ruebezahl commented 13 years ago

hmm.. the names now are user-generated like "my office", "park in front of my flat" or smth. like this. i think this is more user-friendy, and if we really do need country-code and postal code, we still could do a geonames lookup based on lat and lon.

but i'm not sure... any further comments?

nullisnil commented 13 years ago

misunderstanding :)

ruebezahl commented 13 years ago

okay, after short discussion:

user enters location: * uses a map (google maps, openstreetmap) to figure out exact coordinates * enters coordinates and a user-chosen name (like "office") * submits form

anonymous web user does data-lookup: * enters search criteria ("within 30km near $name") * system does a geonames lookup and verifies with user * system selects dataset based on coordinates

ruebezahl commented 13 years ago

see also:

http://en.wikipedia.org/wiki/Wikipedia:Obtaining_geographic_coordinates and http://tools.freeside.sk/geolocator/geolocator.html

tsujigiri commented 13 years ago

I would go with ruebezahl's suggestion.

nullisnil commented 13 years ago

This question was caused by not knowing the thoughts of ruebezahl. After a chat in IRC the comment "Misunderstanding" was created.

It looks like the tickets get reopened when someone submits a new comment.