# When turn tab to Geo, the window white-outs in Dgraph Ratel
**URL:** https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796
**Category:** Ratel
**Tags:** kind:bug
**Created:** [September 22, 2022, 7:56am UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796 "2022-09-22T07:56:06Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@TenUchikawa](https://discuss.dgraph.io/u/TenUchikawa)
#### Post date: [September 22, 2022, 7:56am UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/1 "2022-09-22T07:56:06Z")
Hi I’m ten.
I’m using latest version of ratel
I think it is probably a bug and will report it.
I have the following type
```auto
type UserPosition {
owner: UserTable! @hasInverse(field: position)
name: String! @id @search(by: [hash])
id: ID!
location: Point
}
```
And we queried this kind of JSON in Dgraph Ratel DQL.
```auto
"data": {
"q": [
{
"name": " ******",
"location": {
"type": "Point",
"coordinates": [
"-120.40610713313157",
"35.51546935551258"
]
}
}
]
},
```
The Graph tab and the JSON tab show the data correctly, but as soon as I turn it to Geo, the window white-outs. The console then displays an error like this
Also, when I reload the window, the data that should have been displayed last time is displayed correctly, but when I run the query again, it whiteouts.
Sorry if this is not a bug.
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [September 22, 2022, 4:21pm UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/2 "2022-09-22T16:21:28Z")
Share the DQL query.
---
### Author:  [@TenUchikawa](https://discuss.dgraph.io/u/TenUchikawa)
#### Post date: [September 22, 2022, 4:37pm UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/3 "2022-09-22T16:37:03Z")
here
```auto
{
q(func: type(UserPosition))
{
name:UserPosition.name
location:UserPosition.location
}
}
```
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [September 22, 2022, 4:51pm UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/4 "2022-09-22T16:51:02Z")
Here is working fine.
This error happens when the response is malformed or not available.
```auto
{
"data": {
"tourist": [
{
"name": "Hamon Tower",
"location": {
"type": "Point",
"coordinates": [
-122.4220186,
37.772318
]
}
}
]
}
```
---
### Author:  [@TenUchikawa](https://discuss.dgraph.io/u/TenUchikawa)
#### Post date: [September 23, 2022, 1:45am UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/5 "2022-09-23T01:45:55Z")
My query actually aliases the table UserPosition.fbUid to name.
Like this.
```auto
{
q(func: type(UserPosition))
{
name:UserPosition.fbUid
location:UserPosition.location
}
}
```
Is this a problem?
Also, I looked at the network tab and the response is a 200 number with the following JSON returned. Other than that, there is no indication that the network request failed.
```auto
{
"data": {
"q": [
{
"name": "hLDu10SMq8UaRhUncFjYbzrNwQx2",
"location": {
"type": "Point",
"coordinates": [139.40610713313157, 35.51546935551258]
}
}
{
"name": "GiY9pt8ZrIcbWkdOLBlryh1TOLv2",
"location": {
"type": "Point",
"coordinates": [139.4175337, 35.5154092]
}
}
]
},
"extensions": {
"server_latency": {
"parsing_ns": 124263,
"processing_ns": 981390,
"encoding_ns": 145954,
"assign_timestamp_ns": 1210098,
"total_ns": 2567453
},
"txn": { "start_ts": 21573 }
"metrics": {
"num_uids": {
"UserPosition.fbUid": 2,
"UserPosition.location": 2,
"_total": 4,
"dgraph.type": 0
}
}
}
}
}
```
I am using Nginx to connect to Alpha and am redirecting with Conf like this
This may also be a problem.
```auto
upstream dgraph-backend {
server localhost:8080;
}
server {
listen 9999;# http2;
server_name dgraph_admin;
location /ratel/ {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://dgraph-backend/;
}
}
```
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [September 23, 2022, 2:36am UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/6 "2022-09-23T02:36:45Z")
> [@TenUchikawa](#):
>
> `"-120.40610713313157",`
I don’t get why this is a quoted string. And your last response isn’t.
Can you share an example of you mutation?
---
### Author:  [@TenUchikawa](https://discuss.dgraph.io/u/TenUchikawa)
#### Post date: [September 23, 2022, 2:44am UTC](https://discuss.dgraph.io/t/when-turn-tab-to-geo-the-window-white-outs-in-dgraph-ratel/17796/7 "2022-09-23T02:44:45Z")
OMG…
Sorry, It was my mistake completely. It seems that I changed the schema while leaving the data that I had put in for testing purposes.
Thank you for your help.
The data actually returned in the Network response from the DB were both Float. However, when I open the JSON tab in Ratel, does it keep the type it was when I put the data in? It seems to be.
So in actual operation, I could only see Float.