Degrees Minutes Seconds works:
code,latitude,longitude,feature1
point1,45 12 5.3634,25 38 6.6444,3
Decimal Degrees doesn't work:
code,latitude,longitude,feature1
point1,45.2014897,25.6351792,3
Any chance of being able to use decimal degrees without having to convert all my data?
Running Google Earth Pro 7.3.3.7786 (64-bit) on Linux.
When you import csv file, Google Earth asks you about the columns of the coordinates. Then it asks you about the format of all the columns/fields of your csv file. For your coordinates select text format. This is the solution.
Related
I have 16 netcdf files (without a time dimension) on a global scale that contain the same amount of longitude grid points (namely 432) and the same amount of latitude grid points (namely 324). Each netcdf file contains a slice of data, for example in file 1 there is a data slice from latitude range 90 to 80 and in file 2 there is data available from latitude range 80 to 70. I want to merge these files which each contain a different slice of data to obtain a complete global dataset.
I have tried to merge the netcdf files with cdo mergegrid as described in this answer https://stackoverflow.com/a/51566286/20668027 and that worked as far as I could see, however, when looking in the cdo guidelines it was stated that cdo mergegrid is only supported for rectilinear grids. The grid that I am using is not rectilinear but since it seemed to work on my data I was wondering if I could still use cdo mergegrid? Does anyone have insights about this?
Thank you very much in advance!
The NCO equivalent to CDO ensmean is nces described here. You could try
nces in*.nc out.nc
The Problem
I have downloaded the Master Stations Names File from the UK's Rail Delivery group.
I'm trying to map the dataset and would like to extract the locations. I tried using pyproj in my Python script, but the results are wrong.
The "Eastings" and "Northings" they provide don't seem to fit the National Grid. For example:
York station is given as "14596 64517". If these were epsg:27700, they would translate to -7.420284219986337 50.35401717940486, which is somewhere off the coast of Cornwall.
The documentation for the file says the following:
"Easting in units of 100m. Stations too far south
(Channel Islands) or too far north (Orkneys) or too far
west (west of Carrick on Shannon) have both their
Easting and Northing set to 00000. The most westerly
station in range, Carrick on Shannon, has value
10000. The most easterly station, Amsterdam, has
value 18690."
and
"Northing in units of 100m. Stations too far south
(Channel Islands) or too far north (Orkneys) or too far
west (west of Carrick on Shannon) have both their
Easting and Northing set to 00000.
The most
southerly station in range, Lizard (Bus), has value
60126. The most northerly station in range, Scrabster,
has value 69703."
but that still doesn't tell me the actual format they are in.
Google didn't help - I'm not even sure what to look for.
Question
What format are these coordinates in and how can I transform them into epsg:4326?
One would think that such a seemingly custom format would be better documented but there you go.
After much experimenting and playing with the coordinates given, I came up with the formula:
realEastings = (eastingsInData - 10000) * 100
realNorthings = (northingsInData - 60000) * 100
Why anyone would use this is beyond me, but hopefully this post can be useful for somebody else.
I have a bunch of files with timestamps associated with x and y coordinates. Currently the format of the timestamps is the following:
2016-11-08T15:55:01.7802880+00:00
I need to convert these into manipulatable format, as for example in milliseconds using matlab. I do not wan´t to extract only the milliseconds in the timestamps (example: .780), I need the absolute duration in milliseconds.
Thanks in advance!
Cheers
I'm sure there's a way to convert it with Matlab functions, but I've used this for the past little while.
Gets the job done.
ISO8601toserial.m File Exchange
I have been trying to covert Easting and Northing values to lat/lon using JCoord and GeoTools. Problem is I am getting different results for each library using the same Easting & Northing.
The code I am using is the code provided in the main answer and GeoTools answer provided in this question.
convert latitude and longitude to northing and easting in java?
The easting I am using is : 393339
The Northing I am using is : 806179
The coordinates Jcoord is providing are (57.14645296506957, -2.111698674790966)
The coordinates GeoTools is providing are [57.146449494619105, 2.111714868502565]
They seem to lose accuracy around the 4th digit and I'm wondering which one is right??
Thanks
Assuming that these are OS Eastings and Northings (which seems likely based on your lat/lon values) then they are accurate to 1m (as 6 figure grid references). Based on the values given by this calculator a degree of latitude is around 100 km so the 4th decimal point is roughly 10m or about the accuracy you can expect.
To get more precision out of the calculation you need to make sure of the ToWGS84 parameters being used in each calculation - for GeoTools you can query the projection to find this value, I expect JCoord has a similar operation.
Note in GeoTools the towgs parameter may vary depending on which referencing factory you are using, I believe that gt-epsg-hsql is more accurate than the gt-epsg-wkt.
I've been trying to use MATPOWER to do a power flow analysis for a network i have but all the outputs are coming with only 2 decimal places. Is there a way to configure the output to have the long format?
Trota,
You can modify the number of decimal places printed on screen or forwarded to the output text file.
If you browse the printpf.m file, simply change the required %9.xf to the required number of decimal places, where x is the number of digits after the decimal point. For bus data, these can be found at line 412 onwards.
Hope this helps.
You cannot change the number of decimal places used in the pretty-printed output of MATPOWER, but all of the results are available in full precision in the results struct returned by runpf() or runopf(). You can display these results with whatever precision you choose using standard Matlab commands such as disp() or fprintf().