Changes between Initial Version and Version 2 of Ticket #562


Ignore:
Timestamp:
07/04/13 18:45:19 (7 years ago)
Author:
usul
Comment:

I understand you usecase. Currently it's a bit more complex, as we use this hierachies to speed up the search. So if we offer some kind of free-form search (what would useful, if you want tot look up POIs just by name etc, too), this needs some more refactoring in the background.

As this is related to usability and UX, I assign it to the 0.6 release that will have this in focus.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #562

    • Property Keywords address search usability added
    • Property Owner changed from cp15 to KaZeR
    • Property Component changed from gui/internal to core
    • Property Milestone changed from to version 0.6.0
  • Ticket #562 – Description

    initial v2  
    1 In certain areas one doesn't necessarily know what city a particular street actually lies in. In the San Francisco Bay Area for example there are dozens of small cities that are right next to each other. Where one town ends and the other begins is not obvious.
     1In certain areas one doesn't necessarily know what city a particular street actually lies in. In the [http://www.openstreetmap.org/?lat=37.743&lon=-122.125&zoom=10&layers=M San Francisco Bay Area] for example there are dozens of small cities that are right next to each other. Where one town ends and the other begins is not obvious.
    22
    33Given this scenario I might have to retype search names multiple times, changing the town name I think a street may lie in until I find the proper combination.