This is perfectly normal behaviour in a transverse Mercator projection. The fact that a specific northing does not match a specific latitude (except for the Equator itself) can be easily visualized.
We are used to seeing global maps of the more familiar equatorial-aspect (or normal) Mercator projection, which depicts parallels and meridians as perfectly ...
The UTM zones and their respective EPSG codes cover the whole area of their respecive zone from the equator to 84N / 80S. These areas are subdivided by the letters from South to North, and these again are subdivided into 100km grid squares, but the projection system is not affected by these subdivisions. Hence for 29U you can use EPSG:32629.
For areas ...
Both coordinates are the same. As you are in the Southern Hemisphere a False Northing (of +10000000m) is usually applied to eliminate the negatives.
The utm package applies the false Northing by itself. For Proj you need to specify it:
>>> p = Proj(proj='utm', ellps='WGS84', zone='34H', south=True)
Simple. Don't use UTM projection if want to do some analysis on area falls under multiple UTM zones. You can use other projection in meters. LCC (Lambert Conformal Conic) is the official projection used in India. More information about LCC can be found here. There is also a comparison about commonly used projections in this pdf.
Since QGIS version 2.14, the '$area', '$length' and '$perimeter' options are calculated based on the unit settings defined under 'Project > Project Properties' (see the changelog as well as the description in the image below).
When you change the units in 'Measure Tool', it updates the values in 'Project Properties' and hence you are getting the output in ...
Imagine as if you were somewhere on Earth (easy to imagine I guess), and you have one world map on one hand and a compass on the other.
GRID NORTH: the map you are holding has probably some horizontal and vertical lines. The direction of every vertical line indicates the grid north. So, for every point on the map, the vertical line that passes through that ...
I worked on updating some USGS quads, back in the 90s. It seemed like most of the style guidelines were published internally, long before the Internet, and never made it online.
It's fairly common to show two sets of State Plane Coordinate System grid tics on quadrangles that are near a boundary between two zones. With UTM zones, it isn't such a big ...
There's the utm package, a bidirectional UTM-WGS84 converter for python.
It's able to convert a (latitude, longitude) tuple into an UTM coordinate:
>>> (395201.3103811303, 5673135.241182375, 32, 'U')
Also you can try using projfinder. For instance, when one paste provided coordinates (4581211.88, 5811848.94)
You will see several options. Then you may assume the CRS, which is mostlikely the "EPSG:31468 | DHDN / 3-degree Gauss-Kruger zone 4".
But in your case I will simply follow what @Erik explained.
And then answering your another question &...
To reproject a vector layer (or a batch of layers) (i.e. recalculate the coordinates values for a new reference system) you must go to Menu>Processing>Toolbox (this will open a side window). At processing toolbox search box, type 'reproject layer'. Choose 'reproject layer' algorithm from options bellow. A window will open:
Select the layer to be reprojected....
Following on Ian Turton's comment... Prior to performing ANY geometry calculations or analysis on a layer(s), the layer(s) MUST be 1) projected to the desired CRS, and 2) that CRS must be the same for all layers. (Sidenote #1: in QGIS, projecting a layer to a different CRS is typically accomplished using Save As...)
Your analysis will always fail if the ...
It says right there in your column title "GK4" - which is for Gauss-Krüger Zone 4 (https://epsg.io/31468).
Another hint is the leading 4 on the X-coordinates.
An last but not least you should know where the data should be situated and thus reduce the CRS-options.
The best way I can think is to get two UTM points, convert them to Lat/Long, and compare their geodesic distances to their UTM pythagorean distance.
E.g. Take a point from this example:
The CN Tower is ... in UTM zone 17, and the grid position is 630084m east, 4833438m north.
So if we take A (17n 630084 4833438) and move it 30 km east, we get B (17n ...
I suggest to use UTM zone 35. The points fall inside the Zambia borders:
For UTM Zone 34 and 36, the points would be outside of the country, shifted horizontally into the next UTM zone.
The "Grid" could be some local kilometer-wide grid for finding streets and places. It seems to be build from a Northing coordinate, "c" and an Easting coordinate in ...
If the extent of your map falls within 2 UTM zones, and you are required to use a UTM projection, you could either:
1) Choose the defined UTM zone that more of your map extent falls within. For example, if you are between zones 34N and 35N and more of your map coverage is on the 34N side, create your map in the standard EPSG 32634 and specify that this was ...
The answer depends on what you mean by "origin"
There are indeed 60 UTM zones numbered 1-60 and it starts at 180 W, so UTM zone 1 is used for longitude in [-180° -174°].
That being said, the origin of the center projection is located in the middle of the extent of each zone. The latitude of the center of projection remains 0 for all zones but the ...
As user30184 outlined:
It's a very common task, and there's plenty of documentation: ST_Transform.
To apply this, you need to figure out the EPSG codes of your projections.
UTM 35N probably is EPSG:32635, and your lat/lon coordinates could be anything. One of the more common ones is WGS84 as used in GPS with code EPSG:4326
The Postgis query then would be
Alright, the answer from Antonio above is definitely right and pointed me in the correct direction. Here is the complete code:
#convert_wgs_to_utm function, see https://stackoverflow.com/questions/40132542/get-a-cartesian-projection-accurate-around-a-lat-lng-pair
def convert_wgs_to_utm(lon, lat):
utm_band = str((math.floor((lon + 180) / 6 ) % 60) + 1)
No, you need 14N (N is for Northern Hemisphere). The "Q" is just a latitude band designation.
Latitude bands are not a part of UTM, but rather a part of the military grid reference system (MGRS). They are however sometimes used.
Each zone is segmented into 20 latitude bands. Each latitude band is 8 degrees high,...
You can't determine the projection of a set of points just from the coordinates. Without some other information they are just random numbers. Go back to the data supplier and make them give you some metadata.
If you know where the points are supposed to be then it may be possible to guess which projection they are in.
We use 4647 in Lower Saxony, too. As far as i know, 4647 and 25832 only differ in representation, that is 4647 stores with preceeding zone number, whereas 25832 doesnt. So 25832 coordinate xxxxxx is 32xxxxxx in 4647.
(Please note that some other EPSG codes for UTM32N, for example 5652, swich the N and E coordinates (thanks @Jens))
Your dataset should appear in QGIS with EPSG:5652. If not, use Set CRS for Layer to get it.
The 6-digit CRS is EPSG:25832. Rightclick on the layer, Save As ... under a different name and that CRS, and add it to the canvas.
It might be even enough if you just change the project CRS to EPSG:25832, leaving the dataset unchanged.
If you need high accuracy distances, or "ground" distances, you need to convert your UTM "grid" distances (which you do indeed calculate via pythagorous) using a combined scale factor. This removes the distortion introduced by the combination of (a) reducing the horizontal distance at its elevated (above the ellipsoid) position on the earth and (b) ...
No, because UTM coordinates are repeated in each zone. If the data was localized--only covered the eastern and western parts of two zones, you might be able to do it because you could segregate the values into the two zones. If you had 539594, 9071398 and 493840, 9198483 are these in the same zone or in zones 31 and 32 or 10 and 11?
Don't choose UTM, end of story. Many large countries choose a single sensible projection for some tasks. Victoria, a small state in my country was extremely foresighted in the late 90's and chose a Lambert Conformal Conic projection suitable for state-wide usage when they were undergoing a datum shift (ADG84/66 to GDA94), rather than hobble along with ...
You use a UTM zone when your area of interest fits completely within it or very nearly so. A UTM zone is not appropriate when your area of interest spans several zones such as in your case. A little overlap into a neighboring zone might be ok, but the further away from the zone you pick, the more distortion there will be and the more it matters. I found this ...