{
  "id": 230558,
  "title": "Incorrect map_info height for site 5d27075f03f801723c2e360f",
  "url": "/competitions/indoor-location-navigation/discussion/230558",
  "author_name": "",
  "post_date": "2021-04-04T13:23:23.053684900Z",
  "votes": 21,
  "comment_count": 17,
  "views": 0,
  "content": "<p>I believe the height values in the floor_info.json files for the floors on site 5d27075f03f801723c2e360f are incorrect - below are the adjustments I made to make the waypoints line up correctly with the image (these are approximate - it's difficult to tell exactly what they should be):</p>\n<p>This is the only site I noticed this for (for sites that have test paths - I haven't checked the other sites)</p>\n<p>Site 5d27075f03f801723c2e360f</p>\n<p>Floor B1<br>\n5d27075f03f801723c2e3618<br>\n252.25002019023339 =&gt; 240.0</p>\n<p>Floor F1<br>\n5d27075f03f801723c2e3611<br>\n221.9711303099799 =&gt; 211</p>\n<p>Floor F2<br>\n5d27075f03f801723c2e3614<br>\n222.0824509676249 =&gt; 211</p>\n<p>Floor F3<br>\n5d27075f03f801723c2e3610<br>\n221.85980965595348 =&gt; 211</p>\n<p>Floor F4<br>\n5d27075f03f801723c2e3612<br>\n221.85980965595348 =&gt; 211.0</p>\n<p>Floor F5<br>\n5d27075f03f801723c2e3613<br>\n142.6008283613404 =&gt; 135.3</p>\n<p>Floor F6<br>\n5d27075f03f801723c2e3615<br>\n142.48950770731392 =&gt; 135.3</p>\n<p>Floor F7<br>\n5d27075f03f801723c2e3619<br>\n142.48950770731392 =&gt; 135.3</p>",
  "messages": [
    {
      "id": "1262582",
      "postDate": "04/04/2021 13:23:23",
      "content": "<p>I believe the height values in the floor_info.json files for the floors on site 5d27075f03f801723c2e360f are incorrect - below are the adjustments I made to make the waypoints line up correctly with the image (these are approximate - it's difficult to tell exactly what they should be):</p>\n<p>This is the only site I noticed this for (for sites that have test paths - I haven't checked the other sites)</p>\n<p>Site 5d27075f03f801723c2e360f</p>\n<p>Floor B1<br>\n5d27075f03f801723c2e3618<br>\n252.25002019023339 =&gt; 240.0</p>\n<p>Floor F1<br>\n5d27075f03f801723c2e3611<br>\n221.9711303099799 =&gt; 211</p>\n<p>Floor F2<br>\n5d27075f03f801723c2e3614<br>\n222.0824509676249 =&gt; 211</p>\n<p>Floor F3<br>\n5d27075f03f801723c2e3610<br>\n221.85980965595348 =&gt; 211</p>\n<p>Floor F4<br>\n5d27075f03f801723c2e3612<br>\n221.85980965595348 =&gt; 211.0</p>\n<p>Floor F5<br>\n5d27075f03f801723c2e3613<br>\n142.6008283613404 =&gt; 135.3</p>\n<p>Floor F6<br>\n5d27075f03f801723c2e3615<br>\n142.48950770731392 =&gt; 135.3</p>\n<p>Floor F7<br>\n5d27075f03f801723c2e3619<br>\n142.48950770731392 =&gt; 135.3</p>",
      "rawMarkdown": "I believe the height values in the floor_info.json files for the floors on site 5d27075f03f801723c2e360f are incorrect - below are the adjustments I made to make the waypoints line up correctly with the image (these are approximate - it's difficult to tell exactly what they should be):\n\nThis is the only site I noticed this for (for sites that have test paths - I haven't checked the other sites)\n\nSite 5d27075f03f801723c2e360f\n\nFloor B1\n5d27075f03f801723c2e3618\n252.25002019023339 => 240.0\n\nFloor F1\n5d27075f03f801723c2e3611\n221.9711303099799 => 211\n\nFloor F2\n5d27075f03f801723c2e3614\n222.0824509676249 => 211\n\nFloor F3\n5d27075f03f801723c2e3610\n221.85980965595348 => 211\n\nFloor F4\n5d27075f03f801723c2e3612\n221.85980965595348 => 211.0\n\nFloor F5\n5d27075f03f801723c2e3613\n142.6008283613404 => 135.3\n\nFloor F6\n5d27075f03f801723c2e3615\n142.48950770731392 => 135.3\n\nFloor F7\n5d27075f03f801723c2e3619\n142.48950770731392 => 135.3",
      "votes": null
    },
    {
      "id": "1262584",
      "postDate": "04/04/2021 13:24:59",
      "content": "<p>Oh, and it's also possible that it's the image that is actually not correct, but the image didn't look distorted to me; but I'm not 100% sure :)</p>",
      "rawMarkdown": "Oh, and it's also possible that it's the image that is actually not correct, but the image didn't look distorted to me; but I'm not 100% sure :)",
      "votes": null
    },
    {
      "id": "1262596",
      "postDate": "04/04/2021 13:42:12",
      "content": "<p>Look at my post, is related <a href=\"https://www.kaggle.com/c/indoor-location-navigation/discussion/230379\" target=\"_blank\">https://www.kaggle.com/c/indoor-location-navigation/discussion/230379</a></p>",
      "rawMarkdown": "Look at my post, is related https://www.kaggle.com/c/indoor-location-navigation/discussion/230379",
      "votes": null
    },
    {
      "id": "1262601",
      "postDate": "04/04/2021 13:54:35",
      "content": "<p>Ah, interesting - yep! it looks like that could be a similar issue (I haven't looked at that site yet)</p>",
      "rawMarkdown": "Ah, interesting - yep! it looks like that could be a similar issue (I haven't looked at that site yet)",
      "votes": null
    },
    {
      "id": "1268590",
      "postDate": "04/09/2021 15:07:35",
      "content": "<p>I wonder what will happen if you use snap to grid method with your scaling values. The LB score get better or worse?</p>",
      "rawMarkdown": "I wonder what will happen if you use snap to grid method with your scaling values. The LB score get better or worse?",
      "votes": null
    },
    {
      "id": "1268666",
      "postDate": "04/09/2021 16:13:14",
      "content": "<p>I don't think it would affect it because (I think) this only matters if you're converting between image pixels and meters. (so if you aren't using the images, then it shouldn't matter). </p>\n<p>I believe the waypoint x,y values (used for snap to grid) are independent of this (could be wrong though!)</p>",
      "rawMarkdown": "I don't think it would affect it because (I think) this only matters if you're converting between image pixels and meters. (so if you aren't using the images, then it shouldn't matter). \n\nI believe the waypoint x,y values (used for snap to grid) are independent of this (could be wrong though!)",
      "votes": null
    },
    {
      "id": "1268950",
      "postDate": "04/10/2021 01:27:40",
      "content": "<p>I agree with you. The test labels would be consistent with train waypoints. </p>\n<p>Do you find any specific rules (e.g., ratio) of the distortion? Are true height values always smaller?</p>",
      "rawMarkdown": "I agree with you. The test labels would be consistent with train waypoints. \n\nDo you find any specific rules (e.g., ratio) of the distortion? Are true height values always smaller?",
      "votes": null
    },
    {
      "id": "1268960",
      "postDate": "04/10/2021 01:57:47",
      "content": "<p>I was visualizing the waypoints on the map and noticed a shift (on that map only). I just played with some values (above) until the waypoints looked like they lined up on the map.</p>",
      "rawMarkdown": "I was visualizing the waypoints on the map and noticed a shift (on that map only). I just played with some values (above) until the waypoints looked like they lined up on the map.",
      "votes": null
    },
    {
      "id": "1268970",
      "postDate": "04/10/2021 02:26:14",
      "content": "<p>I see. Thanks!</p>",
      "rawMarkdown": "I see. Thanks!",
      "votes": null
    },
    {
      "id": "1269148",
      "postDate": "04/10/2021 08:10:46",
      "content": "<p>did you find any generic rule to move the waypoint to the correct position on image?</p>",
      "rawMarkdown": "did you find any generic rule to move the waypoint to the correct position on image?",
      "votes": null
    },
    {
      "id": "1269450",
      "postDate": "04/10/2021 14:41:04",
      "content": "<p>No, I tried a few things thinking I should be able to find exactly what the value should be, but couldn't make it match up - the values above are what I'm using now</p>",
      "rawMarkdown": "No, I tried a few things thinking I should be able to find exactly what the value should be, but couldn't make it match up - the values above are what I'm using now",
      "votes": null
    },
    {
      "id": "1275131",
      "postDate": "04/16/2021 01:18:02",
      "content": "<p>Chris, thanks for sharing your insights and adjustments to leverage the geojson file. I'm also working on this problem, because some grids are inside the shops, which looks strange to me. BTW, I sent a message to you using the contact system in kaggle! I would be happy if you could check the e-mail. 🙏</p>",
      "rawMarkdown": "Chris, thanks for sharing your insights and adjustments to leverage the geojson file. I'm also working on this problem, because some grids are inside the shops, which looks strange to me. BTW, I sent a message to you using the contact system in kaggle! I would be happy if you could check the e-mail. 🙏",
      "votes": null
    },
    {
      "id": "1275153",
      "postDate": "04/16/2021 02:21:07",
      "content": "<p>Yes, some grids appear inside shops but are supposed to be in the hallways (like the ones I mentioned above), though there are some that I believe are correctly inside the blue areas (like training path 5e15b007f4c3420006d5229f) - but I think those are rare, and most paths should never be inside the blue shops.</p>\n<p>[also, I responded to your email - let me know if that didn't go through!]</p>",
      "rawMarkdown": "Yes, some grids appear inside shops but are supposed to be in the hallways (like the ones I mentioned above), though there are some that I believe are correctly inside the blue areas (like training path 5e15b007f4c3420006d5229f) - but I think those are rare, and most paths should never be inside the blue shops.\n\n[also, I responded to your email - let me know if that didn't go through!]",
      "votes": null
    },
    {
      "id": "1275248",
      "postDate": "04/16/2021 05:58:52",
      "content": "<p>Yeah, I guess it would be one of the key in this competition. <br>\nThanks for the quick reply, I responded to the e-mail :)</p>",
      "rawMarkdown": "Yeah, I guess it would be one of the key in this competition. \nThanks for the quick reply, I responded to the e-mail :)",
      "votes": null
    },
    {
      "id": "1307883",
      "postDate": "05/14/2021 18:18:45",
      "content": "<p>Thank you <a href=\"https://www.kaggle.com/chris62\" target=\"_blank\">@chris62</a> for the insights. Have you found out whether it is actually the image or the height/width that is wrong?</p>",
      "rawMarkdown": "Thank you @chris62 for the insights. Have you found out whether it is actually the image or the height/width that is wrong?",
      "votes": null
    },
    {
      "id": "1307892",
      "postDate": "05/14/2021 18:25:56",
      "content": "<p>I'm still not 100% sure where the issue actually is, but for the post processing I'm doing I think it doesn't matter - those adjusted site values seem to work. (because I'm matching to the floorplan image, so it doesn't matter if I scale the site or the image for that).</p>\n<p>If you're using the site height/width values for something other than matching to the floorplan though (like the geo values), then I'm not sure, sorry!</p>",
      "rawMarkdown": "I'm still not 100% sure where the issue actually is, but for the post processing I'm doing I think it doesn't matter - those adjusted site values seem to work. (because I'm matching to the floorplan image, so it doesn't matter if I scale the site or the image for that).\n\nIf you're using the site height/width values for something other than matching to the floorplan though (like the geo values), then I'm not sure, sorry!",
      "votes": null
    },
    {
      "id": "1307896",
      "postDate": "05/14/2021 18:36:20",
      "content": "<p>Thank you for your reply :) I'll try to verify it somehow</p>",
      "rawMarkdown": "Thank you for your reply :) I'll try to verify it somehow",
      "votes": null
    },
    {
      "id": "1307988",
      "postDate": "05/14/2021 20:52:28",
      "content": "<p>It seems that one polygon's unit corresponds to 0.863 m (I have checked 4 floor-building pairs). This value is consistent with 5d27075f03f801723c2e360f's polygons and heights/widths.</p>",
      "rawMarkdown": "It seems that one polygon's unit corresponds to 0.863 m (I have checked 4 floor-building pairs). This value is consistent with 5d27075f03f801723c2e360f's polygons and heights/widths.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1262584,
      "author_name": "chris62",
      "author_url": "",
      "post_date": "04/04/2021 13:24:59",
      "content": "<p>Oh, and it's also possible that it's the image that is actually not correct, but the image didn't look distorted to me; but I'm not 100% sure :)</p>",
      "votes": null,
      "replies": [
        {
          "id": 1307883,
          "author_name": "olaf2000",
          "author_url": "",
          "post_date": "05/14/2021 18:18:45",
          "content": "<p>Thank you <a href=\"https://www.kaggle.com/chris62\" target=\"_blank\">@chris62</a> for the insights. Have you found out whether it is actually the image or the height/width that is wrong?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1307892,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "05/14/2021 18:25:56",
          "content": "<p>I'm still not 100% sure where the issue actually is, but for the post processing I'm doing I think it doesn't matter - those adjusted site values seem to work. (because I'm matching to the floorplan image, so it doesn't matter if I scale the site or the image for that).</p>\n<p>If you're using the site height/width values for something other than matching to the floorplan though (like the geo values), then I'm not sure, sorry!</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1307896,
          "author_name": "olaf2000",
          "author_url": "",
          "post_date": "05/14/2021 18:36:20",
          "content": "<p>Thank you for your reply :) I'll try to verify it somehow</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1307988,
          "author_name": "olaf2000",
          "author_url": "",
          "post_date": "05/14/2021 20:52:28",
          "content": "<p>It seems that one polygon's unit corresponds to 0.863 m (I have checked 4 floor-building pairs). This value is consistent with 5d27075f03f801723c2e360f's polygons and heights/widths.</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 1262596,
      "author_name": "enric1296",
      "author_url": "",
      "post_date": "04/04/2021 13:42:12",
      "content": "<p>Look at my post, is related <a href=\"https://www.kaggle.com/c/indoor-location-navigation/discussion/230379\" target=\"_blank\">https://www.kaggle.com/c/indoor-location-navigation/discussion/230379</a></p>",
      "votes": null,
      "replies": [
        {
          "id": 1262601,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "04/04/2021 13:54:35",
          "content": "<p>Ah, interesting - yep! it looks like that could be a similar issue (I haven't looked at that site yet)</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 1268590,
      "author_name": "tomooinubushi",
      "author_url": "",
      "post_date": "04/09/2021 15:07:35",
      "content": "<p>I wonder what will happen if you use snap to grid method with your scaling values. The LB score get better or worse?</p>",
      "votes": null,
      "replies": [
        {
          "id": 1268666,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "04/09/2021 16:13:14",
          "content": "<p>I don't think it would affect it because (I think) this only matters if you're converting between image pixels and meters. (so if you aren't using the images, then it shouldn't matter). </p>\n<p>I believe the waypoint x,y values (used for snap to grid) are independent of this (could be wrong though!)</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1268950,
          "author_name": "tomooinubushi",
          "author_url": "",
          "post_date": "04/10/2021 01:27:40",
          "content": "<p>I agree with you. The test labels would be consistent with train waypoints. </p>\n<p>Do you find any specific rules (e.g., ratio) of the distortion? Are true height values always smaller?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1268960,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "04/10/2021 01:57:47",
          "content": "<p>I was visualizing the waypoints on the map and noticed a shift (on that map only). I just played with some values (above) until the waypoints looked like they lined up on the map.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1268970,
          "author_name": "tomooinubushi",
          "author_url": "",
          "post_date": "04/10/2021 02:26:14",
          "content": "<p>I see. Thanks!</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1269148,
          "author_name": "enric1296",
          "author_url": "",
          "post_date": "04/10/2021 08:10:46",
          "content": "<p>did you find any generic rule to move the waypoint to the correct position on image?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1269450,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "04/10/2021 14:41:04",
          "content": "<p>No, I tried a few things thinking I should be able to find exactly what the value should be, but couldn't make it match up - the values above are what I'm using now</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 1275131,
      "author_name": "mamasinkgs",
      "author_url": "",
      "post_date": "04/16/2021 01:18:02",
      "content": "<p>Chris, thanks for sharing your insights and adjustments to leverage the geojson file. I'm also working on this problem, because some grids are inside the shops, which looks strange to me. BTW, I sent a message to you using the contact system in kaggle! I would be happy if you could check the e-mail. 🙏</p>",
      "votes": null,
      "replies": [
        {
          "id": 1275153,
          "author_name": "chris62",
          "author_url": "",
          "post_date": "04/16/2021 02:21:07",
          "content": "<p>Yes, some grids appear inside shops but are supposed to be in the hallways (like the ones I mentioned above), though there are some that I believe are correctly inside the blue areas (like training path 5e15b007f4c3420006d5229f) - but I think those are rare, and most paths should never be inside the blue shops.</p>\n<p>[also, I responded to your email - let me know if that didn't go through!]</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1275248,
          "author_name": "mamasinkgs",
          "author_url": "",
          "post_date": "04/16/2021 05:58:52",
          "content": "<p>Yeah, I guess it would be one of the key in this competition. <br>\nThanks for the quick reply, I responded to the e-mail :)</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "1262582": "I believe the height values in the floor_info.json files for the floors on site 5d27075f03f801723c2e360f are incorrect - below are the adjustments I made to make the waypoints line up correctly with the image (these are approximate - it's difficult to tell exactly what they should be):\n\nThis is the only site I noticed this for (for sites that have test paths - I haven't checked the other sites)\n\nSite 5d27075f03f801723c2e360f\n\nFloor B1\n5d27075f03f801723c2e3618\n252.25002019023339 => 240.0\n\nFloor F1\n5d27075f03f801723c2e3611\n221.9711303099799 => 211\n\nFloor F2\n5d27075f03f801723c2e3614\n222.0824509676249 => 211\n\nFloor F3\n5d27075f03f801723c2e3610\n221.85980965595348 => 211\n\nFloor F4\n5d27075f03f801723c2e3612\n221.85980965595348 => 211.0\n\nFloor F5\n5d27075f03f801723c2e3613\n142.6008283613404 => 135.3\n\nFloor F6\n5d27075f03f801723c2e3615\n142.48950770731392 => 135.3\n\nFloor F7\n5d27075f03f801723c2e3619\n142.48950770731392 => 135.3",
    "1262584": "Oh, and it's also possible that it's the image that is actually not correct, but the image didn't look distorted to me; but I'm not 100% sure :)",
    "1262596": "Look at my post, is related https://www.kaggle.com/c/indoor-location-navigation/discussion/230379",
    "1262601": "Ah, interesting - yep! it looks like that could be a similar issue (I haven't looked at that site yet)",
    "1268590": "I wonder what will happen if you use snap to grid method with your scaling values. The LB score get better or worse?",
    "1268666": "I don't think it would affect it because (I think) this only matters if you're converting between image pixels and meters. (so if you aren't using the images, then it shouldn't matter). \n\nI believe the waypoint x,y values (used for snap to grid) are independent of this (could be wrong though!)",
    "1268950": "I agree with you. The test labels would be consistent with train waypoints. \n\nDo you find any specific rules (e.g., ratio) of the distortion? Are true height values always smaller?",
    "1268960": "I was visualizing the waypoints on the map and noticed a shift (on that map only). I just played with some values (above) until the waypoints looked like they lined up on the map.",
    "1268970": "I see. Thanks!",
    "1269148": "did you find any generic rule to move the waypoint to the correct position on image?",
    "1269450": "No, I tried a few things thinking I should be able to find exactly what the value should be, but couldn't make it match up - the values above are what I'm using now",
    "1275131": "Chris, thanks for sharing your insights and adjustments to leverage the geojson file. I'm also working on this problem, because some grids are inside the shops, which looks strange to me. BTW, I sent a message to you using the contact system in kaggle! I would be happy if you could check the e-mail. 🙏",
    "1275153": "Yes, some grids appear inside shops but are supposed to be in the hallways (like the ones I mentioned above), though there are some that I believe are correctly inside the blue areas (like training path 5e15b007f4c3420006d5229f) - but I think those are rare, and most paths should never be inside the blue shops.\n\n[also, I responded to your email - let me know if that didn't go through!]",
    "1275248": "Yeah, I guess it would be one of the key in this competition. \nThanks for the quick reply, I responded to the e-mail :)",
    "1307883": "Thank you @chris62 for the insights. Have you found out whether it is actually the image or the height/width that is wrong?",
    "1307892": "I'm still not 100% sure where the issue actually is, but for the post processing I'm doing I think it doesn't matter - those adjusted site values seem to work. (because I'm matching to the floorplan image, so it doesn't matter if I scale the site or the image for that).\n\nIf you're using the site height/width values for something other than matching to the floorplan though (like the geo values), then I'm not sure, sorry!",
    "1307896": "Thank you for your reply :) I'll try to verify it somehow",
    "1307988": "It seems that one polygon's unit corresponds to 0.863 m (I have checked 4 floor-building pairs). This value is consistent with 5d27075f03f801723c2e360f's polygons and heights/widths."
  },
  "source": "meta"
}