Prevent Marking Pins at 0,0

[milo-trujillo]

We occasionally get a rogue camera marked at latitude 0, longitude 0 (off the west coast of Africa). This could be a few things:

• Someone playing with our API and marking a camera there accidentally
• Some platform (probably some Android device) that returns 0,0 as a location before GPS is fully initialized

Assuming it's the second problem then this is non-malicious behavior, but we should add an condition to either the client or the server to prevent sending the marking request if the location is 0,0.

--- Update ---

Confirmed - on Android the system will return 0,0 for a location if you're indoors and can't get a GPS signal. Not sure why they went that route instead of not giving a GPS ping.

Removing the iOS tag since it's an Android bug, and removing the server tag since the server now ignores pin markings at 0,0. Leaving the Android low-priority tag, since we should check client-side and not even make the request if we don't have a real GPS fix yet.

--- Second Update ---

Re-added server tag, since evidence suggests the server is not ignoring cameras marked at 0,0.