L.01

Poland Has the Data. Now We Need to Make It Intelligent

Using existing data resources for industrial location analysis

Poland already has a substantial body of data describing its territory, economy and investment environment. For many industrial location problems, the main obstacle is no longer the absence of data. It is the fragmentation of sources, uneven data quality and the difficulty of combining information collected for different purposes. This is precisely where GeoAI can add value: by bringing machine learning, text analysis and other computational methods into geospatial decision support.

The European Commission’s 2025 Open Data Maturity Report places Poland among Europe’s leading countries in overall open-data maturity.[1] The report is not a ranking of national GIS resources, so it should not be used as one. Its result is nevertheless consistent with what a review of Polish public datasets suggests: there is already a broad base of spatial, statistical, economic and administrative information that can support investment decisions.

The rest of this article looks at how these resources can be combined and analysed to answer practical questions about industrial location.

What data are already available?

The table below summarises the main data families relevant to industrial real estate and site selection. The distinction between public and commercial sources matters. Professional analysis rarely relies on open data alone.

GroupDataData formPublic availabilityTypical spatial detailMain public sourcesCommercial / directly acquired complement
Reference dataCadastral parcelsvectorYES / PARTIALparcelEGiB, Geoportalfull cadastral extracts, ownership information
Buildingsvector / 3DYES / PARTIALbuildingEGiB, BDOT10k, Geoportalenriched property databases
Administrative boundariesvectorYESadministrative unitPRG, GUGiK—
Address pointspointYESaddressPRG, EMUiA, GUGiKHERE, TomTom, Google
Terrain modelsraster / point cloudYESc. 1 m and locally finerNMT, NMPT, LiDAR, GUGiKcommissioned surveys and photogrammetry
OrthophotosrasterYEScommonly 5–10 cm, locally finerGUGiK, Geoportalcommissioned aerial surveys
Land cover and usevector / rasterYES / PARTIALobject / 10 m for Sentinel-2BDOT10k, Sentinelthematic commercial data
Road and rail networksnetwork / vectorYES / PARTIALnetwork segmentBDOT10k, OSM, infrastructure managersHERE, TomTom, PTV
Planning and legal statusLocal zoning plansvector / documentYES / PARTIALparcel / planning zoneUrban Register, BIP, municipalitiesaggregated planning databases
General plans and spatial policyvector / documentYES / PARTIALplanning zone / municipalityUrban Register, BIPplanning databases
Property ownershipregisterRESTRICTEDpropertyEGiB and EKW within legal access ruleslegal due diligence
Cadastral informationvector / tablePARTIALparcel / buildingEGiB, Geoportalofficial extracts
Permits and administrative decisionstable / document / locationYES / PARTIALproject / parcelRWDZ, BIPdevelopment databases
Environmental constraintsvector / documentYESparcel / zoneGDOŚ, Wody Polskie, PIG-PIB, GIOŚspecialist studies
Protected areasvectorYESarea / parcelGDOŚ—
Easements and other property rightsregister / documentRESTRICTEDpropertyland and mortgage registers where the register number is knownlegal due diligence
Development restrictionsderived dataPARTIALparcelplanning data, GDOŚ, Wody Polskie, PIG-PIB, heritage registersdevelopment due diligence
Transport and logisticsAccess to major roadsnetwork / vectorYESparcel–junction / road segmentGDDKiA, BDOT10k, OSMHERE, TomTom, PTV
Travel timesnetwork / time seriesPARTIALorigin–destination pairOSM, GDDKiA, local ITSHERE, TomTom, fleet data
Rail terminals and sidingspoint / linePARTIALfacilityUTK, PKP PLK, OSMlogistics databases
Portspoint / objectPARTIALport / terminalport authorities, GUS, OSMlogistics databases
Airportspoint / objectYESairportULC, BDOT10k, OSM—
Intermodal terminalspointPARTIALterminalUTK, OSM, operatorslogistics databases
Traffic and congestiontime series / network segmentsPARTIALroad segmentGDDKiA, local ITSTomTom, HERE
HGV restrictionsnetwork / attributePARTIALroad segmentroad authorities, OSMtruck-routing systems
Traffic countstable / point / segmentYESpoint / road segmentGDDKiA—
Route cost and pathderived dataPARTIALorigin–destination pairroad networks + public toll dataPTV, HERE, TomTom
Supplier and customer accessibilityderived / networkPARTIALcompany–facility / routebusiness registers + transport networkssupply-chain databases
UtilitiesPower networks and available capacitynetwork / tablePARTIALnetwork segment / connection pointGESUT, PSE, utilitiesdirect utility enquiries
Substationspoint / objectPARTIALfacilityPSE, GESUT, OSMutilities
Gas networksnetworkPARTIALnetwork segmentGESUT, GAZ-SYSTEMutilities
Water networksnetworkPARTIALnetwork segmentGESUT, municipal utilitiesutilities
Wastewater networksnetworkPARTIALnetwork segmentGESUT, municipal utilitiesutilities
Telecommunicationsnetwork / point / addressPARTIALaddress / network segmentinternet.gov.pl, SIDUSIS, GESUToperators
District heatingnetworkPARTIALnetwork segmentGESUT, URE, local operatorsoperators
Renewable-energy potentialraster / time seriesYES / PARTIALraster / locationIMGW, public meteorological dataSolargis and similar services
Environment and site conditionsElevation and sloperaster / point cloudYESc. 1 mNMT, LiDAR, GUGiKsite surveys
Geologyvector / profiles / boreholesYESdepends on sourcePIG-PIB, CBDGgeotechnical investigations
Groundwatervector / pointYES / PARTIALhydrogeological unit / boreholePIG-PIB, Wody Polskielocal investigations
Flood riskvector / rasterYESparcel / zoneWody Polskie—
Soil conditionsvector / mapPARTIALdepends on sourceIUNG, PIG-PIBgeotechnical investigations
Soil contaminationpoint / area / documentPARTIALproperty / areaGDOŚenvironmental site assessments
Noiseraster / contoursPARTIALlocalGIOŚ, municipalitiesmeasurements
Air qualitypoint / raster / time seriesYESstation / modelled rasterGIOŚ—
Natura 2000 and other protected areasvectorYESareaGDOŚ—
Climate and heat riskraster / time seriesYES / PARTIALraster / regionIMGW, public climate modelsspecialist risk databases
Population and labourPopulationtable / gridYESstatistical grid / municipalityGUS—
Labour supplytableYES / PARTIALmunicipality / countyGUScommercial labour analytics
UnemploymenttableYEScounty / regionGUS, labour offices—
WagestableYES / PARTIALcounty / regionGUSsalary surveys
Skills and occupationstablePARTIALregion / countyGUS, education and labour sourcesrecruitment databases and employer surveys
Commutingflow matrixYES, periodicallymunicipality–municipalityGUS, censusmobile-network data
Demographic structuretable / gridYESgrid / municipalityGUS—
Educationtable / pointYES / PARTIALinstitution / territorial unitGUS, education registers—
MigrationtableYES / PARTIALmunicipality / county / regionGUS—
Industrial real-estate marketExisting industrial and logistics stockpoint / object / tablePARTIALbuilding / parkEGiB, BDOT10k, OSM, market reportsREDD, brokers
Warehouse locationspoint / objectPARTIALbuildingOSM, BDOT10k, company websitesREDD, brokers
Building areasvector / tablePARTIALbuildingEGiB, building geometryowners, brokers
VacancytableNO at property levelbuilding / unitaggregate market reportsREDD, brokers
RentstablePARTIALmarket / propertymarket reportsbrokers, landlords
Transaction pricestable / objectYES / expandingtransaction / propertyRCNCenatorium, MSCI, brokers
Land asking pricestable / pointPARTIALlisting / parcellisting portalsportal analytics, brokers
Development pipelinetable / document / locationPARTIALproject / parcelRWDZ, company announcementsREDD, brokers
Take-up and absorptiontableNO at property levelmarket / parkaggregate reportsbrokers
Developers and ownerstable / relationship graphPARTIALentity / propertyKRS, CEIDG, company disclosurescommercial databases
Occupiers and tenantstable / pointPARTIALcompany / propertycompany announcements and websitesleasing and company databases
Business geographyCompany registerstableYESlegal entityCEIDG, REGON, KRSD&B, EMIS, Coface and others
Establishment locationspoint / addressPARTIALestablishment / addressREGON, CEIDG, company websitescommercial company databases
Industry classificationstableYEScompanyPKD, REGON, CEIDG, KRS—
Company employmenttablePARTIALcompany / territorial unitaggregated GUS datacompany databases
Financial informationtable / documentPARTIALcompanyKRS, company reportsEMIS, D&B and others
Suppliersrelationship graph / tableRESTRICTEDcompany relationshippublic procurement, company disclosuressupply-chain databases
Customersrelationship graph / tableRESTRICTEDcompany relationshipcompany disclosuressupply-chain databases
Industrial clustersderived dataPARTIALcluster / regioncompany registers + spatial datacommercial databases
Earth observationSentinelraster / time seriesYES10–60 m depending on bandCopernicus Data Space—
Landsatraster / time seriesYEScommonly 30 mUSGS / Landsat—
High-resolution commercial satellite imageryrasterNOsub-metre possible—Maxar, Planet, Airbus, ICEYE
Aerial imageryrasterPARTIALcentimetresGUGiK orthophotoscommissioned flights
LiDARpoint cloudYESpoint / objectGUGiKcommissioned surveys
Satellite SARraster / time seriesYES / PARTIALsensor dependentSentinel-1ICEYE, Capella
Movement of people and goodsMobile-network mobility dataflows / time seriesNO at useful detailaggregated zones—mobile operators
GPS tracestrajectoriesRESTRICTEDdevice / vehiclelimited research datasetsfleets, telematics
Floating-car / observed vehicle movement datatime series / networkRESTRICTEDroad segmentlocal ITSTomTom, HERE
Public-transport usagetable / time seriesPARTIALline / stopmunicipalities, GTFS, GUSoperators
Footfallpoint / time seriesPARTIALpoint / zonelocal countsmobile operators, retail analytics
Commutingflow matrixYES, periodicallymunicipality–municipalityGUStelecom data
Freight movementtable / flowsPARTIALcorridor / regionGUS, roads, rail, portslogistics and shipment data
Web and volunteered dataOpenStreetMapvector / networkYESobjectOSM—
Business directoriestable / pointPARTIALcompany / addressCEIDG, REGONcommercial directories
Websitestext / documentPARTIALpage / entitypublic webspecialist databases
Real-estate listingstext / table / pointvisible, usually not open in bulklistinglisting portalsportal analytics
POIspoint / vectorYES / PARTIALobjectOSM, WikidataHERE, TomTom, Foursquare, Google
Crowdsourced datavariouslicence dependentobjectOSM, Wikidata—
Location-linked documentsPlanning documentstext / vectorYES / PARTIALdocument / areaUrban Register, BIPplanning databases
Environmental decisionsdocument / locationPARTIALproject / parcelEkoportal, OOŚ database, RDOŚ, BIPdevelopment databases
Permitsdocument / locationYES / PARTIALproject / parcelRWDZdevelopment databases
Municipal strategiesdocumentPARTIALmunicipalityBIP, municipal websites—
Infrastructure plansdocument / mapPARTIALregion / networkPSE, GDDKiA, PKP PLK, GAZ-SYSTEMutilities
Company announcementstext / documentPARTIALcompany / projectESPI, EBI, company websitesbusiness-information databases
Investment and market reportsdocumentPARTIALmarket / regionPAIH, broker reportspaid reports and databases
Tender documentationdocumentYESprocedure / projecte-Zamówienia, BZP, TED—
Company dataPlant locationspoint / objectNO for internal dataplant—company records
Supplier and customer databasetable / relationship graphNOcompany / relationship—ERP, CRM, SRM
Shipments and transporttable / trajectoryNOshipment / route—TMS, WMS
Productiontime series / tableNOline / machine / job—MES, SCADA
Workforce and organisationtableNOemployee / team / plant—HRIS
Energy usetime seriesNOmeter / device / building—EMS, BMS
Operational KPIstime series / tableNOprocess / line / plant—company systems
CAPEXtableNOproject / asset—financial systems
Maintenancetable / time seriesNOasset—CMMS, EAM
Building and operationsBuilding geometry and information modelBIM / 3DNO for private assetsbuilding elementpublic 3D models only as contextBIM model supplied by investor or occupier
Room and equipment locationsBIM / point / objectNOroom / asset—BIM, as-built documentation
Asset registerstable / BIMNOasset—EAM, CMMS, BIM
Energy meterstime seriesNOmeter / asset—BMS, EMS, IoT
Environmental sensorstime seriesNOsensor / zone—BMS, IoT
Production sensorstime seriesNOmachine / line—MES, SCADA, IoT
Movement inside the facilitytrajectories / eventsNOperson / vehicle / zone—RFID, UWB, internal systems

The strongest part of Poland’s public-data base concerns the location and characteristics of physical objects: parcels, buildings, roads, terrain, environmental constraints and administrative divisions. As analysis moves closer to an actual business decision and plant operation, commercial and proprietary information becomes more important. Utility availability, lease terms, supply-chain relationships, freight flows and operational data often have to be obtained from companies, infrastructure operators, municipalities, landlords or specialist providers.

This is not a uniquely Polish weakness. Detailed information on actual utility capacity, rents, supply chains, shipment flows or plant operations is commercially sensitive or proprietary in most markets.

From maps to decision models

The same datasets can support very different levels of analysis. The simplest question is: what is located where? The next step is to combine layers and compare alternatives against explicit criteria. More advanced methods can identify recurring patterns, estimate values or classes, analyse relationships in networks and extract information automatically from documents.

In their systematic review of GeoAI, Siqin Wang and colleagues distinguish raster imagery, vector data, spatiotemporal flows, official statistics and text among the main data types used in the field. These data are used for tasks such as classification, prediction, simulation, automated feature extraction and geoparsing.[2]

This progression builds on established spatial decision-support methods. Jacek Malczewski described GIS-based multicriteria decision analysis as a way of combining geographical information with the evaluation of alternatives in order to produce information for decision-making.[3] GeoAI extends that toolbox with methods capable of learning patterns from large and heterogeneous datasets.

Figure 2. The evolution of spatial decision support, from GIS and multicriteria analysis to machine-learning methods.
Figure 2. The evolution of spatial decision support, from GIS and multicriteria analysis to machine-learning methods.

In their review of 149 industrial site-selection studies, Dongbo Wang and colleagues show that research is increasingly combining multicriteria decision-making, GIS and artificial intelligence.[4] One direction is the integration of imagery, text, vector data and sensor observations within a single analytical workflow. Another is the use of knowledge graphs to represent relationships among companies, sites and infrastructure, and graph neural networks to learn from those relationships. A further strand of research focuses on explainability: not only producing a ranking or prediction, but also showing why a model preferred one location over another.

One decision spans several spatial scales

Industrial location decisions should be assessed across several scales, from the regional context down to the individual property and its surroundings.

Figure 3. Regional, parcel and building-level data sources, and decision questions that require analysis across several scales.
Figure 3. Regional, parcel and building-level data sources, and decision questions that require analysis across several scales.

At the regional level, the main issues are labour availability, access to customers and suppliers, transport connections and local market conditions. At the parcel level, the analysis shifts to development rights, planning constraints, road access, utilities, terrain, environmental restrictions and room for future expansion. If an existing building is under consideration, the analysis must also determine whether its geometry, clear height, structural grid, building services and internal layout can accommodate the intended production process.

Some questions necessarily cut across these scales. “Where should we locate the new plant?” requires a regional comparison first and a property-level assessment second. An even broader decision is “Should we build a new facility, acquire an existing one or expand the current plant?”. That requires a simultaneous comparison of market and logistics conditions, parcel development potential and utility access, and the adaptability of existing buildings.

Location analysis, understood in this way, goes beyond producing a suitability map. Its purpose is to compare real investment alternatives.

Polish applications already exist

Marcin Hernes and colleagues provide a useful Polish example of combining real-estate information with spatial variables and machine learning. Their study used 148 transactions involving investment land in Wrocław. Transaction records were supplemented with information on zoning, development intensity, infrastructure, road access, public transport, distances, flood hazard and surrounding nuisances.[5]

The authors compared multiple regression, random forest and an artificial neural network. In this particular sample, the neural network achieved a mean absolute percentage error (MAPE) of 13%, compared with 22.2% for multiple regression and 26.3% for random forest.[6] This should not be interpreted as evidence that neural networks will always outperform other methods. The more important point is that combining market and spatial variables produced a useful analytical model, while the limited number of transactions remained a major constraint.[7]

The question for Poland is therefore no longer whether such analysis is technically possible. It is how to move from isolated experiments to repeatable workflows that combine public, commercial and company data.

Not only the West and China

Quantitative and spatial methods for facility location are not developing only in the United States, Western Europe and China. Serena Fugaro and Antonino Sgalambro reviewed 288 papers on multi-objective facility-location problems published between 2011 and 2025. Among the 143 studies that used case studies, Iran accounted for 23.0% and China for 22.7%, followed by Turkey and North America.[8]

The industrial site-selection literature also includes specific Iranian examples, such as wind-farm siting in Semnan Province and industrial site-selection studies in Isfahan.[9]

These figures should not be read as evidence that Iran has more operational deployments than Poland. Fugaro and Sgalambro note that many case studies are used to validate methods on realistic data rather than to document tools that have been implemented in day-to-day practice.[8] The comparison is nevertheless revealing: serious work on computational location analysis is being carried out across a much wider range of countries than the usual focus on the largest technology centres might suggest.

The data are here. The next task is to use them better.

Poland does not need to wait for a new generation of spatial-data infrastructure before developing GeoAI applications. Much of the necessary foundation already exists. The priority is to connect sources reliably, control data quality and build analytical workflows that translate those resources into answers to real investment questions.

GeoAI is one part of a broader decision-support toolbox. Depending on the problem, GIS, multicriteria analysis, operations research, statistics, network analysis, text processing and conventional modelling will remain equally important. The objective is not to apply artificial intelligence for its own sake. It is to make better decisions by combining the right data with the right methods.

The literature shows that this approach is developing not only in the United States, Western Europe and China, but also in countries such as Iran. The question is therefore no longer whether GeoAI can be applied to industrial site selection. The question is why Poland — with such a substantial public-data foundation already in place — should not become one of the countries where these methods are developed and used in practice.


References

  1. European Commission / data.europa.eu, 2025 Open Data Maturity Report. ↩
  2. Wang, S. et al., “Mapping the landscape and roadmap of geospatial artificial intelligence (GeoAI) in quantitative human geography: An extensive systematic review”, International Journal of Applied Earth Observation and Geoinformation, 128 (2024), 103734, p. 5. ↩
  3. Malczewski, J., “GIS-based multicriteria decision analysis: a survey of the literature”, International Journal of Geographical Information Science, 20(7) (2006), 703–726, pp. 703–704. ↩
  4. Wang, D., Zhu, Y., Mao, X., Wang, J., Ji, X., “Industrial Site Selection: Methodologies, Advances and Challenges”, Applied Sciences, 15 (2025), 11379, pp. 22–26. ↩
  5. Hernes, M., Tutak, P., Nadolny, M., Mazurek, A., “Real estate valuation using machine learning”, Procedia Computer Science, 246 (2024), 4592–4599, p. 4596. ↩
  6. Hernes, M. et al., ibid., pp. 4596–4597. ↩
  7. Hernes, M. et al., ibid., p. 4598. ↩
  8. Fugaro, S., Sgalambro, A., “Multi-Objective Facility Location Problems: Systematic Literature Review and research agenda”, Computers & Industrial Engineering, 216 (2026), 111994, p. 7 and the discussion of case-study use later in the paper. ↩
  9. Yousefi, H., Motlagh, S.G., Montazeri, M., “Multi-Criteria Decision-Making System for Wind Farm Site-Selection Using Geographic Information System (GIS): Case Study of Semnan Province, Iran”, Sustainability, 14 (2022), 7640; Reisi, M., Afzali, A., Aye, L., “Applications of analytical hierarchy process (AHP) and analytical network process (ANP) for industrial site selections in Isfahan, Iran”, Environmental Earth Sciences, 77 (2018), 537. ↩

Abbreviations used in the table

BIM — Building Information Modeling: a digital representation of building geometry and associated technical information.

BMS — Building Management System: a system used to monitor and control building services such as heating, ventilation, cooling, lighting and energy consumption.

IoT — Internet of Things: connected devices and sensors that automatically collect and transmit data.

MES — Manufacturing Execution System: software used to monitor and manage production execution at plant level.

SCADA — Supervisory Control and Data Acquisition: systems used to monitor, control and collect data from industrial processes.