maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Not able to open Maps application with contacts location as a search string|
|Product:||[Maemo Official Applications] Contacts||Reporter:||David Hagood <david.hagood>|
|Status:||RESOLVED FIXED||QA Contact:||contacts-bugs|
|Priority:||High||CC:||andrew, andre_klapper, ark, javierjc1982, joppu1, jorgen.scheibengruber, loek.engels, mikhail.zabaluev|
|Bug Depends on:||1979, 3269|
Use case: User has multiple contacts in the Evolution database (Contacts app). User wishes to associate one or more physical locations with a contact (e.g. home, business), and have those addresses show up in the Map application as points of interest. This requires both the addition of all the fields EDS supports (bug #1979) as well as some way to tie that into the Wayfinder application. Even better would be if one device could notify another about its location (e.g. by using Jabber over an IM system).
*** This bug has been confirmed by popular vote. ***
Still valid in 4.1.3 (5.2008.43-7) maemo release
This seems more like a Contacts code issue than a Maps issue currently. Moving. Still valid in latest Fremantle.
*** Bug 5080 has been marked as a duplicate of this bug. ***
It's worth noting that in Fremantle, the Contacts app *does* support all these extra fields; it's just that "Address" isn't as integrated as "Birthday", "Email", "SMS", "Web page", "Phone" etc. See description on #5080.
Is there a standard URI scheme for geographical locations? We could think about contacts opening a URL handler which could be a third-party application as well.
(In reply to comment #6) > Is there a standard URI scheme for geographical locations? We could think about > contacts opening a URL handler which could be a third-party application as > well. From http://geouri.org/, I found http://tools.ietf.org/html/draft-mayrhofer-geopriv-geo-uri-01 - however this is limited to longitude, lattitude and (optionally) altitude. So it'd still need to use the existing Maps to handle the translation of street, city, zip code & country to those coords. Perhaps an "open address" D-Bus service would be sufficient, also keeps it open for third party implementations.
Quoting pierlux here: <pierlux> you should create somewhat a standard, here are some guide lines: <pierlux> after I searched for how addresses are displayed in the world, the only thing we can assume is that we don't agree on the information position: <pierlux> Japan likes the postal code first, North ameica last, Europe before the city name <pierlux> it might be preferable to pass each fields separately
(In reply to comment #7) > Perhaps an "open address" D-Bus service would be sufficient, also keeps it open > for third party implementations. That's definitely a taller order. Maybe Tracker and its ontologically-organized data model could help us here, but it's not for Fremantle.
*** Bug 3090 has been marked as a duplicate of this bug. ***
*** Bug 6520 has been marked as a duplicate of this bug. ***
Aligning this report with the internal one in bugzilla. At least the aim is to provide this in Fremantle.
*** Bug 7311 has been marked as a duplicate of this bug. ***
This has been fixed in package libosso-abook 4.20100129.2+0m5 which is part of the internal build version 10.2010.05-10 (Note: 2009/2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).
(In reply to comment #16) > Setting explicit PR1.2 milestone (so it's clearer in which public release the > fix will be available to users). > > Sorry for the bugmail noise (you can filter on this message). > ..and it it does not work in PR1.2. Map application is called, but it shows the same location in the city for all contacts. Perhaps i should open a separate bug for that?