The NRF Log Share site is finally back up!
http://www.entropiaminers.com/
Sorry for the delay; my host has provide excellent service until now, but I don't expect any further downtime as now it's own hosting plan!
Ok, so I upload a database that covers about ~2k finds, get the link, and it won't let me download it? Keeps saying the website doesn't exist, wth? Half the time I try to load any of the pages, it keeps telling me the website itself is down, or doesn't exist, or is an invalid URL, and when I use the key I got from the upload to go to the analysis part, nothing works - doesn't let me click anything (or it simply isn't reading my mouse clicks)...
Cool idea.
I R N00b miner (only started mining this week), have to get NRF and have a play, then make 100 claims.
Probably just add 100 useless (Tinys) to the pool.
Guess I am one of those leeches, but you can't start at the top
Valid Records: 4329 Invalid Records: 76 Duplicate Records: 0
Let's give it a whirl and +rep for initiative
Wow, 36,455 now!
How much longer til we find NRF becomes inoperable due to data overload?!
Seriously, I am thinking about ways to allow people to filter their results better. In the meantime, keep in mind that most database apps (i.e. Access or if you have your own MySQL database somewhere) easily import CSV so you can start filtering on your own before I'm able to provide something. Excel sort of works, but I find it tries to format the date fields and then won't format them back to anything NRF will use.
I also find that once I get the latest import loaded and a map populated with green dots, I can then make use of the Analysis pages to select a region of the map and get information about types, depths, and sizes much more quickly than trying to zoom in with NRF. In other words, try using NRF and the Analysis pages together.
GL! I hope everyone is finding some new spots. I certainly have.
cant seem to export my database, NRF crashes if i choose dateformat, but not if i use NRF-default, too big database ? it's currently at 24,4MB
Why not do this instead
Someone make a new and improved nrf which if you want it to, connects to the db and uploads your stuff automaticly etc
I'm guessing 'yes' it is the size.
Or maybe you've got some screwy dates that it chokes on when you try to use the 2nd date format.
I'm curious, are those all claims or do you record your misses too?
The only thing I can suggest in order to determine if it is a size issue is that you export your whole record set in the format that does not crash.... Export it as csv. Then open that file with notepad and hack it down to about 1/4th the size. Then reimport that back to NRF. Then try again and see if you still get errors. That should at least tell you if its a size thing.
24MB NRF log, wow, that's got my attention! Hope you can figure it out.
Yeah i record everything =)
Why dont you add support for unix time instead? a quick google gives me a couple of codesnippets for asp =)
Since many finders have radius with a decimal I would sugest the application shouldn't expect an integer value there.Line: 3 - Position: 250 - The 'radius' element is invalid - The value '54.5' is invalid according to its datatype 'http://www.w3.org/2001/XMLSchema:integer' - The string '54.5' is not a valid Integer value.
Bump for over 50k records!