Home Release Notes

June 5, 2018 - Release Notes

1. Property Geocode Coordinates

Summary

The Property Details Payload will now include the Geolocation of the property if the corresponding Board/Association allows distribution of Geolocation information. However, even if a Board allows Geocode distribution, it is not guaranteed to be present for all listings.

Boards that allow distribution of Geolocation information will be listed here:
https://support.crea.ca/DDF#/discussion/57/which-boards-allow-distribution-of-property-geolocation

Modification Details

STANDARD-XML format

The Address element of the Property Details payload will indicate the geolocation of the property via the and child elements.

Example:

<Address>
  <StreetAddress>Lorem ipsum dolor sit a</StreetAddress>
  <AddressLine1>Lorem ipsum dolor sit a</AddressLine1>
  <City>Saskatoon</City>
  <Province>Saskatchewan</Province>
  <PostalCode>S7J</PostalCode>
  <Country>Canada</Country>
  <Neighbourhood>Lorem ipsum</Neighbourhood>
  <Longitude>-106.650000</Longitude>
  <Latitude>52.110000</Latitude>
</Address>

COMPACT format

The Property Details payload will indicate the geolocation of the property using two new columns: Longitude and Latitude.

Example:

<Columns> . . .    Longitude         Latitude    . . .<Columns>
<Data>        . . . -106.650000     52.110000  . . .<Data>

2. DDF® more frequent updates

Summary

Data distributed by DDF® will now be updated regularly throughout the day as CREA receives data from local Boards. CREA processes Board updates from 9am to 3am Eastern each day.

Modification Details

Clients do not need to make any code changes in relation to this service enhancement. To take advantage of it, CREA recommends the preferred strategy outlined below:

Preferred Strategy:

Do the following steps as frequently as required by your business model:

  1. Pull the Property Master List (using ID=*)
  2. Delete Properties from your Database if not present in the Master List
  3. Update properties in your Database whose LastUpated value does not match the one in the master list. You would need to do a Property Search Request on these properties to get their updated details.
  4. Add new properties to your Database. These are the ones present in the Master list and not in your database.

Alternate Strategy (for users doing LastUpdated Queries):

  1. Add a 30 min buffer to the time of your previous run when calculating the LastUpdated value for the Query. This buffer is required to account for the timing of the various data processing steps at CREA.

    For example, if you run your queries every hour on the hour:

    In the 9:00 am run, use 8:00 – 30min as your LastUpdated value in your Query: LastUpdated = 07:30am
    In the 10:00 am run, use 9:00 – 30min as your LastUpdated value in your Query: LastUpdated = 08:30am

  2. Schedule your LastUpdated queries as frequently as required by your business model.

Sign In or Register to comment.