osmandapp/Osmand — pull request #781 by rilaby (2014-07-24 22:44:18+00:00)
Title: geo intent activit fixed

I've fixed the support for those geo data strings:
1) geo:0,0?q=34.99,-106.61(Treasure)
2) geo:0,0?z=11&q=34.99,-106.61(Treasure)
3) geo:0,0?q=1600+Amphitheatre+Parkway%2C+CA
4) geo:0,0?z=11&q=1600+Amphitheatre+Parkway%2C+CA

btw, the entry with geo location from google calendar is sending undecoded string ('Amphitheatre Parkway CA' but not 'Amphitheatre+Parkway%2C+CA'), than the street/city/coutry is split in two different tokens. That can be one of the reasons it could not find such the addresses. (but I didn't investigated the algorithm of finding the address yet)

All in all, it is better to figure out all the geo data strings and to rewrite net.osmand.plus.activities.search.GeoIntentActivity.extract(String, Uri) method.

Q:
1) What is "c:geo" protocol?
2) Is the project under tests? What is the approach? Is there a test for extract method?