<p>After quite some research it turns out these are EPSG:3857 WGS 84 / Pseudo-Mercator coordinates.<br>
I found this out by visiting <a href="https://epsg.io" rel="noreferrer">this</a> website where you can transform coordinates from different systems. </p>

CC BY-SA 4.0
2020-02-26T01:29:07.840Z
"Pseudo-Mercator coordinates" wow!
uhoh
CC BY-SA 4.0
2021-09-17T06:17:58.343Z
So they are not lat and lon at all ;-)

Assuming they are in metres, the level of precision is kinda silly. I'm fairly sure the wifi system can't measure the locations of things with a resolution of 0.1 nm....
Semidiurnal Simon
CC BY-SA 4.0
2020-02-25T20:58:44.287Z
2020-02-25T21:12:39.213Z
2020-02-25T21:12:39.213Z
Trup3s
<p>I am currently working on a project with my university and ran into trouble. I am building an application for indoor localization and am currently trying to benchmark our implementation. To do this I use some data sets with reference values which contain the latitude and longitude of a scanned point, but I can't figure out, how to interpret these kind of coordinates:</p>

<p>Latitude: 4864889.6629166845<br>
Longitude: -7515.916799399859</p>

<p><a href="https://archive.ics.uci.edu/ml/datasets/ujiindoorloc#" rel="nofollow noreferrer">Here</a> is the link to the data sheet.</p>

<p>Maybe one of you guys has some experience with this and can help me out, thanks for your help!</p>

<hr>

<p>Per request in comments, here's some of the data and explanation <s>in case</s> when the link rots (they always do!):</p>

<pre><code>Attribute Information:

Attribute 001 (WAP001): Intensity value for WAP001. Negative integer values from -104 to 0 and +100. Positive value 100 used if WAP001 was not detected.
....
Attribute 520 (WAP520): Intensity value for WAP520. Negative integer values from -104 to 0 and +100. Positive Vvalue 100 used if WAP520 was not detected.
Attribute 521 (Longitude): Longitude. Negative real values from -7695.9387549299299000 to -7299.786516730871000
Attribute 522 (Latitude): Latitude. Positive real values from 4864745.7450159714 to 4865017.3646842018.
Attribute 523 (Floor): Altitude in floors inside the building. Integer values from 0 to 4.
Attribute 524 (BuildingID): ID to identify the building. Measures were taken in three different buildings. Categorical integer values from 0 to 2.
Attribute 525 (SpaceID): Internal ID number to identify the Space (office, corridor, classroom) where the capture was taken. Categorical integer values.
Attribute 526 (RelativePosition): Relative position with respect to the Space (1 - Inside, 2 - Outside in Front of the door). Categorical integer values.
Attribute 527 (UserID): User identifier (see below). Categorical integer values.
Attribute 528 (PhoneID): Android device identifier (see below). Categorical integer values.
Attribute 529 (Timestamp): UNIX Time when the capture was taken. Integer value.
</code></pre>

<blockquote>
  <p>Data Set Information:</p>
  
  <p>Many real world applications need to know the localization of a user in the world to provide their services. Therefore, automatic user localization has been a hot research topic in the last years. Automatic user localization consists of estimating the position of the user (latitude, longitude and altitude) by using an electronic device, usually a mobile phone. Outdoor localization problem can be solved very accurately thanks to the inclusion of GPS sensors into the mobile devices. However, indoor localization is still an open problem mainly due to the loss of GPS signal in indoor environments. Although, there are some indoor positioning technologies and methodologies, this database is focused on WLAN fingerprint-based ones (also know as WiFi Fingerprinting).</p>
  
  <p>Although there are many papers in the literature trying to solve the indoor localization problem using a WLAN fingerprint-based method, there still exists one important drawback in this field which is the lack of a common database for comparison purposes. So, UJIIndoorLoc database is presented to overcome this gap. We expect that the proposed database will become the reference database to compare different indoor localization methodologies based on WiFi fingerprinting.</p>
  
  <p>The UJIIndoorLoc database covers three buildings of Universitat Jaume I with 4 or more floors and almost 110.000m2. It can be used for classification, e.g. actual building and floor identification, or regression, e.g. actual longitude and latitude estimation. It was created in 2013 by means of more than 20 different users and 25 Android devices. The database consists of 19937 training/reference records (trainingData.csv file) and 1111 validation/test records (validationData.csv file).</p>
  
  <p>The 529 attributes contain the WiFi fingerprint, the coordinates where it was taken, and other useful information.</p>
  
  <p>Each WiFi fingerprint can be characterized by the detected Wireless Access Points (WAPs) and the corresponding Received Signal Strength Intensity (RSSI). The intensity values are represented as negative integer values ranging -104dBm (extremely poor signal) to 0dbM. The positive value 100 is used to denote when a WAP was not detected. During the database creation, 520 different WAPs were detected. Thus, the WiFi fingerprint is composed by 520 intensity values.</p>
  
  <p>Then the coordinates (latitude, longitude, floor) and Building ID are provided as the attributes to be predicted.</p>
  
  <p>Additional information has been provided.</p>
  
  <p>The particular space (offices, labs, etc.) and the relative position (inside/outside the space) where the capture was taken have been recorded. Outside means that the capture was taken in front of the door of the space.</p>
  
  <p>Information about who (user), how (android device &amp; version) and when (timestamp) WiFi capture was taken is also recorded.</p>
</blockquote>

CC BY-SA 4.0
2020-02-25T19:59:43.800Z
I suspect that's supposed to be 48.648866 N, 75.15916799 W.
gerrit
CC BY-SA 4.0
2020-02-25T20:04:48.177Z
I've already tried that, but the data set was created at university of jaume in Spain (39.995015, -0.069154) which should have at least latitude between ~36 and ~42. But thanks for your try!
Trup3s
CC BY-SA 4.0
2020-02-25T20:44:04.847Z
My guess would be UTM in meters, but assuming zone 31 those coordinates would point to latitude 43N, which is some hundred kilometers North from Universitat Jaume I campus. However, assuming those coordinates to be meters the dataset would span just a few hundred meters, which makes sense for the campus of a small university. Then, my guess is updated as Northing and Easting in meters with a still unknown origin. Anyway, I think the best advice would be to ask the authors - and tell us for completion.
Pere
CC BY-SA 4.0
2020-02-25T23:36:12.820Z
Please copy-paste the important part of the remote link, making your question comprehensible after the remote side goes down.
peterh
CC BY-SA 4.0
2021-09-10T03:10:36.820Z
hope you're doing fine. Well, i'm working on the same project that you. As you should have finished it, i'd like to know if you could share with me your final project so i could take some ideas from it. Sincerely, Lucas T. Email: lucastavarestt@gmail.com
Lucas Tavares
CC BY-SA 4.0
2021-09-10T03:24:42.890Z
could be a projected coordinate system.  Should be part of the metadata
f.thorpe
<geography><data-formats>
How to interpret these kind of coordinates?
Trup3s
# How to interpret these kind of coordinates?

(Asked by: username_0 on 2020-02-25)

I am currently working on a project with my university and ran into trouble. I am building an application for indoor localization and am currently trying to benchmark our implementation. To do this I use some data sets with reference values which contain the latitude and longitude of a scanned point, but I can't figure out, how to interpret these kind of coordinates:

Latitude: 4864889.6629166845  
Longitude: -7515.916799399859

[Here](https://archive.ics.uci.edu/ml/datasets/ujiindoorloc#) is the link to the data sheet.

Maybe one of you guys has some experience with this and can help me out, thanks for your help!

---

Per request in comments, here's some of the data and explanation ~~in case~~ when the link rots (they always do!):

```
Attribute Information:

Attribute 001 (WAP001): Intensity value for WAP001. Negative integer values from -104 to 0 and +100. Positive value 100 used if WAP001 was not detected.
....
Attribute 520 (WAP520): Intensity value for WAP520. Negative integer values from -104 to 0 and +100. Positive Vvalue 100 used if WAP520 was not detected.
Attribute 521 (Longitude): Longitude. Negative real values from -7695.9387549299299000 to -7299.786516730871000
Attribute 522 (Latitude): Latitude. Positive real values from 4864745.7450159714 to 4865017.3646842018.
Attribute 523 (Floor): Altitude in floors inside the building. Integer values from 0 to 4.
Attribute 524 (BuildingID): ID to identify the building. Measures were taken in three different buildings. Categorical integer values from 0 to 2.
Attribute 525 (SpaceID): Internal ID number to identify the Space (office, corridor, classroom) where the capture was taken. Categorical integer values.
Attribute 526 (RelativePosition): Relative position with respect to the Space (1 - Inside, 2 - Outside in Front of the door). Categorical integer values.
Attribute 527 (UserID): User identifier (see below). Categorical integer values.
Attribute 528 (PhoneID): Android device identifier (see below). Categorical integer values.
Attribute 529 (Timestamp): UNIX Time when the capture was taken. Integer value.

```

> Data Set Information:
>
> Many real world applications need to know the localization of a user in the world to provide their services. Therefore, automatic user localization has been a hot research topic in the last years. Automatic user localization consists of estimating the position of the user (latitude, longitude and altitude) by using an electronic device, usually a mobile phone. Outdoor localization problem can be solved very accurately thanks to the inclusion of GPS sensors into the mobile devices. However, indoor localization is still an open problem mainly due to the loss of GPS signal in indoor environments. Although, there are some indoor positioning technologies and methodologies, this database is focused on WLAN fingerprint-based ones (also know as WiFi Fingerprinting).
>
> Although there are many papers in the literature trying to solve the indoor localization problem using a WLAN fingerprint-based method, there still exists one important drawback in this field which is the lack of a common database for comparison purposes. So, UJIIndoorLoc database is presented to overcome this gap. We expect that the proposed database will become the reference database to compare different indoor localization methodologies based on WiFi fingerprinting.
>
> The UJIIndoorLoc database covers three buildings of Universitat Jaume I with 4 or more floors and almost 110.000m2. It can be used for classification, e.g. actual building and floor identification, or regression, e.g. actual longitude and latitude estimation. It was created in 2013 by means of more than 20 different users and 25 Android devices. The database consists of 19937 training/reference records (trainingData.csv file) and 1111 validation/test records (validationData.csv file).
>
> The 529 attributes contain the WiFi fingerprint, the coordinates where it was taken, and other useful information.
>
> Each WiFi fingerprint can be characterized by the detected Wireless Access Points (WAPs) and the corresponding Received Signal Strength Intensity (RSSI). The intensity values are represented as negative integer values ranging -104dBm (extremely poor signal) to 0dbM. The positive value 100 is used to denote when a WAP was not detected. During the database creation, 520 different WAPs were detected. Thus, the WiFi fingerprint is composed by 520 intensity values.
>
> Then the coordinates (latitude, longitude, floor) and Building ID are provided as the attributes to be predicted.
>
> Additional information has been provided.
>
> The particular space (offices, labs, etc.) and the relative position (inside/outside the space) where the capture was taken have been recorded. Outside means that the capture was taken in front of the door of the space.
>
> Information about who (user), how (android device & version) and when (timestamp) WiFi capture was taken is also recorded.

**Tags:** geography, data-formats

> **Comments:**
> **username_1**: I suspect that's supposed to be 48.648866 N, 75.15916799 W.  
> **username_0**: I've already tried that, but the data set was created at university of jaume in Spain (39.995015, -0.069154) which should have at least latitude between ~36 and ~42. But thanks for your try!  
> **username_2**: My guess would be UTM in meters, but assuming zone 31 those coordinates would point to latitude 43N, which is some hundred kilometers North from Universitat Jaume I campus. However, assuming those coordinates to be meters the dataset would span just a few hundred meters, which makes sense for the campus of a small university. Then, my guess is updated as Northing and Easting in meters with a still unknown origin. Anyway, I think the best advice would be to ask the authors - and tell us for completion.  
> **username_3**: Please copy-paste the important part of the remote link, making your question comprehensible after the remote side goes down.  
> **username_4**: hope you're doing fine. Well, i'm working on the same project that you. As you should have finished it, i'd like to know if you could share with me your final project so i could take some ideas from it. Sincerely, username_4 T. Email: lucastavarestt@gmail.com  
> **username_5**: could be a projected coordinate system.  Should be part of the metadata  

---

## 1 answers

### Answer by username_0 on 2020-02-25. Score: 8

After quite some research it turns out these are EPSG:3857 WGS 84 / Pseudo-Mercator coordinates.  
I found this out by visiting [this](https://epsg.io) website where you can transform coordinates from different systems.

> **Comments:**
> **username_6**: "Pseudo-Mercator coordinates" wow!  
> **username_7**: So they are not lat and lon at all ;-)  Assuming they are in metres, the level of precision is kinda silly. I'm fairly sure the wifi system can't measure the locations of things with a resolution of 0.1 nm....  

---

