Opened 9 years ago

Last modified 6 years ago

#2007 new defect

v.to.db azimuth direction

Reported by: davidinosauro Owned by: grass-dev@…
Priority: trivial Milestone: 6.4.6
Component: Docs Version: unspecified
Keywords: v.to.db Cc:
CPU: Unspecified Platform: Unspecified

Description

Working for the first time with v.to.db and azimuth calculations, it took me a little while to figure out that angles are compute clockwise. I have no idea whether or not other GIS systems use this same convention, but in mathematics I have always used positive angles counter-clockwise.

I believe one line in the docs about this would not hurt and could improve a first-timer experience, even if this were a standard in GIS.

Davide

BTW, how is the doc-writing organized? Is there some pull-request system, so that I can patch it myself and let you just accept the changes?

Change History (4)

comment:1 in reply to:  description Changed 9 years ago by neteler

Fully agreed.

For text snippets: If you could write up the change and add it here (ideally) as "svn diff", it would be most easy to integrate. Or the full file starting from the current HTML code and we diff ourselves.

comment:2 Changed 9 years ago by hamish

v.to.db is a bit backward in this respect, elsewhere in grass the convention is always cartesian (theta CCW from the +x axis) not nautical (degrees CW from north). Without saying that one way is more appropriate than the other, I believe that for consistency v.to.db should be changed in trunk to match the rest.

I've been slowly adding options to modules to allow both, but default to cartesian:

      aspect_type   Direction map aspect type
                    options: cartesian,compass
                    default: cartesian

where cartesian = 90 - compass and vice versa. you can do that in db.execute to add the alternate convention into a new column.

and if v.to.db+azimuth doesn't already error-out in a lat/lon location, it should. (even if using geodesics, great circle azimuth has two diff't answers depending on which endpoint you use, and it transitions along the line)

patches for docs always welcome, Hamish

comment:3 Changed 7 years ago by neteler

It seems that explanations have been added (long time ago):

Can the ticket be closed?

comment:4 Changed 6 years ago by neteler

Milestone: 6.4.46.4.6
Note: See TracTickets for help on using tickets.