Putting latitudes and longitudes is one way. Putting just the address and geocoding it before displaying on map is another. The caveat with the latter approach is that geocoding everytime you retrieve data is costly. Since latitudes/longitudes associated with addresses do not change, it is best to store lat/lng in dB after geocoding the address at the time of inserting the entry in db.
On Mar 22, 4:48 pm, sunny <[email protected]> wrote: > in my project i need to take entries frm Db and show location on map > > is der any simpler approach den puttin latitude and longitude in table -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
