Hi,
2013/1/3 Robert Norris <rw_nor...@hotmail.com>
> >
> > I have only toyed with Viking until recently when I was OSM mapping a
> > feature (a wind turbine, as it happens) which I could not approach
> > directly.
> >
> > Instead, I did the obvious: I took a series of bearings with a compass
> > from waypoints that I created.
>
> Yeah, old skool!
> Pen, paper, ruler, magnetic compass, drawing compass, sextant...
>
+1 I liked that. :)
> I assume the feature is too new to appear on Bing aerial imagery.
>
>
> > The Viking ruler tool seemed the obvious way to locate the
> > best point where the bearings intersected. But it seems that it was not
>
> The original author of Viking noted many years ago (IIRC in the TODO.txt
> file) that having multiple rulers would be useful.
>
A probably simpler solution: what about adding bearing information between
to consecutive trackpoints while drawing a track? Currently, the track
length is displayed, but we can display any information.
Behaviour would be:
1) put all the waypoints
2) from each waypoint, draw a simple track (2 points)
2a) while searching the rigth place to click the second point of each
track, a tooltip display the bearing from previous trackpoint.
3) create (manually) a new waypoint where tracks intersect
This is probably not really precise as final waypoint is placed manually,
but can certainly be sufficient here.
> >
> > I suggest that the ruler tool should have the faciliy to create points,
> > perhaps waypoints, or indeed two node tracks (as construction lines),
> > in these circumstances - a right alt click or whatever, perhaps.
> >
> > That should be very easy to implement? And it would be extremely useful.
>
> Unfortunately IMHO it is not very easy in Viking.
>
> All the drawing is done in low level GTK drawing C API, and drawing new
> things on top of existing view needs careful management of each graphic
> layer drawn - especially for dynamic movement of the changing graphics.
>
> I can't find the right words to explain the difficulties, but I assume
> this sort of thing is much easier in higher level drawing APIs - such
> provided in Java Swing or MS C# libraries.
>
In my long todo list, I wish to evaluate the replacement of home made
drawing with a canvas library (see GooCanvas).
> I'd say this kind of thing would be more usefully implemented in JOSM as a
> plugin - almost surprising there isn't one yet (I can't find one).
>
+1
--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
