A Survey of Methods and Input Data Types for House Price Prediction: Literature list

Open data API in a single place

Provided by Catholic University of Leuven

Get early access to A Survey of Methods and Input Data Types for House Price Prediction: Literature list API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.07.25 12:12
Created
2022.07.25
Available languages
English
Keywords
data mining, house price prediction, survey, spatial-temporal systems, regression, machine learning, literature review, geospatial data, real estate
Quality scoring

Dataset description

General file description This xlsx document contains the literature list that forms the basis of the paper 'A Survey of Methods and Input Data Types for House Price Prediction' by Geerts, M., vanden Broucke, S. and De Weerdt, J. The Excel document contains seven sheets, relating to the phases described in the survey. Phase3 This sheet contains the literature list for the end of Phase 2 and the start of Phase 3. It has 590 rows and 19 columns. Each row contains the citation information of one article. The columns describe the ID, Authors, Title, Year, Source title, Volume, Issue, DOI, ISSN, ISBN, PubMed, Publisher, Document Type, Language, Keywords, Link, Book DOI, Algorithmic (Title) and Algorithmic (Abstract). The latter two columns are used to indicate whether the articles describe an algorithmic approach to predict house prices based on the title and the abstract respectively. These two columns take the values 'Yes', 'No', and 'Maybe', and were completed during Phase 3. Phase4 This sheet contains the literature list for the end of Phase 3 and the start of Phase 4. It has 116 rows and 20 columns. Each row contains the citation information of one article. The columns describe the ID, Authors, Title, Year, Source title, Volume, Issue, DOI, ISSN, ISBN, PubMed, Publisher, Document Type, Language, Keywords, Link, Book DOI, Algorithmic (Title), Algorithmic (Abstract) and Reading. All columns are the same as in the first sheet, except for the three last columns. The columns Algorithmic (Title) and Algorithmic (Abstract) now only contain the value 'Yes' as only the articles that describe an algorithm are retained in Phase 3. The column Reading describes the outcome of Phase 4. This columns is empty if the article is retained in this phase and describes the reason if it is not retained. Phase4(end) This sheet contains the literature list for the end of Phase 4. It has 94 rows and 20 columns. Each row contains the citation information of one article. The columns describe the ID, Authors, Title, Year, Source title, Volume, Issue, DOI, ISSN, ISBN, PubMed, Publisher, Document Type, Language, Keywords, Link, Book DOI, Algorithmic (Title), Algorithmic (Abstract) and Reading. All columns are the same as in the second sheet. The column Reading is now empty because the articles that were not retained in Phase 4 are removed from the list. Data table This sheet contains a table of the literature at the end of Phase 4 with indications of input data types used in the articles, the data novelty score and the cluster that the articles belong to. It has 95 rows, where each row contains the information of one article, except the last 'Total' row. It contains 21 columns : ID: This is the same identifier as in the previous sheets. Column1: This is a new identifier, based on an ordering on year and author. Authors: Same as before. Title: Same as before. Year: Same as before. Structural, Temporal data, Socioeconomic, Environmental, POI, Basic spatial, Location, Eucl Distances, Adv Spatial, Network Distance, Topographical data, Graphs, Images, Text: These are the different input data types. The cell is filled with 'X' if the corresponding article is using the input data type described in the column name. Score: This column indicates the data novelty score, calculated as explained in the paper based on the sheet 'Rules Data novelty score'. Cluster: This column indicates the cluster number as explained in the Discussion section of the paper. Rules Data novelty score This sheet contains 15 rows, of which the first contains the titles, and two columns. The first columns contains the input data types as in the previous sheet and the second column contains the respective novelty scores. Model table This sheet contains a table of the literature at the end of Phase 4 with indications of model types used in the articles, the model novelty score and the cluster that the articles belong to. It has 95 rows, where each row contains the information of one article, except the last 'Total' row. It contains 21 columns : ID: Same as before. Column1: Same as before Authors: Same as before. Title: Same as before. Year: Same as before. MRA, Kriging, SEM, SVC, Time Series, FL, NN, DT, RF, GBT, SVM, ANN, (Other) Ensembles, DL: These are the different model types. The cell is filled with 'X' if the corresponding article is using the model type described in the column name. Score: This column indicates the model novelty score, calculated as explained in the paper based on the sheet 'Rules Model novelty score'. Cluster: This column indicates the cluster number as explained in the Discussion section of the paper. Rules Model novelty score This sheet contains 15 rows, of which the first contains the titles, and two columns. The first columns contains the model types as in the previous sheet and the second column contains the respective novelty scores.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks