Tiered property structure

for vacation rentals specifically, would be nice to have a 'tiered' or 'treed' structure whereby any property could be part of another property which is part of another property which is part of another property, etc etc etc.

for example 'Buffalo Lodge - unit 8401' is part of 'Buffalo Lodge' which is part of 'River Run Village' which is part of 'Keystone Resort'. or '2843 Palm Way' is part of 'Windsor Palms Resort' which is part of 'Disney Area Resorts' which is part of 'Orlando Florida'. Note that OSCalendar Rooms could also be implemented this way with 'Queen room' being part of 'Holiday Inn' which is part of 'Disney Area Hotels' which is part of 'Orlando FL. It could always end in a 'city' being the highest level.

You can get a start on this function currently by adding an extra field 'property_is_part_of' that points to the id of the next larger item. so if Buffalo Lodge (a building) is property 100, the property_is_part_of for the property buffalo lodge unit 8401 would be 100. then you have to write custom code to show the linkage. so it would be a start to add an extra field that is a selection list of available properties (or a dropdown list extra field which uses an SQL statement to fill the options... which would have many other uses...)

would be nice to have this tiered structure (either a fixed 4 levels, or an unlimited structure) be a native part of osproperty.

this is needed for vacation rentals because just 'city' isn't enough distinction when all of the rental properties are in the same city.

Hi Barry,
You idea is very good, when we designed the location structure. We had thought about this. But when we saw the cities list of countries, we felt they are really huge. So we decided not add child level of location (after city). I am sure this is the issue that we need to find solution in future.
Thanks
Dam

suggestion: adopt something like on jomestate.comdev.eu/ (see their backend demo and select components->jomestate->address)

they have an 'address' section where you can set up any tiered/tree structure you like. whatever makes sense for your location/market. it's done much like menus in joomla are where you can build a list of things with sub-things and sub-sub-things. so it can be country->city like osproperty has. but it can also be country->city->village->neighborhood->building->property or just start with village (if you only sell or rent properties in that village so country and city are irrelevant to your use-case). then when you're in the property, under address you select the top level (country for example) and an ajax list of choices for the next level is created for you, and on and on as you get more and more detailed in your location of the property. it's ingenious...

all of the extensive data in your current country->city structure would still be able to be loaded and used in the new structure so migration would not have to be done.

Hi Barry,
That's good feature from Jomestate, but in that case, we won't be able to import location. But that solution is proriety with small Real estate, and you can use it for one city or one state.
Come back to OS Property, with huge country as US, we have a lot of cities. If administrator need deeper location levels like districts, villages... i believe he won't have enough time to enter those data for a huge cities, and of course we aren't also provide the details location with districts, village... (in .txt file) of those countries too.
In future, we will try to find solution for this problem, maybe we will add the part that allow administrator to manage deeper location level (Bellow cities)
Thanks
Dam