rob42

Looks like ec2.py gets `ec2_facts` rather than `ansible_facts`. To get `ansible_facts` I have to ssh to each host (via ansible) which fails as there are many different ssh keys for...

FYI my use case is to automate a scan of the AWS account and produce a reliable list of all hosts and groups for staff reference and for inventory.

See https://github.com/lorin/ansible-quickref/blob/master/ec2.rst#hostvars-from-ec2py-dynamic-inventory-script

More compliant with n2k or a better way to handle routes/tracks?. The big advantage of geoJson is the flexibility. It can be edited with std web tools, converted to/from useful...

@timmathews I implemented routes and tracks in freeboard-sk. I found the simplest way was to define a route as a geojson line feature that connected two waypoints. A route therefore...

For the route above I have two waypoints (Nelson, and Adele Is) and a complex line that avoids shallows, fish farms, and takes me through a pass to the anchorage...

Yes we should support both types, in fact a traditional route is actually an ordered list of simple (straight lines) geoJson routes. So possibly we need a way to store...

@tkurki the conceptual difference is that a route between two waypoints can be a wiggly line. This removes the need for hundreds of waypoints. That hugely simplifies the naming and...

Keep in mind that the signalk tree is only one representation of the data. Using the unix filesystem as a model see hard links: https://en.wikipedia.org/wiki/Hard_link So its possible to have...

Dont really know the answers, its one of those options we have to try out to understand better. The providers shouldnt need to know about other, and its not practical...