Hi,
Ășt 7. 8. 2018 v 6:22 odesĂlatel Pablo J. Zader napsal:
> "grass" Is it working well for "bionic"?
note that beside official package (GRASS 7.4.0) [1] there are fresh
packages (currently GRASS 7.4.1) available in Ubuntu Unstable PPA [2].
Ma
[1] https://packages.ubuntu.com/bionic/grass
[2]
I'm about to give up for today, but perhaps fresh eyes will see what I'm
not seeing.
Input data fragment:
name,lon,lat,elev,sampdate,prcp
Headworks Portland Water,2370575.38427211,199337.634652112,228,2005-01-01,0.59
Six fields comma separated.
Command:
v.in.ascii
On Fri, 10 Aug 2018, Helmut Kudrnovsky wrote:
shouldn't you re-project your vector data?
Helmut,
I just confirmed what I had observed before when importing lon/lat data:
an unusual location creation result.
Creating a new location specifying EPSG:4326 created the location, but did
not
On Fri, Aug 10, 2018 at 3:45 PM, Markus Neteler wrote:
> Hi Pablo,
>
> On Tue, Aug 7, 2018 at 6:22 AM, Pablo J. Zader
> wrote:> Hi list
> ...
> > What is the best combination of grass with ubuntu (16.04 LTS, 18.04 LTS)
> > today?
>
> While I am mostly on Fedora, we also have GRASS GIS running
On Fri, 10 Aug 2018, Helmut Kudrnovsky wrote:
how do you convert an attribute table from lat/lon to EPSG:2838?
shouldn't you re-project your vector data?
Helmut,
Perhaps I did not directly import the original data into the EPSG:2838
location. That makes sense.
Thanks,
Rich
Hi Pablo,
On Tue, Aug 7, 2018 at 6:22 AM, Pablo J. Zader
wrote:> Hi list
...
> What is the best combination of grass with ubuntu (16.04 LTS, 18.04 LTS)
> today?
While I am mostly on Fedora, we also have GRASS GIS running on Ubuntu 18.04.
Newer distro = newer packages (e.g. if you want ZSTD
>Convert attribute table lon/lat to EPSG 2838:
how do you convert an attribute table from lat/lon to EPSG:2838?
shouldn't you re-project your vector data?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
The precipitation file in my earlier thread replaced the lon/lat
coordinates with the projected coordinates after running v.to.db on the
table. Replacing the source table with one having two more columns (date and
precipitation amount) is failing the coordinate conversion somewhere, and I
fail
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
14 matches
Mail list logo