Hi, as per 
http://groups.google.com/group/android-challenge/browse_thread/thread/4412631fb4d5e285/27e9df98fd31c5c1#27e9df98fd31c5c1
, devs particpating the android-challenge aren't allowed to provide a
mock kml file and properties file (for LBS) or a mock geodb file for
geocoding.
As per the thread, judges will not be able to run "adb push" to push
the kml, properties or geodb files.

I have two questions for google.

1. It is possible that the challenge-rules are cast in stone, but I
figure it is worth asking anyway.
    Android just provides mock functionality now and the default
geocoder mock file just has 4 locations in it. All 4 point to the
White house,Washington DC.  The location provider does a loop in San
Francisco.
    Can you work with the challenge-rules people to support mock LBS
and geocoder files that are submitted by devs ?

2. The thread referenced above also suggests storing the geodb or kml/
properties files as raw resources and writing it to SD on first run.
    However, I'm not sure if the SD card suggestion is a viable
option.
    The LBS documentation specifically notes that mock providers
should go to /data/misc/location/<provider_name>. This directory is
inaccessible to Android applications at runtime.
    Can you please let us know if it is possible to create a mock
location provider and mock geocoding by writing properties/kml files
into the SD card ?

(If the answer to 1 is "no" and the answer to 2 is "no" or "very
expensive in terms of time", I'll probably work on hard-coding the
geodb data.)



--~--~---------~--~----~------------~-------~--~----~
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]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to