Apartments.com Data: Unit Prices for 3,000 Buildings Every Day
A daily apartments.com feed for a US apartment locator: about 3,000 buildings from the client's own list, down to each unit's rent and floor plan.
Sahibinden at national scale: 226,000 plots in the first file
Each row is one listing, opened in full, with the fields in the order of the client's template. The first full Sahibinden file, 226,000 rows of land for sale, went to the client 25 days after the project start. Files of that size do not travel as attachments, so they went through a shared Google Drive folder. A second Sahibinden file followed. A third run then went through a listing of 280,000 to 290,000 plots, and its files went to our FTP.
HepsiEmlak: the same land from a second portal
When the client added HepsiEmlak, a first sample of 3,917 rows, land for sale in two provinces, went out within six days. The client marked up the file: columns to drop, columns it needed, and values to correct. Where a plot is listed by an agency, the file now carries the agency name and the agent's name in separate columns, and the listing owner in a column of its own.
The client also explained that HepsiEmlak shows land in three ways: for sale, offered in exchange for flats in a future building, and for rent. The last two are small, but the client wanted all three, so the file gained a listing type column. A new 200-row sample with all three types followed, and the full set of 86,200 rows was delivered three weeks after the request, in an FTP folder set up for the client.
KAKS and gabari: what may be built on the plot
On land, the value is in what may be built, and two values carry most of it: the floor area ratio, known in Turkey as KAKS, and the gabari, the height a building on the plot may reach. The client explained how to read the gabari, 3.50 for one storey and 9.50 for three, and singled it out as important.
The client's spreadsheet uses a comma as the decimal separator, and a gabari of 8.50 opened there as a date. So KAKS and gabari go into the file as text with a comma, as in 8,50, and no value changes on the way.
Sahibinden and HepsiEmlak files in UTF-8 JSON
The client asked for UTF-8 on both portals, so that Turkish letters such as ş, ğ and ı display correctly in its software. The HepsiEmlak file was re-issued in UTF-8, and the client confirmed the letters were right the same day. The earlier Sahibinden data did not need a new collection: within a day its 175,000 records went back as UTF-8 JSON.
What the client has now
The client has Turkish land listings from two portals: 226,000 Sahibinden plots in the first file, a third run over 280,000 to 290,000 listed plots, and 86,200 HepsiEmlak listings in three listing types, with KAKS and gabari and the agency, agent and owner in their own columns. The files open cleanly in Turkish.
See our Sahibinden scraper, our HepsiEmlak scraper and our real estate data scraping service; data can also come through our API or as a JSON feed. To scope a land or property collection of your own, contact our team.
