A campus map is more complex than just rows and columns. It contains a wide variety of complex structures, such as 0D models and coordinates. Simple SQL struggles to store this type of data on its own. The primary reason I chose this technology is that ORDBMS supports both tables and objects. On the one hand, it can store classic tables like student lists, and on the other hand, it can store complex structures. Another reason is that it helps us query location. Thanks to different extensions, we can ask the database location-based questions. For example, what events are taking place in the room on the right, how far is the stage from this room, etc. Once features like roads and streets within the map are entered into the system, it can query them almost without needing to change anything. This makes querying faster and saves us time. While SQL cannot process location data, NoSQL could not establish the connections between location and events. ORDMS is a perfect intermediate form.