Status Update
Comments
il...@google.com <il...@google.com> #2
Thank you for posting.
For further checking, kindly provide the expected exact location/coordinate of the provided address Lot 19 1RN, Mosa, Middlesex, ON, CA
.
ap...@google.com <ap...@google.com> #3
the totally *irrelevant* responses that geocoder returns. Why does the
Maps application understand that Camden is a township in Kent county, but
the geocoder gives me CAMDEN, DELAWARE, USA! When I look for similar
locations in Michigan I always get a meaningful response. It does not
throw in a location with a similar name in FRANCE!
I am not fussy about the exact location/coordinates returned as long as it
is in the vicinity. If you choose to ignore leading parts that you do not
understand until you find something in your database that is meaningful,
fine by me. Why, when I have supplied both a valid township and county
name do you sometimes return only the County as a response. And sometimes
when I ask about a location in Canada the very first result is the STATE OF
CALIFORNIA!
The Google geocoder handles urban addresses, but not rural addresses.
Rural properties in both Canada and the United States are generally
identified by lot, concession, and township, like this example. In the
case of Mosa township street names and numeric addresses were only added
about 20 years ago in order to facilitate fire department service, because
these locations are serviced by the Canadian equivalent of RFD. 1st Range
North of Longwoods Road in Mosa township
<
Middlesex county, Ontario is such a concession. I have provided a link to
the record in my database that describes that concession. I believe that
you are entitled by the contract that I have for the use of your API to
copy any location and boundary information that I have added for a
location. I have even provided an alternative interface by which you can
obtain this information as a JSON document
tool is documented at
example to get all locations in my database that contain the string '1RN,
Mosa' ask for
I am not expecting you to return a perfect response. For example if
geocoder had returned your record for all of Mosa township, I would have
been happy. But instead in most cases with this sort of location I get
either the whole county, or the province of Ontario, or the STATE OF
CALIFORNIA!
The ideal response to my request for the specific location is
.
As I indicated I understand that you are entitled to copy any additional
information that I have accumulated using your geocoder and Maps
interfaces. It is fine with me if others benefit. There are almost 30,000
locations in my database.
On Mon, 18 Dec 2023 at 01:30, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
jb...@google.com <jb...@google.com> #4
island of South Uist, in the Outer Hebrides, which is administered as part
of the county of Invernessshire in Scotland. No matter what I entered into
geocoder it kept returning the the ENTIRE COUNTY OF INVERNESSSHIRE. This
is not a helpful response. I was forced to waste time looking up Bornish
south uist on Google Maps and then copy and paste the coordinates from the
URL. Please fix this!
On Mon, 18 Dec 2023 at 01:30, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
na...@google.com <na...@google.com> #5
Thank you for the information.
Please note that there are many reasons why Geocoding returns the incorrect/unexpected result like when the data is not available on our end or the data is problematic. This is why we are requesting users to provide additional information like the sample of the request where the issue is encountered with the expected correct result including the official source that can validate that it is correct.
Another reason for inaccurate results can be because of the request itself like when there are ambiguous or incorrect addresses. For this, kindly visit and check
Description
Component used: androidx.lifecycle.viewmodel
Version used: 2.5.0
Description:
Since lifecycle 2.5.0,
ViewModelProvider
createsViewModel
instance withViewModelFactory.create(modelClass, extra)
method if this method is implemented.In
ViewModelProvider.AndroidViewModelFactory
class case, it provides both ofcreate(modelClass, extra)
andcreate(modelClass)
, but it will always usecreate(modelClass, extra)
only.create(modelClass)
method is not used anymore if class is inherited fromViewModelProvider.AndroidViewModelFactory
,ViewModelProvider.AndroidViewModelFactory.create(modelClass)
create(modelClass)
method only instead ofcreate(modelClass, extra)
forViewModelProvider.AndroidViewModelFactory
class.