17

Mobile devices use WGS84 coordinates, and the coordinates might be displayed in different formats. One of them is DDM format. A comma for separating degree and minute, a dot for decimal. Your coordinates look like in that format. DD: Decimal degrees. Ex: 38.2045 N DDM: Degrees decimal minutes. Ex: 38° 40.1365' N DMS: Degrees minutes seconds. Ex: 38° 40' 20&...


7

It looks like normal lat/lon: 38° 40.1365' N, 75° 04.23933’ W DD MM SS: 38°40'08.2"N, 75°04'14.4"W or Decimal Degrees: 38.668942, -75.070656


5

First, let's emphasis that it is a strange requirement... CRS and axis order are tightly coupled, so the clean solution is to export and load the data using the same CRS. That being said, you can create the (not anymore)Well-known-text using swapped coordinates using a virtual layer. Go the the menu layer / add layer / add-edit virtual layer and enter the ...


4

I think it is a typo and should correctly read like this: "Geographic coordinates are the earth's latitude and longitude system, ranging from 90 degrees south to 90 degrees north in latitude and 180 degrees west to 180 degrees east in longitude" Please note, The 180th meridian is one of the shames of geospatial technology. The story goes that ...


3

Your data is in a projected coordinated system, and your coordinates are perfectly normal not "odd" at all. Just reproject your geodataframe to a geographic CRS, e.g EPSG:4326 nc_counties = nc_counties.to_crs(4326) nc_counties['lon'] = nc_counties.centroid.x nc_counties['lat'] = nc_counties.centroid.y Note lat = y and lon = x, not the other way ...


1

working with QGIS 3.16.4-Hannover, here what worked for me after couple of hours: 39°15'44.856"E,21°35'41.815"N for some reason QGIS wasn't able to plot the geometry and only gave a table, in the above notation, limiting your decimals for the seconds -i used python "{.3f}".format(S)- was crucial -not necessary 3 places i tried up to 9 ...


Only top voted, non community-wiki answers of a minimum length are eligible