Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Additional Properties

Additional niches properties of products allow studying user preferences and calculating recommendations more accurately. This section describes allowing filling the product feed with niche features of real estate.


Realty

The "realty" element must be inside the "offer" element.

<offer ...>
    ...
    <realty>
        ...
    </realty>
</offer>



Price

The "price" element must be inside the "offer" element and have a value per unit area (1m², 1ft², etc).

<offer ...>
    ...
    <price>10.52</price>
</offer>


Space

Optional parameter <space>. Placed within the <offer> subsection, inside the <realty> section.

Consider the following table of possible values:

ValueMetric UnitsDescription
minSquare MeterMinimum size
maxSquare MeterMaximum size
finalSquare MeterExact size

NOTE

Metric units are always square meter, even if the object is a 30 hectares-wide ground area.


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<realty>
	    <space>
			<!-- Here can be set minimum and maximum object group size or precise size of a particular object -->
			<min>30</min>
			<max>100</max>
			<final>37</final>
		</space>
	</realty>
</offer>
...

Object Floor 

Optional parameter <floor>. Placed within the <offer> subsection, inside the <realty> section.

Consider the following table of available subparameters:

ParameterDescription
<current>Object floor
<total>Total number of floors in the building


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<realty>
	    <floor>
			<!-- Object floor -->
			<current>3</current>
			<!-- Total number of floor in the building -->
			<total>12</total>
		</floor>
	</realty>
</offer>
...

Transaction type 

Mandatory parameter <action>. Placed within the <offer> subsection, inside the <realty> section.

Consider the following table of possible values:

ValueDescription
rentFor lease
sale

For sale

If the same realty object is both on sale and lease simultaneously, XML-file should contain two separate objects, each having its own unique ID, and each specifying in the <offer> section the required type of action (sale, rent).


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<realty>
	    ...
		<action>sale</action>
	</realty>
</offer>
...

Type of Property

Mandatory parameter <type>. Placed within the <offer> subsection, inside the <realty> section.

Consider the following table of possible values:

ValueDescription
flatFlat
office

Office

warehouseWarehouse
landGround area


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<realty>
	    <type>flat</type>
	</realty>
</offer>
...

  • No labels