New answers tagged

0

For me; in the beginning TCX worked perfectly but suddenly the same thing happend to me so i tried this; after saving your .kml file from google earth, go to http://www.gpsvisualizer.com/elevation and load the file there. Click "Convert and Add Elevation," and output as a .gpx file. Download the link that it gives you and import that into TCX Converter. Do ...


0

You can use the Translate tool which allows you to convert input rasters into RGB by setting the Expand option and selecting RGB. You can find the tool from the menu bar: Raster > Conversion > Translate


2

Sorry for the long time to answer, I was on vacation. I am using the QGis 2.14 in portuguese, but i'll try to show you the steps with pics bellow. 1- click in save as 2- On the "save window" choose the option "inclui dimensao-z" in english is equal to "include Z data" i think.


0

First, Geoserver style (SLD) and data (KML) are totaly different. Import the KML file in Geoserver and later, create SLD file in the style editor or create style within the viewer (like Mapfishapp) and next, save the .sld file to get the sld easily without write within XML (more difficult to realize classification or other specific style when some system ...


1

Here is the answer I got back from NOAA. It's in the form of java code, and the order of parameters has to be inferred, but in case it proves useful to someone else here it is: public static final HTDP NAD83 = new HTDP(0.9910, -1.9072, -0.5129, 0, 0, 0, 1.25033e-7, 0.46785e-7, 0.56529e-7, 0.00258e-7, -0.03599e-7, -0.00153e-7, 0, 0, 1997); public static ...


2

That script is outdated. You can use the built in functionality of ArcGIS Desktop's ArcToolbox: http://desktop.arcgis.com/en/arcmap/latest/tools/conversion-toolbox/kml-to-layer.htm It's in the Conversion Tools toolbox, and then inside From KML.


2

Could you check ArcGIS help, which stated that This warning commonly occurs when the Extent or XYDomain environment settings have been previously set for a specific geographic area and the values were inadvertently used when running another tool.


1

from pyproj import Proj, transform P3857 = Proj(init='epsg:3857') P4326 = Proj(init='epsg:4326') x,y = transform(P4326, P3857, lon, lat)


1

afalciano has the right answer but wanted to include a variant usage of pyproj. It does require you know the proj4 string and is a tiny bit faster. import pyproj p = pyproj.Proj("+proj=merc +lon_0=0 +k=1 +x_0=0 +y_0=0 +a=6378137 +b=6378137 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs") lon, lat = p(x, y, inverse=True) print lat, lon


0

What about PDAL? There is a Python package here - https://pypi.python.org/pypi/PDAL/1.2.0. Here is an example from the command line documentation: pdal translate input.las output.txt


0

I think you may have used the wrong dimensions. Projected Coordinate systems usually take meters as units, and your point should be in the North of France (Lambert Nord, Lambert 1 has an additional shift of 1000000 Northing). If you enter coordinates in kilometers, they will end up at the origin of the projection, which is off the Atlantic Coast: So try ...


0

I believe there is a confusion between EPSG:27561 and EPSG:27571. Here are the differing parameters between the two: EPSG:27561 NTF (Paris) / Lambert Nord France False Northing: 200000 m EPSG:27571 NTF (Paris) / Lambert zone I False Northing: 1200000 m That would explain the differing latitude values. I think the online converters may be returning ...


3

No you cannot convert shapes located in map composer to a vector shapefile. You are simply adding graphic objects to a layout, which do not have any spatial reference nor a projection, so I don't think there is a way to do it inside composer.


3

You can use the rios (raster input/output simplification) module to read the columns of the RAT, giving you a numpy array which can be written to a csv col_names = rios.rat.getColumnNames(img) rat_values = [] for col in col_names: rat_values.append(rios.rat.readCoumn(img, col) Alternatively it will possibly be easier to create a gdal image directly ...


1

The help file for the feature vertices to points tool states that all original fields are kept. If the unique ID in your polyline happens to be the FID or OBJECTID then that will be lost. So a simple solution is to add a new field call it "PID" for polyline ID and copy over the FID/OBJECTID in your polyline dataset before you explode it into the individual ...


2

It seems you are running on windows. Simply double-click the laszip.exe program and operate it via the GUI. You can browse to the folder you want to decompress via the 'browse...' rollout on the left side of the menu. Why are you needing to decompress LAZ to LAS? Is there a software you want to use that does not support LAZ natively? Which one? Check this ...


1

For running LASzip from the command prompt window it is also necessary to specify the path of the input file. For example, suppose the laszip.exe file is installed under the drive D: (D:\LASzip\laszip.exe) and that the .laz files are stored in D:\lidar. Then, type: D:\LASzip\laszip D:\lidar\*.laz It will decompress all LAZ files in the current folder ...


0

If you're just using the smartphone GPS you probably do not need to worry about the conversion. The current difference between GDA94 and WGS84 is of the order of 1 metre, but you'd be unlikely to get a GPS location any more accurate than 4 metres in my experience. If differential GPS was being used however, it might matter. But if you are intent on ...



Top 50 recent answers are included