The day will never come that this will be picked up as a change, unless you go through the process of pushing this through into the Android code base yourself (Hint: ain't going to happen either) What I would do is to read the coords and string, determine if they fall within an existing range (i.e. on this planet) and contain a non null value, and go from there. Should be pretty straightforward.
On Dec 13, 4:21 am, "Jordan B." <[email protected]> wrote: > Hi, > > The LATITUDE and LONGITUDE fields of the Images Content Provider are > not filled in after taking a picture on my HTC Hero (I guess the HTC > Camera app does not do it). So I read the EXIF metadata of the file > and then update the database in order to save time the second time. > But I'm facing an issue since LATITUDE and LONGITUDE have two > states : > 1. Set with correct values > 2. Not set, returning default values ; 0 for getDouble, null for > getString > > It would be nice to have three states : > 1. Set with correct values > 2. Not set > 3. Something like "NO_GEO_TAG" with a value of 1000 for example (out > of the scope of possible values) > > Thus, we could differentiate between pictures with no GPS data, and > pictures that might have data in the exif but have not been updated in > the database. It would also be useful for pictures copied onto the > SDCard. > > What do you suggest ? -- 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
