I set the mercator projection in the namelist.wps of WPS, and set up 2 layers of nested areas. The latitude range of the first layer is -30~30, and the latitude range of the second layer is -20~20. But in the output wrfoutput file, The lat range in the d01 result is consistent with the setting, but the latitude range in the d02 file is displayed as -30~10°.
I have never encountered this problem.
I also checked the met*d02 file, and its latitude range is also -20~20, but There is a problem with running and playing WRF.exe.
The following is my namelist.wps and namelist.input, hope to get an answer, thank you.
namelist.wps
namelist.input
I carefully checked the domain area and the latitude range of the met* file and wrfinput* file and found that it is consistent with the set -20~20, but in the result after running wrf.exe, the lat range of the d02 output file becomes -30~10, only the lat range of the first moment is -20~20, and the others are -30~10.
Related
Location History data (downloaded from Google Takeout) is reporting incorrect Longitude on both the JSON and KML exports. Latitude is correct but Longitude is showing in the 304 to 305 range (after dividing by 107), instead of the negative number it should be in my case. It seems like the longitude data is simply "too high", by 430 (×107).
The problem shows in a JSON Location History I retrieved a few days ago; today I tried re-generating the downloads in both JSON and KML and both are still affected by this issue.
The same problem is reported by someone else here about 4 days ago but that's the only other mention of this issue I can find online.
Thoughts on how to proceed?
Found a solution: (no thanks to Google on this one!)
They seem to have an integer overflow error in preparing the data for
the takeout (downloading the kml directly from google maps for a
specific day works correct).
If the number is greater than 1800000000 (for latitude, also comparing
to 900000000 would work) you need to subtract 2^32 (=4294967296) and
you get the correct latitudeE7 or longitudeE7.
Example:
latitudeE7 = 4233738877 - 4294967296 = -61228419 (= 6.12 South)
longitudeE7 = 1066510714 (= 106.7 East, no conversion here)
we are using rethinkdb geospatial features to calculate distance between two latitude and longitude but the result returned by rethinkdb is different and looks wrong if i cross check on google maps or any distance calculator website. I have copied same code given rethinkdb help.
var point1 = r.point(-122.423246,37.779388);
var point2 = r.point(-117.220406,32.719464);
r.distance(point1, point2, {unit: 'km'})
// result returned
734.1252496021841 km
but when i test same point on http://www.onlineconversion.com/map_greatcircle_distance.htm it return following result 642.1854781517294 km.
Different from some other geo systems, RethinkDB uses the convention of having the longitude first, followed by the latitude.
We made that decision in order for being consistent with the GeoJSON format.
See http://www.rethinkdb.com/api/javascript/point/
From looking at your example, it looks like you've computed the distance correctly in RethinkDB, but entered the coordinates in the opposite direction in the online tool.
With latitude and longitude entered into the correct fields, I'm getting consistent results:
A more advanced note:
There is some difference behind the decimal point. The online calculator claims that "The script uses "Haversine" formula, which results in in approximations less than 1%." by which I assume it means up to 1% error, so this sort of deviation is to be expected.
RethinkDB uses geodesics on an ellipsoid for computing distances, based on the algorithm by C. F. F. Karney 1. This is an extremely precise algorithm, that calculates geodesics up to the limits of double-precision floating point numbers.
You will see even more deviation from Google maps (it gives me 735.234653 km for these two points). It looks like Google maps uses great-circle distances, which do not take the ellipsoidal shape of the earth into account at all.
1 http://link.springer.com/article/10.1007%2Fs00190-012-0578-z
How do I convert a Google maps link to GPS coordinates? (I think
10°11'12.0"N 13°14'15.0"E
is an example of a common GPS coordinate format.)
The reason I ask is that Google Maps for Android (I use Samsung Galaxy Note 3) does not seem to give coordinates. It will only give Google links. (Any instructions with right click can not be followed in a phone, only in a computer.)
For example. How do I convert the following link to find the coordinates of the Eiffel Tower:
http://goo.gl/maps/VqEsU
I think there have been earlier standards by Google where the hyperlink arguments contained the coordinates. But the current standard is more cryptic.
Right now I want to do it manually in my Android (Samsung Galaxy Note 3) phone. But maybe the question is of interest for programmatic conversion too.
Edit:
This question is NOT about the conversion between decimal and DMS (degrees, minutes, seconds) formats for coordinates. Many web pages and code-snippets are available for that.
You need to unshorten the url link, and the result will be and url with coordinates embedded in it. In your example:
https://www.google.com/maps/place/Eiffel+Tower/#48.8583701,2.2922926,17z/data=!3m1!4b1!4m2!3m1!1s0x0:0x8ddca9ee380ef7e0?hl=en
See this topic on how to unshorten using Python:
How can I unshorten a URL?
Then you need to parse it for the coordinates, for example by searching for the # character. Assume your long url is called longurl. In Python, you can do
import re
temp = re.search('#([0-9]?[0-9]\.[0-9]*),([0-9]?[0-9]\.[0-9]*)', longurl, re.DOTALL)
latitude = temp.groups()[0]
longitude = temp.groups()[1]
(Then you can further convert it from DD to minutes, seconds, if you need that.)
This link shows you how to convert coordinates from a Google Maps link (which is in DD, aka decimal degrees) into GPS coordinates (DMS - degrees, minutes, seconds). The general idea is to take the DD value and split it up into the degrees, minutes, and seconds values for latitude and longitude using the following process:
1) Take the integer value. This becomes the degrees.
2) Take the remaining decimal value and multiply it by 60. The integer portion of this value is the minutes.
3) Lastly, take the remaining decimal value and multiply it by 60 again. This is the seconds value (and is generally rounded off to 2 decimal points).
Example: 48.8583701, 2.2944813
Latitude: degrees = 48
0.8583701 * 60 = 51.502206 => minutes = 51
0.502206 * 60 = 30.13236 => seconds = 30.13
Latitude (DMS): 48º 51' 30.13" N
The link also has some code if you want to do it programmatically.
I need in WP 8 when a device be in the range of specific point (say 1km range) the application shown a toast notification tell me that am near this place.
You should fix a set of coordinates, latitude and longitude which is your specific point.
You have the position changed event for the geolocator which you can handle.
like here:: http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj247548(v=vs.105).aspx
Once you have that working, you can calculate distance between two locations as shown here,
Calculating Distance between two Latitude and Longitude GeoCoordinates
And you can show any pop up on the screen if you find that the distance is greater than or equal to 1km.
Hope that helps.
I have this file from tsp.gatech but the lat lng coordinate is divide into two half. Why is this?
COMMENT: Created July 7, 2012, www.tsp.gatech.edu/data/usa/
1 33613.158800 86118.306100
2 33100.954000 85529.675300
3 31571.835200 85250.489300
For example the first coordinate should be 33.613158800 86.118306100.
Update: I searched for New York City and I found it lat lng coordinate to be similar.
Update 2: I think it's incorrect formated see this image of points: http://www.tsp.gatech.edu/data/usa/img/usa115475_large.jpg. I get the points from a file from this website: http://www.tsp.gatech.edu/data/usa/index.html. The site is about a challenge and the file I downloaded is usa115475.tsp.
Euclidean Distance would tend to suggest the values are X,Y distances from a reference point (in feet, meters, kilometers, miles, ...). But this is normally reserved for small scale mapping where the effects of the curvature of the earth can be considered minor.
If the data seems to correspond to decimal degrees that are incorrectly formatted, there could be an error in whatever system is returning the data. But its better to review your own processes before pointing the finger. What query/process/code are you doing to obtain this data?