We do run into the part that I didn’t touch upon, that if Skyhook can handle duplicate Mac
Addresses or not. If they can you would have to check the frequency they patrol an area before your MAC is back in the database – then you would have to change it again.

Also this is about routers and not about tracking laptops or phones – which would be a completely different discussion.

In theory my one AP is newer and prob. is not in the database, if my other API's are in the database it will probably say the wrong state depending on when they passed through – pre or post move to my current location.

Either way – I can change, I know how to change, and if I am inclined I can do it in under a minute.

What the real point of this article was everyone was going WAY overboard and overthinking this issue and solutions to remove their own AP's from teh database. If they don't like the database or have a grudge against, my solution is simple and sweet. The geo loc. data they get from your MAC is wrong – but like you pointed out if they want the information they can just walk down the street and pick up a different one.

There is no reason I have to be altruistic and give out my geo loc. information just because someone didn't buy a device with a GPS in it. That's really the issue though right? When geo location applications become more refined we will just be using GPS chips in all of our devices anyways? At that point the skyhook database should eventually die off. It's a stop gap until the GPS chip itself takes over.