Closed cascading-jox closed 2 years ago
I noticed that this will happen if the mapper send the altitude value which is not a rounded integer (eg: float).
yes i'm having the same problem on a few hexagons. i noticed indeed the doc says altitude needs to be int
, but i assume it's easy for the mapper api to parseInt()
to fix incoming float values, and i hope the web interface can be fixed to deal with the incorrect data that got into the database?
Closing this as those hexes now load just fine. This was likely a discrepancy between what was loaded from the tileserver and what could be queried from the database.
I found a hexagon which when pressed throws the error TypeError: t[0] is undefined on firefox or TypeError: Cannot read property 'timestamp' of undefined on chrome. It is located at 58.405858, 15.628672.
https://user-images.githubusercontent.com/8418570/125160276-56008100-e17c-11eb-910d-c3b03249c66a.mp4