Menu
▾
▴
#5 Location map error: tokenizer: expected digit or . after -
When viewing two close nodes such as http://www.brismesh.org/
db/view.php?nodeid=1600&peerid=2312 the location map (http://
www.brismesh.org/db/map2b.php?
s=2.8192821663351&w=350&h=350&n=6958191.9&e=495959.2&t[
1600]=X&t[2312]=o) produces an error message:
** MAP IMAGE NOT AVAILABLE **
line 27: tokenizer: expected digit or . after -
The network and terrain maps work OK.
Ian
Logged In: YES
user_id=1002972
Been looking into this one.
Have made the following observations (at least on the 3
nodes provided.
I refer to lines 274 to 290 or so. (I forgot to write the line
codes into my notes, so may be a line or 2 out.
What is mdist used for? Why generate a value for it around
line 274 just to modify it a little later.
ok,
Logged In: YES
user_id=1002972
Been looking into this one.
Have made the following observations (at least on the 3
nodes provided.
I refer to lines 274 to 290 or so. (I forgot to write the line
codes into my notes, so may be a line or 2 out.
What is mdist used for? Why generate a value for it around
line 274 just to modify it a little later.
ok, if we have specified a zoom value, it sets mdist to 0
(which will then be set to 20000 a little later). But if we don't
specify it, it'll either use 1 or our cookie value, but leave
mdist at whatever it was generated above.
In the case above, it's 31.036269105956.
This makes a major impact on the value of s, as you end up
with 2.8192... instead of a nice 0.56.
I couldn't workout what mdist is used for other than
generating the s, so don't know, but it appears as the bug
happens when s > 1
zoom=229 - generates error (s=1.001875)
zoom=228 - works (s=0.9975)
Food for thought.
Michael.