[GRASS-dev] Weekly report #6 - GRASS v.net front end

GRASS GIS GRASS GIS developer
1

Hello,

I am sorry to be late with my report. I wanted to wait for committing my changes into trunk (testing have taken me little bit more time than I expected) and report finally some real work, not just words as in previous reports.

1) What do I have completed this week?

Mostly I tested and tuned the changes, which were committed today ([1], [2], [3]).
More info about commited work can be found at [4].

2) What am I going to achieve for next week?

I am going to work on integration of v.net.path module to front end and also to work further on GCP Manager which shares lot of functionality with //the front end.

3) Is there any blocking issue?

No.

[1] https://trac.osgeo.org/grass/changeset/52255
[2] https://trac.osgeo.org/grass/changeset/52256 <https://trac.osgeo.org/grass/changeset/52255&gt;
[3] https://trac.osgeo.org/grass/changeset/52257 <https://trac.osgeo.org/grass/changeset/52255&gt;
[4] http://grass.osgeo.org/wiki/GRASS_GSoC_2012_WxGUI_front_end_for_vector_analysis_modules#Week_6_.28June_18.29

Regards,
Stepan

2

Štěpán wrote:

2) What am I going to achieve for next week?

I am going to work on integration of v.net.path module to
front end and also to work further on GCP Manager which
shares lot of functionality with //the front end.

Hi Štěpán,

re. http://grass.osgeo.org/grass-wiki/images/Interactive_inserting_of_coords_dialog.png

any chance to push selected points through G_format_easting()
and G_format_northing() libgis functions? (from ctypes interface)

No point reporting back coordinates to the micron when the GIS
knows for that location that it isn't needed, and the width of the
pixel the mouse selected covers some tens of meters. (and knowing
what is appropriate to use is why to use libgis instead of just
using %.3f throughout and assuming location is e.g. meters-based)

thanks,
Hamish