Zebo Technologies

RETS import for Wordpress Realtors

I’m pleased to annouce that I am working on a RETS import script.  Its almost finished.  It has taken a good deal of learning the nuances of the RETS server standards.  While I’m pleased with the data that RETS makes available, I’m quite disappointed in the RETS standard.  I had the false impression that RETS would simplify things in setting up sites regardless of city or realtor associations.

The problem I have always had with IDX is that each association decides what is in their feed.  The order of the fields and the names of the fields also changes per association.  This makes creating an import for a new client tedious unless we already have another client in that area.  I had hoped that RETS would standardize the naming of fields and get rid of the heavy customization that occurs per feed.

Unfortunately, it does not.   While RETS does make updating easier (we can update every 15 minutes now and only have to retrieve new/updated listings since we last updated), RETS still allows heavy customization.  The names of fields tend to be different per RETS Server provider and perhaps per association regardless of RETS vendor. (this remains to be seen, I will have to wait to see when I get more clients to work with)

An example of this.   RETS has a recommended standard name for a listing id.  It is called ListingID.  Albuquerque’s RETS follows this standard name.  Hawaii on the other hand calls it MLSNUM.   This is just one example. There are dozens of fields in the RETS database.  Of which only around 30 even have standard names.  The rest of the fields have been determined by the realtor association or the RETS provider. (not sure which)

What does this all mean?  It means that for every new client in an area where we have not scripted the import already, will have to have the data mapped from scratch.  In WPRL, I have used as many standard names for my variables as I have found so far.   So I am calling an mls number ListingID.  I have to map the data I import from RETS so that MLSNUM = ListingID.   A map has to be created for all the variables we wish to download.  (I have over 100 setup for the Hawaii residential property feed)

It likely means I will need to relook at my pricing sheet.  Setup of WPRL just isn’t going to get easier with RETS like I had hoped.  Looks like it will be getting more complicated as the RETS feed data will need to be carefully analyzed and mapped into WPRL data fields.

Regardless of all this, RETS importation is coming to WPRL.  This will let us meet the needs of many potential clients as the National Assocation of Realtors is pushing all Associations to provide RETS only by July 2009. (goodbye IDX, I will not miss thee)