                                                                                                                                                                                                                                                                
Date: Wed, 10 Oct 2012 13:50:04 -0700 (PDT)
From: Nicholas Campion <camp...@gmail.com>
To: android-developers@googlegroups.com
Message-Id: <b8097ea6-a4e6-4f42-9e84-d7dd7663181f@googlegroups.com>
Subject: Strategy for Unknown Location
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_4_11396288.1349902204093"

------=_Part_4_11396288.1349902204093
Content-Type: multipart/alternative; 
	boundary="----=_Part_5_8727779.1349902204094"

------=_Part_5_8727779.1349902204094
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Obviously, Android apps sometimes don't know their location 
(lastKnownLocation returns null, etc.). Internally, we deal with this by 
checking if the app wide Location object is null and substituting -999 for 
latitude and longitude ... something that is obviously invalid so we can 
quickly spot it.

I'm wondering what other people do in this area. I looked at creating a Null 
Object Location <https://en.wikipedia.org/wiki/Null_Object_pattern> but got 
kinda worried by the two constructors for Locations that I might be barking 
up the wrong tree. Anyone have ideas on how to deal with creating a 
substitute location when the OS won't provide one?

------=_Part_5_8727779.1349902204094
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Obviously, Android apps sometimes don't know their location (lastKnownLocation returns null, etc.). Internally, we deal with this by checking if the app wide Location object is null and substituting -999 for latitude and longitude ... something that is obviously invalid so we can quickly spot it.<div><br></div><div>I'm wondering what other people do in this area. I looked at creating a&nbsp;<a href="https://en.wikipedia.org/wiki/Null_Object_pattern" style="cursor: pointer; ">Null Object Location</a>&nbsp;but got kinda worried by the two constructors for Locations that I might be barking up the wrong tree. Anyone have ideas on how to deal with creating a substitute location when the OS won't provide one?</div>
------=_Part_5_8727779.1349902204094--

------=_Part_4_11396288.1349902204093--