Page tree
Skip to end of metadata
Go to start of metadata

Real Estate algorithm is developed to identify specific demands of the customer in real estate category.

Following steps are covered

 

Introduction

Real Estate algorithm is developed to identify specific demands of the customer in real estate category.

The algorithm considers:

  1. Particular characteristics of the property (size, floor)
  2. Transaction type (sale, lease)
  3. Type of the property (residential, commercial)

Algorithm then specifies product recommendations based on this data.

Add Additional Parameters to Your XML-file

For the algorithm to work properly every product in your XML Product Feed should have additional properties:

  • Object size
  • Object type
  • transaction type

This data should be included into the XML-file in the form of specific product parameters and send to REES46.

Section <price>

Object price specified in this parameter is the price of 1 square meter of the object (for more information about the basic parameter <price>, see XML Product Feed)

Section <location>

Linking to a specific geographic location is done inside the <locations> section (for more information about the basic parameter <location>, see XML Product Feed). 

IMPORTANT

Do not try to set the price of the real property in the <location> section! 

 

Section <realty>

A distinctive real property feature is the presence of the <realty> subsection inside the <offer>  section.

Add the following parameters to each product to your XML-File

Object Size

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>
...

Return to the top of the page Return to the main page

Table of Contents

  • No labels