Zillow Explorer
Pricing
$30.00/month + usage
Zillow Explorer
💫 Scrape Zillow.com Homes
0.0 (0)
Pricing
$30.00/month + usage
11
Monthly users
23
Runs succeeded
99%
Last modified
6 months ago
Scrapes have different headers with same search parameters
I have been scraping different cities and MSA's. I change nothing but the locations and run the same scrape. The column headers for the scrapes sometimes add additional headers, making the data difficult to further parse.
What can we do about this. Is there a way to create a template for what headers I want that doesn't involve me going in a selecting the columns (headers) everytime? Why would this be adding (or subtracting) additional columns when I don't change anything in the scrape parameters?
Please help!
Thank you!
NoUturns
Please see attached exported scrapes, run within 10 minutes of each other. Notice that one has the "groupType" header and the other doesn't. Why is this?
NoUturns
IT appears the "groupType" is a "for rent" thing as its an apartmetn complex and has a for rent listing. Why is this? Can we get rid of this option? I am running "sold" scrapes right now and don't want for rent listings. Why did that slip in there?
cmpusa
I am experiencing the same issue. This does not allow for standard import mapping to a database as the headers can change at random.
Hello, sorry for the inconvenience. Please add dev_no_strip=1 to your input. example: { "location": "New York", "limit": 10, "dev_no_strip": 1 }
Explanation: This actor normally will remove any empty values (NULL, FALSE, empty array/object and empty string) from the results. This is done to save space and memory. But this will make number of columns inconsistent, from one run to another. dev_no_strip will disable this behavior, and will keep empty values in datasets, so number of columns will consistent from 1 run to another. The dev_no_strip flag is hidden parameter and there is no UI for that (yet). I will soon update the actor UI to include this.
The "stripping" process is done before the results sent to Dataset Storage.
I hope this make sense. :)
Another way is to "re-shape" the dataset using dev_transform_enable and dev_transform_fields
cmpusa
@cat(Jupri) thanks for the suggestions. I'm definitely going to try the custom fields...would save a little time shaping the output file.
cmpusa
Update...the Custom Field option worked perfectly for me. I now have a standardized output file to be imported to our internal systems. Thank you.
Pricing
Pricing model
RentalTo use this Actor, you have to pay a monthly rental fee to the developer. The rent is subtracted from your prepaid usage every month after the free trial period. You also pay for the Apify platform usage.
Free trial
7 days
Price
$30.00
