Use of static factory methods for vectors and matrices library
To put it simply, you're using the wrong language elements to achieve your goals.

The purpose of interfaces is to serve as a contract.
They define a set of actions that implementations must be able to perform.
Although Java 8 made it possible to add static and default methods to an interface (and I'll have to read up on why they did that),
it's best when an interface contains no implementation at all.
Before adding static or default methods,
think twice, and question yourself if there's a better way.

In this example,
it seems quite clear that all those createFrom* methods are in fact utility methods,
that would be best in a utility class.
There's no point putting them anywhere else if they cannot be extended or overridden.
So it would be better to extract these to a Vector2dUtils class or similar.

And why does a Vector2d extend Bufferable and Measurable?
What does that even mean?
It seems like this interface is trying to do too much.
I strongly suspect violations of the single responsibility principle in your implementation.


  
  the interface class knows about a specific implementation and can only return Vector2f instances, and
  


Why does an interface know about any implementations at all? It really shouldn't.


  
  a client expecting a Vector2d implementation class gets a Vector2f instead!
  


Why would a client expect a specific implementation from a method that returns an interface type? It really shouldn't.

You seem deeply confused. I recommend further reading on the subject:


In Effective Java by Joshua Bloch (in this order):


Item 19: Use interfaces only to define types
Item 17: Design and document for inheritance or else prohibit it
Item 18: Prefer interfaces to abstract classes
Item 16: Favor composition over inheritance

Consider a related pattern used by java.util.Collections (source code), in particular the facilities provided by methods like .emptyList, .unmodifiableList, .synchronizedList
Consider a related pattern used by java.util.EnumSet (source code), especially how its various factory methods create either RegularEnumSet or a JumboEnumSet depending on what is appropriate given the input params, and the client just doesn't need to know whatever is the actual implementation.