On Fri, 10 Aug 2018, Micha Silver wrote:
I was trying to point out that, regardless if the units are meters or
feet, when you transform to a different CRS, you change all three values
of the location, x,y and z. For example:
micha@TP480:~$ echo "35.3 30.8 -180" | cs2cs +init=epsg:4326 +to
On 08/10/2018 05:45 PM, Rich Shepard
wrote:
On
Fri, 10 Aug 2018, Micha Silver wrote:
If I understand, you have a vector of
points with x,y and z in the
attribute table, and you want to transform to some
On Fri, 10 Aug 2018, Micha Silver wrote:
Pardon for butting in...
Micha,
It was not a private conversation.
If I understand, you have a vector of points with x,y and z in the
attribute table, and you want to transform to some different coordinate
system, while also transforming the
Pardon for butting in...
On 08/10/2018 04:45 PM, Rich Shepard
wrote:
On
Thu, 9 Aug 2018, Daniel Victoria wrote:
Try using v.to.db to add the coordinates
of each point to the attribute
table and then export it
On Thu, 9 Aug 2018, Daniel Victoria wrote:
Try using v.to.db to add the coordinates of each point to the attribute
table and then export it using DB.out.ogr.
Daniel,
The points have an elevation -- in feet -- associated with the geographic
location. Is there a grass module that will
On Thu, 9 Aug 2018, Daniel Victoria wrote:
The lat/long coordinates you get from DB.out.ogr probably comes from your
vector attributes, which contains the old coordinates.
Daniel,
Yes, that's the source since db.out.ogr dumps the attribute table.
When you project the data in Grass, the
The lat/long coordinates you get from DB.out.ogr probably comes from your
vector attributes, which contains the old coordinates.
When you project the data in Grass, the coordinates in the vector geometry
are updated but the attribute table is not changed. Try using v.to.db to
add the coordinates
I have precipitation data for all stations within a county. The geographic
coordinates of the source are lon/lat. These were imported to a lon/lat
directory using v.in.ogr then reprojected (v.proj) to the standard state
projection (EPSG 2838).
I want to run spatial analyses on these data in
