GRASS Location Wizard: Difference between revisions
Jump to navigation
Jump to search
(+category development) |
(+template OutDated) |
||
| Line 1: | Line 1: | ||
{{OutDated}} | |||
=== Development of a graphical Wizard to easily create locations === | === Development of a graphical Wizard to easily create locations === | ||
Revision as of 00:16, 13 April 2008
Development of a graphical Wizard to easily create locations
Background
It is a long standing problem for newcomers that locations can be only created in an ASCII based interface.
Idea
Write a graphical Wizard to easily create locations which leads the user through a dialog of:
- directory of GRASS database (option to create new directory if needed)
- name of location (avoid white spaces in name)
- name of mapset (default: PERMANENT)
- query for (non)projection:
- xy unreferenced data: rows, cols, xmin, xmax, ymin, ymax, default raster resolution
- lat/long: ellipsoid + geodetic datum (from list or EPSG code), W, N, E, S, default raster resolution
- UTM: ellipsoid + geodetic datum (from list or EPSG code), W, N, E, S, default raster resolution
- Other projections: ellipsoid + geodetic datum + lase easting/northing etc (from list or EPSG code), W, N, E, S, default raster resolution
Material
(please use 6.3-CVS-HEAD)
- the current GUI startup is in 'lib/init/gis_set.tcl'
- the EPSG file is browsable through 'lib/init/epsg_option.tcl[.in]'
- the needed parameters for each projection are defined in 'lib/gis/geo_init.c' (the ASCII location dialog follows this file to query the user)
- geodetic datums are here: 'lib/gis/datum*'
Python: a new SWIG based interface to GRASS' C functionality is in 'swig/python/'
Questions
- write in TclTk (maybe horrible) or Python (nicer, but extra dependency)?
