Add missing position_2d and geodetic_position_3d types

For many use cases where the user does not want to specify a height it is useful to have a position_2d data type.

Also we sometimes want to specify geodetic_position_3d, for example in order to distinguish between the top and bottom roads of a bridge.

Both should be added in the next iteration of the standard.