Status Update
Comments
an...@google.com <an...@google.com>
[Deleted User] <[Deleted User]> #2
Can you please test with latest library and update result here.
If possible please provide a complete sample application.
Expected output
What do you expect to occur?
Current output
What do you see instead?
de...@yahoo.com <de...@yahoo.com> #3
su...@google.com <su...@google.com>
sa...@gmail.com <sa...@gmail.com> #4
Sample project is attached.
Steps to test:
1. Import, build and install apk
2. Notice "Number of 'onLoadFinished' calls: 1"
3. Click "Click me!" button to start Second Activity
4. Notice "Number of 'onLoadFinished' calls: 2"
EXPECTED: At stap 4 "Number of 'onLoadFinished' calls" should be 1.
ACTUAL: It's 2.
@ha...@gmail.com
That's not the solution because developers are not in control of all Loaders. For example CursorLoader from support libaray should be then fixed by google, not by developers.
And this is behavior change which is not documented, so suggestion on issuetracker is not good enough.
mi...@gmail.com <mi...@gmail.com> #5
ma...@gmail.com <ma...@gmail.com> #6
lo...@gmail.com <lo...@gmail.com> #7
Try this solution I've written about (read the last part of the text too, as it talks about the changes) :
kf...@kfei.net <kf...@kfei.net> #8
ra...@gmail.com <ra...@gmail.com> #9
Attached sample project, that "loads" content, and after 5 seconds returns a result, that will be returned on the current Activity.
el...@gmail.com <el...@gmail.com> #10
fo...@google.com <fo...@google.com>
ke...@flowmo.co <ke...@flowmo.co> #11
de...@gmail.com <de...@gmail.com> #12
The reason is that after you load something, you wish to use it. After orientation change, all is destroyed, but the result is still available, so you can use it.
If you don't want to use the result, either ignore it, or check whether the loader (if existing) has a result or not.
But this loses the whole point of using a loader. By using a loader, you are supposed to use its result, even after an orientation change.
jo...@gmail.com <jo...@gmail.com> #13
jo...@gmail.com <jo...@gmail.com> #14
Obscurity provides NO security.
wi...@gmail.com <wi...@gmail.com> #15
[Deleted User] <[Deleted User]> #16
(need in Java API)
zw...@google.com <zw...@google.com> #17
Given that currently after the signed in deprecation we lack a way to identify users, we will not be able to share user information, e.g. shared devices from a user.
da...@thewhytehouse.org <da...@thewhytehouse.org> #18
It isn't official and I guess prone to breakages, but provides a method for getting shared location data.
de...@yahoo.com <de...@yahoo.com> #19
You could also incorporate a way in which the user will share his position without telling who he is and for a short period of time. More or less the way you do it now with a hashed URI.
zw...@google.com <zw...@google.com> #20
We have a tutorial:
which shows how you can manage location data between devices, and have them expire over time. HTML5 has an geolocation API:
Perhaps combining these two will give you the ability for a solution for now.
jo...@gmail.com <jo...@gmail.com> #21
za...@gmail.com <za...@gmail.com> #22
I would love to have API access to my shared location via google. This will also be a great feature for tracking apps on android. Cause now only google maps has to send location updates vs several apps doing the same thing.
fv...@google.com <fv...@google.com>
ph...@gmail.com <ph...@gmail.com> #23
[Deleted User] <[Deleted User]> #24
sl...@gmail.com <sl...@gmail.com> #25
[Deleted User] <[Deleted User]> #26
In that case there would not be necessary to implement any fancy authentication.
an...@gmail.com <an...@gmail.com> #27
ya...@gmail.com <ya...@gmail.com> #28
ru...@gmail.com <ru...@gmail.com> #29
ci...@gmail.com <ci...@gmail.com> #30
na...@gmail.com <na...@gmail.com> #31
rv...@gmail.com <rv...@gmail.com> #32
jm...@gmail.com <jm...@gmail.com> #33
si...@gmail.com <si...@gmail.com> #34
I want to implement that running locally could be able to get input from my google home mini, send it to a local server that push a response to the google home...
"Ok google, where is [name]?"
google home send the request to a local server (nodered?), request the person location (if shared, via the missed API), send the response back to google home that speak it.
Please.. location api!!!
ma...@gmail.com <ma...@gmail.com> #35
we...@gmail.com <we...@gmail.com> #36
kr...@gmail.com <kr...@gmail.com> #37
ma...@gmail.com <ma...@gmail.com> #38
lw...@googlemail.com <lw...@googlemail.com> #39
su...@gmail.com <su...@gmail.com> #40
li...@seznam.cz <li...@seznam.cz> #41
ma...@gmail.com <ma...@gmail.com> #42
sk...@gmail.com <sk...@gmail.com> #43
sa...@gmail.com <sa...@gmail.com> #44
fa...@gmail.com <fa...@gmail.com> #45
sb...@gmail.com <sb...@gmail.com> #46
pa...@gmail.com <pa...@gmail.com> #47
an...@google.com <an...@google.com> #48
We do really value your comments to help us investigate these requests, and the most helpful kind of comment is one where you tell us why exactly you are requesting a feature. i.e.
1) What problem you're trying to solve
2) How this feature would help you solve it
(no more +1 guys... they're honestly pointless, and just prove you can't read... and they're annoying)
jo...@hotmail.nl <jo...@hotmail.nl> #49
mj...@gmail.com <mj...@gmail.com> #50
pf...@gmail.com <pf...@gmail.com> #51
cr...@gmail.com <cr...@gmail.com> #52
ca...@gmail.com <ca...@gmail.com> #53
na...@gmail.com <na...@gmail.com> #54
I have actually tried an implementation (
I think similar implementation in google maps would be an also very useful feature. e.g. sending me push notification when a family member leaves home or getting close to a location e.g they will be home in 5 minutes.
I hope you guys consider implementing it, or at least make an official api available.
Thank you!
er...@gmail.com <er...@gmail.com> #55
ev...@gmail.com <ev...@gmail.com> #56
an...@google.com <an...@google.com>
mr...@gmail.com <mr...@gmail.com> #57
ma...@gmail.com <ma...@gmail.com> #58
an...@gmail.com <an...@gmail.com> #59
Have a Home automation system that residents can share their location with. The home automation system must have a separate google account, so it can be found by the residents as a separate user, plus it can send out and receive mails to the residents. A resident has the initiative to share their location, and can stop sharing the location with the system at any time. The home automation system must have a means to iterate the residents sharing their location with it, to enable it to generate a list of all residents sharing. The home automation system gets a push notification when a resident's location changes "significantly" (*). When a residents' shared location changes, the new location is compared to the home automation's location (which is most likely static, but could be retrieved through f.e. gps). The home automation system then has following uses for the location data:
- if the resident is less than x meters away from the home automation system's location, this resident is reported 'at home', when the resident is less than y kilometers away, he is reported as 'in the neighborhood' and otherwise he is reported 'away'. So multiple rings around the home location can be defined for different applications: the lights can be turned of when all residents are outside of the house, but turning the heating from comfort into eco-mode is only lucrative when all residents are likely not to return soon, i.e. are more than several kilometers away from home.
- if a resident's status changes, appropriate action(s) are taken: for example: heating is switched on or off, lights are switched on or off or the coffee maker is started or whatever the resident needs. Actions may be also be triggered when the last resident leaves the house, or when the first resident comes home. Most home automation systems should be able to implement this grouping themselves, however the API must deliver notifications to support tracking individual residents, if it can also support notification on group level, like 'first resident entered', 'last resident left', that is an added bonus.
- an address nearby the resident's location is shown in a dashboard. This can be used to see teh location of each resident (very helpfull when you have kids that forget to mention they go out to play at a friend's)
(*) When a location change is significant is preferably configurable: depending on the location of the home (in town/in the country), greater precision may be required, or less exact gps positioning in other areas may require to allow a greater tolerance in those locations.
ke...@gmail.com <ke...@gmail.com> #60
fr...@gmail.com <fr...@gmail.com> #61
sc...@gmail.com <sc...@gmail.com> #62
zw...@google.com <zw...@google.com> #63
However most of the uses cases that are described above here, could be implemented with a realtime database, for which we have a tutorial online:
The physical geo location can be acquired from within JS with HTML5
xd...@gmail.com <xd...@gmail.com> #64
be...@gmail.com <be...@gmail.com> #65
Like many said, the data is already there, just provide us with an API to access it.
li...@gmail.com <li...@gmail.com> #66
Your automation système need to send request with your authenticated cookies en it will get a WTF
almost json with all the data.
French POC here :
xd...@gmail.com <xd...@gmail.com> #67
be...@gmail.com <be...@gmail.com> #68
fe...@gmail.com <fe...@gmail.com> #69
If I save my google account cookies how long can be used this before expire?
mo...@gmail.com <mo...@gmail.com> #70
pa...@gmail.com <pa...@gmail.com> #71
So I wouldn't build your wrapper around it just yet..
de...@gmail.com <de...@gmail.com> #72
xd...@gmail.com <xd...@gmail.com> #73
ro...@gmail.com <ro...@gmail.com> #74
Thanks for sharing that URL.
I was able to get the data I was looking for.
If it can help someone, below is a quick an dirty bash script that output data from 1 or several accounts into csv format. Just drop one or more cookie in the cookies array.
As I was unable to figure out every entry of that weird json, I had to scrape the data by line number once formated. So I get user id, profile image url, user name, latitude, longitude, time, current address, country code and battery level.
If someone figure out the meaning of other lines, please advise me.
#!/bin/bash
cookies=("cookie1" "cookie2")
tmp1=`mktemp /tmp/gsl.XXXX`
tmp2=`mktemp /tmp/gsl.XXXX`
echo "user id;profile image;user;latitude;longitude;time;address;country code;battery level"
for i in "${cookies[@]}"; do
cookie="$i"
curl -s "
tail -n +2 $tmp1|python -mjson.tool|sed '/^ ],/,+100 d'|tail -n +3 > $tmp2
size=`wc -l $tmp2|cut -d" " -f1`
iteration=`expr $size / 46`
z=0
while ! [ $z == $iteration ]; do
m=`expr $z \* 46`
userid=$(awk "FNR==$(expr $m + 3)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
profile_image=$(awk "FNR==$(expr $m + 4)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
user=$(awk "FNR==$(expr $m + 6)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
long=$(awk "FNR==$(expr $m + 16)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
lat=$(awk "FNR==$(expr $m + 17)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
ts=$(awk "FNR==$(expr $m + 19)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//'|sed 's|...$||g')
time=`date -d @$ts`
address=$(awk "FNR==$(expr $m + 21)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
cc=$(awk "FNR==$(expr $m + 23)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
bat=$(awk "FNR==$(expr $m + 44)" $tmp2|sed 's|,$||g'|sed -e 's/^ *//')
echo "$userid;$profile_image;$user;$lat;$long;$time;`echo -e $address`;$cc;$bat"
((z++))
done
done
rm -f $tmp1
rm -f $tmp2
mi...@gmail.com <mi...@gmail.com> #75
sy...@gmail.com <sy...@gmail.com> #76
fr...@gmail.com <fr...@gmail.com> #77
ka...@gmail.com <ka...@gmail.com> #78
ka...@gmail.com <ka...@gmail.com> #79
ma...@gmail.com <ma...@gmail.com> #80
fe...@gmail.com <fe...@gmail.com> #81
th...@gmail.com <th...@gmail.com> #82
vs...@gmail.com <vs...@gmail.com> #83
be...@gmail.com <be...@gmail.com> #84
lu...@gmail.com <lu...@gmail.com> #85
al...@gmail.com <al...@gmail.com> #86
fr...@gmail.com <fr...@gmail.com> #87
ah...@europcar.com <ah...@europcar.com> #88
cr...@gmail.com <cr...@gmail.com> #89
fe...@gmail.com <fe...@gmail.com> #90
ne...@gmail.com <ne...@gmail.com> #91
df...@redhat.com <df...@redhat.com> #92
df...@googlemail.com <df...@googlemail.com> #93
jo...@gmail.com <jo...@gmail.com> #94
se...@gmail.com <se...@gmail.com> #95
be...@google.com <be...@google.com>
fr...@gmail.com <fr...@gmail.com> #96
de...@gmail.com <de...@gmail.com> #97
ro...@gmail.com <ro...@gmail.com> #98
do...@gmail.com <do...@gmail.com> #99
vb...@gmail.com <vb...@gmail.com> #100
Other great experience is on cargo tracking. Eg: if a truck is close to a potentially dangerous area(eg: affected by floods and the weather service is reporting rain condition), send an alert to driver to stop or avoid that area.
ch...@gmail.com <ch...@gmail.com> #101
vb...@gmail.com <vb...@gmail.com> #102
th...@gmail.com <th...@gmail.com> #103
I got it to work using HSID, SSID and SID only
ry...@gmail.com <ry...@gmail.com> #104
Would have posted plus one but comments above suggested I add something
do...@gmail.com <do...@gmail.com> #105
he...@gmail.com <he...@gmail.com> #106
ke...@gmail.com <ke...@gmail.com> #107
j....@gmail.com <j....@gmail.com> #108
py...@google.com <py...@google.com>
ne...@gmail.com <ne...@gmail.com> #109
ne...@gmail.com <ne...@gmail.com> #110
mo...@gmail.com <mo...@gmail.com> #111
gr...@gmail.com <gr...@gmail.com> #113
It just needs a single authenticated call to a URL that returns a list of usernames together with the relevant timestamp, latitude and longitude, accuracy and (ideally) battery status.
How would I use it? Well the obvious Google Assistant response to 'Where is <person>?' is one option, although it is baffling that hasn't been implemented out of the box. Otherwise I can look at a home automation dashboard and see someone isn't present, tap on their name, and discover where Google thinks they actually are in my choice of ways, which wouldn't include any way that caused my dashboard to disappear. Given that the shared locations can be off the wall bonkers a map wouldn't be first choice either, at least not by itself, as I for one find it easier to recognise the word Finland rather than a map of the outskirts of Helsinki (and that is a real example, and the person was in south London at the time).
lc...@gmail.com <lc...@gmail.com> #114
lu...@appjobs.com <lu...@appjobs.com> #115
to...@gmail.com <to...@gmail.com> #116
je...@gmail.com <je...@gmail.com> #117
fe...@gmail.com <fe...@gmail.com> #118
and I've just found this other very promising page!
more here:
xd...@gmail.com <xd...@gmail.com> #119
ga...@gmail.com <ga...@gmail.com> #120
he...@gmail.com <he...@gmail.com> #121
sk...@gmail.com <sk...@gmail.com> #122
ko...@gmail.com <ko...@gmail.com> #123
sa...@gmail.com <sa...@gmail.com> #124
But instead i've starred the topic.
dr...@gmail.com <dr...@gmail.com> #125
The Firebase/HTML5/JS notion is OK, but would require manual location updates by the user, whereas I'd like to be able to use the native Google location service which is friction-free to implement.
da...@gmail.com <da...@gmail.com> #126
I also would love to have the ability to use it within Tasker to alert me when a family member is almost home ect.
EDIT: In the mean time, I'm looking into using the Google transport-tracker for my own simple use case and to test with.
to...@gmail.com <to...@gmail.com> #127
[Deleted User] <[Deleted User]> #128
[Deleted User] <[Deleted User]> #129
ma...@gmail.com <ma...@gmail.com> #130
ni...@gmail.com <ni...@gmail.com> #131
to...@googlemail.com <to...@googlemail.com> #132
ho...@gmail.com <ho...@gmail.com> #133
ma...@gmail.com <ma...@gmail.com> #134
ve...@gmail.com <ve...@gmail.com> #135
ru...@gmail.com <ru...@gmail.com> #136
co...@gmail.com <co...@gmail.com> #137
ka...@gmail.com <ka...@gmail.com> #138
outside of Google Maps?
m....@gmail.com <m....@gmail.com> #139
vb...@gmail.com <vb...@gmail.com> #140
ah...@gmail.com <ah...@gmail.com> #141
ho...@gmail.com <ho...@gmail.com> #142
pr...@gmail.com <pr...@gmail.com> #143
th...@gmail.com <th...@gmail.com> #144
gr...@gmail.com <gr...@gmail.com> #145
For everyone removing their stars due to the +1 issue, you can now choose to be notified only on major updates.
ho...@gmail.com <ho...@gmail.com> #146
do...@gmail.com <do...@gmail.com> #147
mh...@gmail.com <mh...@gmail.com> #148
ma...@gmail.com <ma...@gmail.com> #149
ca...@gmail.com <ca...@gmail.com> #150
ho...@gmail.com <ho...@gmail.com> #151
4....@gmail.com <4....@gmail.com> #152
tg...@gmail.com <tg...@gmail.com> #153
Please read at least #95, #99, #102, ..., #150
an...@gmail.com <an...@gmail.com> #154
ch...@gmail.com <ch...@gmail.com> #155
jo...@live.com <jo...@live.com> #156
su...@amazinggadgetdeals.com <su...@amazinggadgetdeals.com> #157
ca...@gmail.com <ca...@gmail.com> #158
It works like a comment, which then alerts everybody who's watching this thread. Everybody, except Google, that is.
If you star the issue, then Google gets the message, while nobody else is bothered.
Also, read threads before you post. Especially post 153.
xd...@gmail.com <xd...@gmail.com> #159
tg...@gmail.com <tg...@gmail.com> #160
gt...@gtoal.com <gt...@gtoal.com> #161
go...@gmail.com <go...@gmail.com> #162
ma...@gmail.com <ma...@gmail.com> #163
I'm the one who created it with another account and I'm un-starring it because of all your brainless "+1" (and also Google won't do anything about if).
Awesome community, please unplug your router.
pa...@gmail.com <pa...@gmail.com> #164
an...@gmail.com <an...@gmail.com> #165
mi...@gmail.com <mi...@gmail.com> #166
mu...@gmail.com <mu...@gmail.com> #167
sa...@gmail.com <sa...@gmail.com> #168
it...@gmail.com <it...@gmail.com> #169
ri...@driessen.net <ri...@driessen.net> #170
ca...@gmail.com <ca...@gmail.com> #171
Do you think you're alone in having this opinion, on this thread?
@169
There is no API, which is the reason for the whole thread.
I'm counting both of these as "+1". Please only post if you have something to add that others will be interested in, and only after reading the other posts.
If you want to join the club of people who want this feature, click the star. The star is how Google gets a sense of the 'need' for this feature.
Posting +1 or variants thereof only irritates other uses, and makes you look stupid and/or lazy. Please don't.
si...@gmail.com <si...@gmail.com> #172
da...@gmail.com <da...@gmail.com> #173
ne...@gmail.com <ne...@gmail.com> #174
ca...@gmail.com <ca...@gmail.com> #175
1) Google does not seem to be interested in providing this functionality.
2) Idiots putting +1.
Just to be clear: putting +1 makes you an idiot.
an...@thefunkygibbon.net <an...@thefunkygibbon.net> #176
ya...@gmail.com <ya...@gmail.com> #177
Would also be nice show shared locations on Nest Hub in addition to an API. i.e. "Where is Dad?" "Dad is 2.1 miles away" *displays map*
zh...@gmail.com <zh...@gmail.com> #178
da...@gmail.com <da...@gmail.com> #179
ro...@gmail.com <ro...@gmail.com> #180
ke...@gmail.com <ke...@gmail.com> #181
fi...@gmail.com <fi...@gmail.com> #182
lp...@gmail.com <lp...@gmail.com> #183
ha...@gmail.com <ha...@gmail.com> #184
ga...@gmail.com <ga...@gmail.com> #185
ky...@gmail.com <ky...@gmail.com> #186
et...@gmail.com <et...@gmail.com> #187
mi...@gmail.com <mi...@gmail.com> #188
al...@gmail.com <al...@gmail.com> #189
87...@gmail.com <87...@gmail.com> #190
I want to build a small robot for my desk that always points to my phone with a huge red arrow. I'd need an API to get the gps data or else I have to use third party apps on my phone.
ac...@gmail.com <ac...@gmail.com> #191
je...@gmail.com <je...@gmail.com> #192
dr...@gmail.com <dr...@gmail.com> #193
js...@gmail.com <js...@gmail.com> #194
lo...@gmail.com <lo...@gmail.com> #195
je...@gmail.com <je...@gmail.com> #196
ch...@gmail.com <ch...@gmail.com> #197
ju...@gmail.com <ju...@gmail.com> #198
Those +1s are really annoing.
ra...@google.com <ra...@google.com>
so...@gmail.com <so...@gmail.com> #199
br...@barry-callebaut.com <br...@barry-callebaut.com> #200
a....@gmail.com <a....@gmail.com> #201
ba...@gmail.com <ba...@gmail.com> #202
tr...@gmail.com <tr...@gmail.com> #203
01...@gmail.com <01...@gmail.com> #204
ks...@gmail.com <ks...@gmail.com> #205
I had an idea for that science project at my university to create a machine learning control algorithm for home automation that would take into account the places of where I and all of my family are and how are we are moving to control the appliances at home.
My idea is also to create a learning based algorithms that would be able to predict whether and when to control temperature at home based on where people are. If this is successful I would be able to create either an app or a plug-in for a home automation system.
ji...@gmail.com <ji...@gmail.com> #206
fe...@googlemail.com <fe...@googlemail.com> #207
th...@gmail.com <th...@gmail.com> #208
ni...@gmail.com <ni...@gmail.com> #209
an...@thefunkygibbon.net <an...@thefunkygibbon.net> #210
ch...@gmail.com <ch...@gmail.com> #211
ja...@gmail.com <ja...@gmail.com> #212
mi...@pcn.se <mi...@pcn.se> #213
ka...@gmail.com <ka...@gmail.com> #214
An...@gmx.de <An...@gmx.de> #215
da...@googlemail.com <da...@googlemail.com> #216
ev...@gmail.com <ev...@gmail.com> #217
da...@gmail.com <da...@gmail.com> #218
ne...@gmail.com <ne...@gmail.com> #219
20...@gmail.com <20...@gmail.com> #220
gi...@gmail.com <gi...@gmail.com> #221
he...@denis.kim <he...@denis.kim> #222
ro...@googlemail.com <ro...@googlemail.com> #223
dr...@gmail.com <dr...@gmail.com> #224
ma...@gmail.com <ma...@gmail.com> #225
da...@gmail.com <da...@gmail.com> #226
rp...@gmail.com <rp...@gmail.com> #227
PLEASE DO NOT post +1 or "me too" comments.
That will just spam a lot of people with a useless comment emailed to them. Your +1 comment will never be read or counted in any way by anyone that matters.
If you want to indicate support for this issue, use the star at the top next to the issue title. However, be aware that this issue has been open for over three years and Google has not responded in the least. It will probably never get done, as it would make it possible to build an application that would (in some small way) compete with Google Maps itself.
jh...@google.com <jh...@google.com> #228
mu...@gmail.com <mu...@gmail.com> #229
di...@gmail.com <di...@gmail.com> #230
ri...@gmail.com <ri...@gmail.com> #231
al...@gmail.com <al...@gmail.com> #232
sa...@gmail.com <sa...@gmail.com> #233
np...@gmail.com <np...@gmail.com> #234
jh...@google.com <jh...@google.com>
ma...@gmail.com <ma...@gmail.com> #235
th...@gmail.com <th...@gmail.com> #236
I want to make a Harry-potter (Mrs weasley) style clock for my parents that displays the locations of all of their kids (weve all grown up and moved out, so this is mostly for the novelty). My idea is everyone would have location shared via Google maps and the app running on the clock would periodically check locations and update the output. I’d have my siblings set up parameters defining geo areas for their home/work/etc.
xd...@gmail.com <xd...@gmail.com> #237
Noooooo, it's been triaged to "NeatIdea" status :(
That's where feature requests go to die. Sounds like we will be able to give this data to Google but never be able to get it back out until the end of time.
an...@gmail.com <an...@gmail.com> #238
ad...@gmail.com <ad...@gmail.com> #239
an...@gmail.com <an...@gmail.com> #240
That's just the way Google is. I'm happy there are alternatives. And despite being more tricky to find alternatives, it's still more reliable than relying on any products that Google develops: they all are going to be abandoned sooner or larer.
ma...@gmail.com <ma...@gmail.com> #241
dj...@gmail.com <dj...@gmail.com> #242
I wish to see location of my family on my wear os smartwatch.
ma...@gmail.com <ma...@gmail.com> #243
na...@gmail.com <na...@gmail.com> #244
You could have already implement and test it...
בתאריך יום ד׳, 29 בספט׳ 2021, 21:29, מאת <buganizer-system@google.com>:
[Deleted User] <[Deleted User]> #245
py...@gmail.com <py...@gmail.com> #246
al...@gmail.com <al...@gmail.com> #247
mc...@gmail.com <mc...@gmail.com> #248
ja...@gmail.com <ja...@gmail.com> #249
+1
kh...@gmail.com <kh...@gmail.com> #250
ke...@gmail.com <ke...@gmail.com> #251
ch...@gmail.com <ch...@gmail.com> #252
+1
de...@yahoo.com <de...@yahoo.com> #253
ni...@gmail.com <ni...@gmail.com> #254
ji...@gmail.com <ji...@gmail.com> #255
be...@gmail.com <be...@gmail.com> #256
- Alert my home automation system when I or my wife or both are away from home, to varying degrees - down the block, out of town, out of country.
- Same for when we return.
- Enable me to set up a cron job and alert for if I travel >100 miles since last ping so that she gets that alert whenever I land at my destination because I will forget
- The inverse; allow an alert if I or we are NOT in a specified geofence by ~ETA
- Where's Ben? feature for home or cloud-based components of a home security system to base event-driven messaging or other decisions on
fu...@gmail.com <fu...@gmail.com> #257
di...@gmail.com <di...@gmail.com> #258
ry...@gmail.com <ry...@gmail.com> #259
el...@gmail.com <el...@gmail.com> #260
jh...@google.com <jh...@google.com> #261
ru...@gmail.com <ru...@gmail.com> #262
ai...@gmail.com <ai...@gmail.com> #263
If you are signed into Maps, it appears that navigating to
I can imagine it'd be possible to use Selenium to automate downloading this list at a certain cadence (e.g. once a minute). Of course it's not a true API use because it relies on using a browser and being signed into Maps, but at least it doesn't require scraping because it gets you a nicely formed JSON file.
Of course it's "use at your own risk, can get broken at any time" kind of deal because it is a not a public API, but still better than nothing.
ol...@gmail.com <ol...@gmail.com> #264
fr...@gmail.com <fr...@gmail.com> #265
st...@gmail.com <st...@gmail.com> #266
While of no real practical use, it illustrates how people have a connection to their location information and would like access to it.
That piece is what brought me to search for this issue as it seemed like something that would be relatively trivial to program if the APIs existed, and give that (oddly impractical) feature to many others who may find value from it.
qa...@gmail.com <qa...@gmail.com> #267
ma...@gmail.com <ma...@gmail.com> #268
nu...@gmail.com <nu...@gmail.com> #269
nu...@gmail.com <nu...@gmail.com> #270
mi...@gmail.com <mi...@gmail.com> #271
m....@gmail.com <m....@gmail.com> #272
ph...@gmail.com <ph...@gmail.com> #273
ju...@bellwether-softworks.com <ju...@bellwether-softworks.com> #274
va...@gmail.com <va...@gmail.com> #275
ab...@gmail.com <ab...@gmail.com> #276
fe...@gmail.com <fe...@gmail.com> #277
ro...@gmail.com <ro...@gmail.com> #278
bh...@gmail.com <bh...@gmail.com> #279
ab...@gmail.com <ab...@gmail.com> #280
#277
ha...@gmail.com <ha...@gmail.com> #281
On how to enable, and the limitations:
While not as ideal as having a documented API, this satisfies some of the use cases I would want to explore with such an endpoint.
jo...@gmail.com <jo...@gmail.com> #282
Also posted on
There is no official API (yet), but someone created a cool Python package
Install
pip install locationsharinglib
Usage:
from locationsharinglib import Service
cookies_file = 'cookies.txt'
google_email = '<your google username>@gmail.com'
service = Service(cookies_file=cookies_file, authenticating_account=google_email)
for person in service.get_all_people():
print(person)
-
cookies.txt file
You need to sign out, and manually sign into your Google account. Then browse to google.com/maps and extract from your "google.com" cookies and save it as
cookies.txt
- Checkout
to help export such file very easilythis chrome extension
- Checkout
mi...@gmail.com <mi...@gmail.com> #283
wi...@gmail.com <wi...@gmail.com> #284
fr...@muenn.net <fr...@muenn.net> #285
ba...@gmail.com <ba...@gmail.com> #286
ja...@gmail.com <ja...@gmail.com> #287
Each driver would share their location with a central administrative account which can then map out where each bus is. Sometimes different buses and drivers are used so GPS devices are not always available but everyone will have their phone on them.
Going wider, my company does coaches for events around the UK and almost the same situation - it'll be used as a fleet tracking utility
ah...@gmail.com <ah...@gmail.com> #288
hi...@gmail.com <hi...@gmail.com> #289
It's possible on Android devices to create a widget that opens the Maps app to a specific user's location, but I think that's probably accomplished with an intent rather than a URL, and as of now HomeAssistant doesn't support launching intents (and I can't extract that information from the widget anyways).
b8...@gmail.com <b8...@gmail.com> #290
HA Map:
Actionable Notifications:
Broadcast intents:
ad...@hackaday.com <ad...@hackaday.com> #291
az...@gmail.com <az...@gmail.com> #292
ma...@gmail.com <ma...@gmail.com> #293
ch...@gmail.com <ch...@gmail.com> #294
ma...@gmail.com <ma...@gmail.com> #295
ri...@gmail.com <ri...@gmail.com> #296
la...@gmail.com <la...@gmail.com> #297
ji...@gmail.com <ji...@gmail.com> #298
vi...@gmail.com <vi...@gmail.com> #299
da...@geak.ru <da...@geak.ru> #300
wa...@gmail.com <wa...@gmail.com> #301
cr...@gmail.com <cr...@gmail.com> #302
Basically any developer who wants to setup a service that provides information based on users location will have to rebuild Google location sharing, and for very low feature set apps, this becomes overkill.
ra...@gmail.com <ra...@gmail.com> #303
Although I can imagine many users will decide using an open source solution such as that is quicker/easier than waiting for this feature.
The question is, dear Google, do you really want to push users to open source solutions and have them turn of your location tracking? How much $$$ do you make by selling data about user movements? Do you want to loose that income due to your refusal to implement a simple API?
ju...@icloud.com <ju...@icloud.com> #304
sa...@gmail.com <sa...@gmail.com> #305
Someone I know has dementia, and they shared their location with their caregiver. Out of concern for his well-being, the person's immediate family, who lives abroad, has also requested access, but the caregiver cannot forward it via maps. They approached me to build a solution, but I can't do it without an API.
am...@gmail.com <am...@gmail.com> #306
gt...@gtoal.com <gt...@gtoal.com> #307
je...@gmail.com <je...@gmail.com> #308
iv...@wiima.fi <iv...@wiima.fi> #309
aa...@gmail.com <aa...@gmail.com> #310
ac...@gmail.com <ac...@gmail.com> #311
sk...@gmail.com <sk...@gmail.com> #312
va...@gmail.com <va...@gmail.com> #313
de...@gmail.com <de...@gmail.com> #314
ok...@gmail.com <ok...@gmail.com> #315
ga...@gmail.com <ga...@gmail.com> #316
oz...@gmail.com <oz...@gmail.com> #317
ko...@gmail.com <ko...@gmail.com> #318
sl...@gmail.com <sl...@gmail.com> #319
se...@seungjin.net <se...@seungjin.net> #320
Surprised that still it is not available.
sa...@gmail.com <sa...@gmail.com> #321
wf...@gmail.com <wf...@gmail.com> #322
pr...@gmail.com <pr...@gmail.com> #323
I don't want to use a third-party app which endangers or will endanger my privacy. Eg: Life360.
Having owntracks on each phone in my family is hard, but thanks #307. I will try.
Any Google devs reading this: There's a way to tie Google Maps Location Sharing, Find My Network, Family Link and this API "NeatIdea" endpoint together, which might be life-changing for millions of people.
Description
# It is OK to share your API Project ID, but _not_ API keys.
What would you like to see us add to this API?What would you like to see us add to this API?
=> Is it possible to display on my website's Google Map the device location of a user who has shared it with me ?
What part of the API (please specify, a library, or the code module)?
=> Google Maps Javascript API or that new feature to share a device position to another email.
Please describe how the feature should work:
=> I've submitted my request in stackoverflow :
Please give a use case or explain where and why you need this feature:
=> I have a website (not online yet) where I want to share the position of my Android phone. The website Api key has been generated with a different email than my phone.