Resourceset geometry should define object shape, but not visuals

[KvotheBloodless]

This is more of a feature request than an issue, depending on perspective.

Currently, using a resource provider with Freeboard, we are able to set some very basic style parameters to render the geometry of a resource, this is too restrictive to be able to provide good UX.

For example, consider 2 entirely unrelated object types both defined with a geometry of type point. It is only possible at this stage to display a small circle for each, at best with a different fill or stroke.

I would like to propose that the geometry define the location (point) or draw the outline (polygone etc...), and the style attributes be used instead to specify some kind of map marker. This example shows 3 point resources, each or a different type which is immediately clear to the user.

Possibly a generic map marker shape with the ability to change color and provide the SVG icon would be an excellent outcome.

[panaaj]

The style attributes supported in resource sets is intentionally minimal as to not skew the definition towards purely towards what OpenLayers can support.
An image is probably the best solution in this case but the challenge is that the image must be part of the Freeboard app distributable or a fully qualified path to a location accessible when running in the browser.

[KvotheBloodless]

Thanks Adrian.

So if we break this down, there are 2 things to consider.

• How can Freeboard's Resourceset protocol be extended so it is possible to specify an image to display instead of (or in addition to) the geometry?
• The only way I could think a resource provider could supply it's own images would be by registering as a webapp... which is not the intended use of the webapp framework. As you suggested, the alternative would be for Freeboard to supply a library of image icons to reference. What do you think?

[panaaj]

After sleeping on it, a common set of icons available to all apps IMHO would be an appropriate solution.

They could be made available at a common path e.g. /signalk/v2/api/resources/icons and deployed by a plugin which can be managed as a GitHub repo.

[tkurki]

Icons at a well known path would be a great idea imho! Don't know how complex we want to go, we can start with something very straightforward like just one size, scalable format = svg. Create a separate issue in server or specification?

[panaaj]

SignalK/signalk-server#1837

[KvotheBloodless]

@panaaj should this ticket be left open for the work to enable the Resourceset to specify the icon to use in Freeboard?