Skip to main content
15 events
when toggle format what by license comment
Nov 9, 2017 at 3:28 vote accept davidtgq
Nov 9, 2017 at 3:25 vote accept davidtgq
Nov 9, 2017 at 3:26
Nov 9, 2017 at 0:28 comment added Evan Carroll @dtgq but that not the question here, the second this involves an api and not the DB it's on-topic on Stack Overflow but not here.
Nov 9, 2017 at 0:27 comment added Evan Carroll @dtgq most certainly. =) You need to be doing the calculations in whatever they're sending out, not the projection for the web interface.
Nov 9, 2017 at 0:05 comment added davidtgq In Nyxynyx's comment here gis.stackexchange.com/questions/56862/…, it says that Google's map visually uses 3857 while the API uses 4326 when interfacing with users. Is that true, and if so should I be using 4326 in my calculations?
Nov 8, 2017 at 23:46 history edited Evan Carroll CC BY-SA 3.0
deleted 3 characters in body
Nov 8, 2017 at 23:45 comment added Evan Carroll I think there is some confusion here. Google tends to give lat/long on EPSG:3857. It's not inaccurate (well, it is but that's just becaues it does so much). You need to keep all of your math on that projection of EPSG:3857. If you do, you can within reason get useful calculation. But longitude is going to be relative to the placement of the point on that projection. One degree of longitude will never be a measure of distance. Just look at a toy glove. Your pinky can touch all the lines in the right spot -- on Earth too.
Nov 8, 2017 at 23:42 comment added Evan Carroll What do you mean inaccuracy from Google?
Nov 8, 2017 at 23:40 history edited Evan Carroll CC BY-SA 3.0
added 35 characters in body
Nov 8, 2017 at 23:36 comment added davidtgq If the data is coming from Google Maps API, the inaccuracy from Google is inaccurate in the same way when given to Leaflet, so they cancel out and net result is that it should work without an SRID, right? The viewport gives two lat/lng pairs and so it should work with the data they give if I understand correctly.
Nov 8, 2017 at 23:31 history edited Evan Carroll CC BY-SA 3.0
added 85 characters in body
Nov 8, 2017 at 23:25 history edited Evan Carroll CC BY-SA 3.0
added 85 characters in body
Nov 8, 2017 at 23:19 history edited Evan Carroll CC BY-SA 3.0
added 85 characters in body
Nov 8, 2017 at 23:11 history edited Evan Carroll CC BY-SA 3.0
added 85 characters in body
Nov 8, 2017 at 23:05 history answered Evan Carroll CC BY-SA 3.0