@bdavenport,

Thanks for the responses!

The OSM config is for custom OSM tilesets, since there are many
different tile renderings (see
http://wiki.openstreetmap.org/wiki/Rendering for more info on this).
For example running "OsmTileUrlFormat =
'http://tile.stamen.com/toner-lite/{z}/{x}/{y}.png'" in the dev
console, changes the map immediately to use the toner-lite tileset
from maps.stamen.com.
The lastOsmX code is so the tilesource may be changed live, now from
browser developer console, and later thru the settings UI.

Also there is a more readable (without those indecipherable letter
variables and params) and more robust (working OK with old dump1090's
without many fields) version of the updVal code, in the "mods" branch
of my repo.

About the table, personally I like it, but if it got replaced with
something better than that's good :-) To speed it up (it is still slow
with many rows after applying the pull request), I was thinking of
reusing generated DOM nodes, and updating the rows themselves (keeping
a reference to a plane's row in each plane-object until ttl expired)
instead of generating the rows anew on every refresh.


On 6/2/14, Brian Davenport <notifications@github.com> wrote:
>> @@ -214,7 +249,7 @@ var planeObject = {
>>  					position: new google.maps.LatLng(this.latitude, this.longitude),
>>  					map: GoogleMap,
>>  					icon: this.funcGetIcon(),
>> -					visable: true
>> +					visible: true
>
> I really got to kick myself in the ass for this one.  Good catch!
> https://developers.google.com/maps/documentation/javascript/reference?csw=1#Data.StyleOptions
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/MalcolmRobb/dump1090/pull/18/files#r13309038