radmon.org to-do list 25/9/2018

Yes, that is the lowest I'm prepared to go for the submission period. Otherwise server has to deal with lots of rq/s if everyone decides that 4 seconds submission period is a good idea.

Ok, bringing it back to to-do

- RadLog 100% done? This will probably be V0.43 Final unless there is another major bug found.
- OSM numbercrunching. This fell over about 2 weeks in. Not sure if server actually froze or watchdog timer in BIOS trigger happy, let's say the filesystem was *very* busy and system responsiveness was nil. radmon.org moved onto this hardware just recently and was installed in the desired location. So this may restart, at a reduced intensity. Not a showstopper, as I can use the public tile server for devleopment. And it can whirr away calculating for however long is necessary.
- OSM map. Got the map displaying and station data imported. Trying to get markers to show. Need to write routine to draw a nice marker like before. I can implement clustering, there is a good example to use in the API documentation. However I am undecided that it is a good thing. Clustering hides stations in alert. I may choose, at low zooms to implement coloured dots which then turn into numbered markers when you zoom in some more. Got to crack this annoying markers not displaying problem first.
- Implement php function call to draw custom radmon.org maps at specified zoom/location/mode for webmasters
- Import pre-hack radiation data
- Get Bert490's interesting nuclear locations data put on map
- Get radioactive@home's stations back on the map (these are temporarily removed while website is restored new map is developed)