Closed philippjfr closed 8 years ago
Seems fine although I'm not sure how I feel about adding Geo
in front of class names. I understand it is to avoid confusion by naming new classes with identical names to those already used in HoloViews. On the other hand, I think that is what namespaces are for. :-)
This is a fairly general concern that isn't specific to this particular PR. I am happy to merge if you think it is ready.
On the other hand, I think that is what namespaces are for. :-)
Sure, although they are usually subclasses of their HoloViews equivalents so the HoloViews version would have to be imported as HvTextPlot
or something similar.
Also, yes it's ready.
Sure, although they are usually subclasses of their HoloViews equivalents so the HoloViews version would have to be imported as HvTextPlot or something similar.
That seems like the right approach to me if we believe the subclass offers all the original functionality of TextPlot
and more. Anyway, this is a tricky question with no obvious right answer so I won't let it stop me from merging this PR.
Adds an Element type to place Text annotations at a coordinate specified in an associated coordinate reference system. The GeoAnnotationPlot baseclass passes the coordinate reference system to the subclasses, which can apply the transform.
Here's an example in action, the text coordinates can be supplied in supported coordinate reference system: