# \[Solved\] Google geocoding precision **URL:** \ **Category:** Questions about Thunkable X\ **Tags:** googlemaps, solved\ **Created:** [April 8, 2020, 6:36pm UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004 "2020-04-08T18:36:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![sleon003x2rq](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@sleon003x2rq](https://community.thunkable.com/u/sleon003x2rq)\ **Post date:** [April 8, 2020, 6:36pm UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/1 "2020-04-08T18:36:49Z")
Hi, so I’ve been playing with the google maps geocoding api and I noticed that when I click on a building the returned street address isn’t right. for example: I clicked on all the building across my current location and the majority of the address returned the same, something like 5 out 7 buildings returned the same address. when i click on my current location it may return the address of my actual location or the address of the building across the street. I tried to duplicate what I was seeing on my project on the google maps app and I was able to duplicate it, if I really tried too…I zoomed in all the way on a building, and clicked on the corner of the property it may give me the next address over but if I click on the center of the building it will always return the right address. I wonder if am doing something funny with my block, i looked through the google maps api dev documentation and stack overflow to see what other tests i could run but didn’t see much info…any suggestions would be greatly appreciated. Thanks!!! ![geocodeblocks](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/8/085b6e4699e090670d4d3571e12255a13762ca9f.png) ---
**Author:** ![sleon003x2rq](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@sleon003x2rq](https://community.thunkable.com/u/sleon003x2rq)\ **Post date:** [April 12, 2020, 8:50pm UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/2 "2020-04-12T20:50:41Z")
ugh well, after walking around and looking at my JSON responses I think part of the issue was the **&result\_type=street\_address** turns out that “street\_address” will not necessarily match the actual building address, i made the mistake of assuming it always would. So for now I will leave the result\_type out of my expression. so far leaving that out has been correct every time on all my tests. ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [April 12, 2020, 9:09pm UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/3 "2020-04-12T21:09:34Z")
Thanks for the update! I like thisnidea you have. Could you share the working code? ---
**Author:** ![henrikhngj5](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/henrikhngj5/32/67710_2.png) [@henrikhngj5](https://community.thunkable.com/u/henrikhngj5)\ **Post date:** [April 13, 2020, 8:55am UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/4 "2020-04-13T08:55:53Z")
really cool idea… 👍 ---
**Author:** ![sleon003x2rq](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@sleon003x2rq](https://community.thunkable.com/u/sleon003x2rq)\ **Post date:** [April 14, 2020, 10:02pm UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/5 "2020-04-14T22:02:52Z")
sure… let me clean my blockspace I have a lot of random things floating around 🤣 but I simply was playing with the api’s “filter by type” to see what I could get [/intro#reverse-restricted](https://developers.google.com/maps/documentation/geocoding/intro#reverse-restricted) > The following example filters the addresses returned to include only those with a location type of ROOFTOP and an address type of street\_address. > > [https://maps.googleapis.com/maps/api/geocode/json?latlng=40.714224,-73.961452](https://maps.googleapis.com/maps/api/geocode/json?latlng=40.714224,-73.961452) > &location\_type=ROOFTOP&result\_type=street\_address&key=YOUR\_API\_KEY here is an image that sort of helps understand what the different locations types can be (other APIs outthere offer more options)…after doing some digging I can understand how two ![Untitled](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/1/9/19a7248dc6c317b7bd9d464aef8410ab6772efae.jpeg) buildings can share the same “street\_address” or at least their definition of it ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [November 8, 2024, 11:39am UTC](https://community.thunkable.com/t/solved-google-geocoding-precision/563004/6 "2024-11-08T11:39:02Z")