Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tip: how to find the lon/lat for your rectangles more easily #38

Open
edevnull opened this issue Aug 12, 2016 · 6 comments
Open

Tip: how to find the lon/lat for your rectangles more easily #38

edevnull opened this issue Aug 12, 2016 · 6 comments

Comments

@edevnull
Copy link

Use this google page: https://google-developers.appspot.com/maps/documentation/javascript/examples/full/rectangle-event

Then draw the rectangle and use the popup information to copy paste the lon/lat into the config.json

Example:

screen shot 2016-08-12 at 20 25 16

@Zentriert
Copy link

Man I spent over an hour last night making 6+ boxes perfect using latlong.net and viewWork.html, this would have made it a lot faster! I knew something like this much exist but I couldn't find it.

Much appreciate your posting it! Thank you.

@Damananth
Copy link

@edevnull Can someone explain why is there 2 lat1,long1,lat2,long2?

[lat1,long1, lat2,long2],
[lat1,long1, lat2,long2]

@Zentriert
Copy link

@Damananth because it's an example of using two locations.. two boxes.

I used six in my recent scan in order to scan three different areas I hunt in (a total of only ~1sqkm) instead of having to run separate scans and separate workers etc.

You don't need the comma if you're only doing one cord.

@fshy00
Copy link

fshy00 commented Aug 13, 2016

Since the posted version has NE and SW, whereas it seems this project prefers NW and SE, I whipped up a quick fiddle with the correct coordinates set, so you can copy paste directly rather than worrying about mixing the coordinates.

https://jsfiddle.net/fshy00/yfm1cvn9/3/

@subzerofun
Copy link

@edevnull i have bought an app only to mark my locations.... thanks for the tipp!

@RedSparr0w
Copy link

#45 would be useful for you guys and should be able to close this when merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants