windy-plugin-rnc | RNC Nautical Charts
-
Thank you for the contribution :)
I imagine that this plugin may create a lot of interest once the marine users become aware of it.
I look forward to future progress.
If you need some specific help then apart from the Windy developers there are also other plugin developers such as @rittels who may be able to provide some assistance too.
-
A Navionics layer would be great!
-
@undersampled
Are you sure Navionics will allow you to use Navionics tiles? If you can do this, then all sailors will cry for GPS positioning, which Navionics is unlikely to allow.
By the way, the Navionics viewer is free,
https://webapp.navionics.com/#boating@7&key=uy{lHpjxM
but the GPS positionning is only available through the paid app.The alternative solution would be to use OpenCPN which is an open source free chart software with GPS positioning.
https://opencpn.org/ -
A layer/plugin with data from www.openseamap.org would be nice indeed!
-
@justinlimbo Hello, try to test my new plugin: windy-plugin-openseamap (https://www.npmjs.com/package/windy-plugin-openseamap).
-
@mufac
I tried to load your plugin but not succeeded. What I made wrong?
-
@idefix37 Hello, try to set only plugin name: windy-plugin-openseamap, see picture
-
-
it works, but does not load the tiles:
There is an error fetching tiles:
GET https://tiles.openseamap.org/seamark/10/312/380.png net::ERR_CERT_AUTHORITY_INVALID -
@rittels
Thank you, now I know why. -
@idefix37 hello, site opensemap.org (source for nautical markers) is back up and running without errors. Try the plugin now.
-
@mufac
Thank you, I’ll try it as soon I’m back at home, on desktop. Now I can use only the mobile app and plugins are not available. -
works nicely, thanks @Mufac !
-
can this be added to the plugin menu to get faster access to the plugin?
-
@mufac
It works for me. This plugin is really interesting to see navigation marks at high zoom level.
-
as soon as I start the distance & planning tool, this plugin shuts off and all navigation aids are gone. is there a way to prevent this behaviour from the plugin side? or is this a "windy problem"?
