add locations next to POIs

[mfrasca]

From @mfrasca on February 15, 2018 14:22

POIs belong to locations and become visible at very deep zoom.
but how do you know where to find locations?
so I think we should add a location table, each location has coordinates and a zoom (to select the initial view), POIs must mention the location they belong to.

• while no location is selected:
  • all locations should be visible at any zoom (review reaction to onZoom #7)
• when a location is selected,
  • its zoom level and centre point are activated (recentre on chosen location #5) ✔️
  • its POIs are loaded into the app (recentre on chosen location #5) ✔️
  • POIs are visible at zoom 17 or deeper, (review reaction to onZoom #7) ✔️
  • locations are hidden at zoom 17 or deeper, (review reaction to onZoom #7) ✔️
  • all this information is in the asset database (initially hard coded, in perspective refresh list of gardens from server #3)
  • all this information can be downloaded from the central ghini.web server (refresh list of gardens from server #3)

Copied from original issue: Ghini/ghini.tour-audiowand_version#8

[mfrasca]

order of action is:

• hard code some location/poi in asset database
  • copy gardens from ghini.web ✔️
  • ask people if they're interested in contributing POIs, ✔️
  • in the meanwhile use Cuchubo and Tanager as examples,
• implement recentre on chosen location #5 ✔️
• correct review reaction to onZoom #7 ✔️
• con tiempo, sin prisa: refresh list of gardens from server #3.

meaning: it's just collecting/faking some data.

[mfrasca]

as far as this issue is concerned: done.
when we have some real data, we go on.