In the old days, all suppliers had geography searching only. It’s efficient in many respects, and inefficient in others. It’s best practice nowadays to support PropertyID searching. This allows, for example, cross-geography searches (e.g. search the 20 best luxury hotels in the world) rather than do 20 destination searches and throw away most of the results.
It also wouldn't be possible for iVectorOne to perform this geography hierarchy function, as not everyone has the same view of geography and carve up the world in different ways.
We do, however, provide you the supplier geography in the content feed. The assumption here is that you have a reservation system that you are connecting iVectorOne to, which has a concept of geography / geography hierachy that you will be able to map the iVectorOne property data to