Incorporate Support for Related Tables

[SESMAPS]

Description

Currently, MapStore offers a powerful platform for visualization and management of geospatial data. However, a feature that I believe would greatly enhance user experience is the ability to work with related tables. Related tables would be extremely useful when data doesn't have a direct spatial representation, but has a relationship through primary keys, foreign keys, or pivot tables. For example, in the case of cadastral data, we could have a layer of polygons representing land parcels, and a related table containing information about the owners of each parcel, using a primary key in the parcel layer and a foreign key in the owner table.

Some reasons why I believe this feature would be beneficial include:

• Enhances Data Integrity: Allows for associating complementary data to geospatial entities, maintaining data integrity and avoiding redundancy.
  

• Facilitates Analysis and Decision Making: With additional data available in related tables, users can perform deeper analysis and make informed decisions based on a more comprehensive understanding of the data.
  

• Adaptability to Different Scenarios: The ability to work with related tables offers flexibility for users to adapt MapStore to a wide range of scenarios and specific requirements. 
  

Origins of the Idea:

Description of the Feature of Related Tables in MapStore

This feature, which I came across in ArcGIS Online, allows for associating additional data that is related to the attributes of the main layer. This is useful when you have data linked to the main layer but not necessarily part of it.

What is a Related Table?
A related table is simply a table of attributes that is linked to a main feature layer through a common field, such as a unique identifier. This table can contain additional information that complements the data of the main layer.
Why Add a Related Table?
Adding a related table allows you to keep data organized and logically related. For example, you could have a main layer containing information about buildings, and a related table containing information about the owners of those buildings.
How to Add a Related Table in ArcGIS Online?
To add a related table in ArcGIS Online, follow these steps:

• Open ArcGIS Online and go to the feature layer item to which you want to add the related table.

• On the layer item page, go to the "Content" tab and click on "Show table".

• In the layer table, click on the dropdown menu next to the layer name and select "Manage related tables".

• In the window that appears, click on "Add related table".

• Select the table you want to relate to the main layer and specify the field to be used as the relationship key.

• Save the changes.

Technical Considerations:

To implement the functionality of related tables in MapStore, there are several aspects to consider regarding architecture and technical implementation. Here are some considerations:

1. Layers and Tables in the PostgreSQL Database and GeoServer:
   
    MapStore uses a combination of PostgreSQL/PostGIS databases and GeoServer to store and serve geospatial data.
    The implementation of related tables could leverage the existing structure in the PostgreSQL database, allowing for the creation of relationships between related tables and geospatial layers in GeoServer.
    GeoServer can be configured to access related tables and combine data from geospatial layers with data from related tables during the generation of WMS and WFS services.
   

2. Direct Implementation in MapStore:
   
    Another option is to implement the functionality of related tables directly in MapStore, without relying on GeoServer for the management of related data.
    This could involve creating an abstraction layer in MapStore that handles relationships between geospatial layers and related tables stored in the PostgreSQL database.
    MapStore could provide user interfaces for managing these relationships, allowing users to configure relationships and access related data directly from the MapStore interface.
   

3. Performance and Scalability Considerations:
   
    Regardless of the chosen implementation, it is important to consider the performance and scalability of the system.
    Accessing related data can have an impact on performance, especially if there is a large volume of data involved.
    Optimization strategies, such as the use of indexes in the database, query optimization, and caching, should be implemented to ensure optimal system performance.