<p><strong>Abstract.</strong> This paper explains the investigation carried out to understand NDCDB data handling within GIS applications. The method used was a case study replicated to five established GIS applications from different agencies, namely eKadasOnline, SKiP, iPlan, TM SmartMap and DBKL Interactive Portal. The case study was propositioned to the statements of; i) “<i>Such methods of applying NDCDB are because user understands its characteristics</i>”, and ii) “<i>such methods of applying NDCDB are because users know how to adopt it.</i>” Cross-case comparison analysis was then conducted to identify rival findings and explanation building. Based on the evidence of the multi-case study, it was concluded that such methods of adopting NDCDB by the GIS applications administrators and developers were because most of them have a partial understanding of the NDCDB characteristics which led to NDCDB being adopted based on the method that they think were suitable. Recommendations are highlighted in this paper to rectify knowledge-based mistakes found in this study, that included; i) ensuring the NDCDB’s cut-off-date; ii) utilises all existing NDCDB layers; iii) ensure to use the map projection parameters are the authorised and official value; iv) understand that the NDCDB utilises the GDM2000 datum with ITRF2000 epoch 2006; v) False Easting and North Easting can be discarded for geocentric datum; vi) adopting the built-in Geocentric Cassini map projection of GIS software is not advisable; and vii) obtaining relevant additional NDCDB layers. With the recommendations emplace, it is hoped the full potential of NDCDB can be tapped especially for multipurpose cadastre implementation including to ease spatial analysis. Data replication, exhaustion of resources, and reduce risks or costly investments made by decision makers, policy makers, developers or individuals can be avoided when NDCDB is fully optimised for spatial analysis.</p>