Mapping package: Difference between revisions

Jump to navigation Jump to search
382 bytes added ,  24 March 2017
(3 intermediate revisions by 3 users not shown)
Line 9: Line 9:
* Add more options to mapshow.
* Add more options to mapshow.
* Implement support for projections. I (current mapping pkg maintainer) have little need nor much experience with this subject => help welcome!
* Implement support for projections. I (current mapping pkg maintainer) have little need nor much experience with this subject => help welcome!
* Add geodesy functions. Patches have been submitted but not yet integrated.
* Add geodesy functions. Patches have been submitted but not yet integrated. A suggested roadmap would be to integrate Felipe Nievinsky's geodesy toolbox as an upstream dependency but that toolbox needs documentation work.


Several functions in the current mapping package release (1.2.1) haven't had much testing. Please try them out and report issues in the bug tracker with "[OF] mapping pkg:" tag in the title.
Several functions in the current mapping package release (1.2.1) haven't had much testing. Please try them out and report issues in the bug tracker with "[OF] mapping pkg:" tag in the title.
Line 17: Line 17:


As a number of polygon functions in the mapping package relate to geometry stuff, chances are that some of that lacking functionality is already present in the [http://wiki.octave.org/Geometry_package geometry package]. In fact there is a discussion about which functions belong where. Matlab compatibility suggests the mapping package, but based on similar functionality the geometry package might also be a good home.
As a number of polygon functions in the mapping package relate to geometry stuff, chances are that some of that lacking functionality is already present in the [http://wiki.octave.org/Geometry_package geometry package]. In fact there is a discussion about which functions belong where. Matlab compatibility suggests the mapping package, but based on similar functionality the geometry package might also be a good home.
Recent mapping toolbox versions are classdef-based. It is unclear yet if we need to follow this route as classdef support in Octave is still experimental and has no file I/O.


{{Note|this entire section is about current version 1.2.1. If a Matlab function is missing from the list and does not appear on the current release of the package, confirm that is also missing in the [https://sourceforge.net/p/octave/mapping/development sources] before adding it.}}
{{Note|this entire section is about current version 1.2.1. If a Matlab function is missing from the list and does not appear on the current release of the package, confirm that is also missing in the [https://sourceforge.net/p/octave/mapping/development sources] before adding it.}}
Line 27: Line 29:
* aer2ned
* aer2ned
* angl2str
* angl2str
* antipode
* arcgridread '''[1]'''
* arcgridread '''[1]'''
* areaint
* areaint
Line 110: Line 111:
* globedem
* globedem
* globedems
* globedems
* gpxread
* gpxread '''[6]'''
* gradientm
* gradientm
* grid2image
* grid2image
Line 206: Line 207:
* quiver3m
* quiver3m
* quiverm
* quiverm
* rad2km
* rad2nm
* rad2nm
* rad2sm
* rad2sm
Line 300: Line 300:
* [4] ''See oc_polybool in the OF octclip package.''
* [4] ''See oc_polybool in the OF octclip package.''
* [5] ''See OF image package''
* [5] ''See OF image package''
* [6] ''There's a basic gpxread in the 1.2.2 version (to be released)


==== Grouped list ====
==== Grouped list ====
99

edits

Navigation menu