For some reason, GatherMate_Data r199 / v1.57 is marked as Load on Demand, and I'm getting the following error from GatherMate r673 / v1.19 on login:
[2009/08/07 14:40:49-6140-x1]: GatherMate-v1.19\Config.lua:1055: Usage: GetAddon(name): 'name' - Cannot find an AceAddon 'GatherMate_Data'.
AceAddon-3.0-5 (Ace3):167: in function `GetAddon'
GatherMate-v1.19\Config.lua:1055: in function `CheckAutoImport'
GatherMate-v1.19\Config.lua:1029: in function <Interface\AddOns\GatherMate\Config.lua:1021>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher":9: in function <[string "safecall Dispatcher"]:5>
(tail call): ?:
AceAddon-3.0-5 (Ace3):502: in function `InitializeAddon'
AceAddon-3.0-5 (Ace3):614: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:607>
wowdb data scraper complete, and GatherMate_Data has been updated with that data. Please note however wowdb dosnt seem to have data for Isle of Qual'Danis If one of you with the curse client be so kind as to go farm up some nodes and upload it will be extracted Sunday during the weekly upload.
Going to grab the Curse client now. I know it's off-topic, but I'm disappointed to see that it's Windows-only.
Edit: Stupid thing is broken and won't log in. Oh well.
Edit 2: Looks like the Curse client linked on wowdb.com was an outdated version. I posted this on their forums and they corrected the link.
Also, it seems that the lack of Isle of Quel'Danas data is an issue with the site rather than a lack of data, as bloodberry bush locations are not being shown on a zone map either, despite the fact that the site records their existence. I submitted a bug report and got a reply stating that they're working on it.
Zangar marsh is messed up because wowhead is messed up, go look at the maps for it it all matches what you see in your screenshot.
Im going to try to add some additional boundry checks for wher eI know data should not be in an upcoming scraper release. Also are you sure you didnt filter out adamantite? Because it is definitly in the data extract
boundary checks would help, although i still think there is a lot of bogus data in the real area of the zone as well. I suppose that's not nearly as inconvenient though, since Routes does do clustering (it does taboo regions too but they take longer to set up).
Kagaro wrote the merging/import code, so yes, it is intended. This is because GatherMate_Data is a LoadOnDemand addon, and as such, only executes once on being loaded. Clicking the Import button causes LoadAddOn("GatherMate_Data").
The automatic import option merely checks the TOC file for the ## fields to determine its last revision number, if its newer than last import, then LoadAddon() it.
This is very different from Cartographer_Data, which loads every time, and overwrites every time, deleting any and all new nodes you find without warning.
That sounds odd, since you can do a merge import rather than just a replace import.
Just started using this addon and seems nice except typing /gathermate does nothing for me. The addon is installed correctly and the nodes show on my map but i can't seem to get to the options anyway i try.
An alternate way to get there is /ace3 and then select gathermate from the dropdown in the upper-left.
Wowhead's data, as shown on their own site, is perfectly reliable. If you look at something with a low number of nodes, like Black Lotus, you can see that those are actually spawn points; I know for a fact that Wowhead's Black Lotus data is accurate, because I've used it to farm Black Lotus with, and have at one time or another found a Black Lotus at each and every spot that Wowhead has marked. Even if you look at something with a high number of nodes, like Felweed, all of the nodes displayed on Wowhead are within the boundaries of any given map area.
The problem is that however Kagaro is scraping Wowhead, he's getting node data that Wowhead itself doesn't display. It's either that, or GatherMate is corrupting the data during the import process. I couldn't say for sure either way.
All I know is crap data is getting into GatherMate_Data somehow, or it did on the last update anyways. So either Wowhead removed it after the last update, or Wowhead doesn't display the crap data but lets it get scraped (may be an anti-scraping measure?), or something else went wrong.
Anaral: The problem is that he doesn't want to use GatherMate_Data's data for a particular zone. Instead, he wants to build his own map of nodes for that zone.
What I think would be cool is if, instead of scraping node data from unreliable sites, let GatherMate users upload their personally-collected node data so a site where it is then merged together into one database. How is this different than WoWHead, you ask? Well, you could then let users generate filtered data sets on the fly that, say, only include nodes that have been reported a minimum number of times to exclude noise.
in my experience, there seem to be far fewer locations that nodes typically appear
This is not a bug in many cases. What's happening is that Blizzard defines a whole bunch of potential spawn locations (nodes) for, say, herbs, but initially spawns herbs at only a fraction of those nodes. When a player collects the herb(s) from an active node, a new herb spawns at one of the other spawn locations (nodes) that didn't previously have an herb available.
Sites like WoWHead and addons like GatherMate allow users to record places where they've seen nodes, in hopes of finding all of the potential spawn points. This is useful because it allows you you to check them all to find which ones are currently active without looking in place where that herb (or whatever) would never spawn (and even better, it allows you to find an optimal route using Routes to check the known spawn points).