GIS discussion: Tables in OpenXdata for GIS

[Raghu Mittal]

Hi all

I have got the views on GIS. Now i need to start putting the system tables for GIS into OXD database, and write services for accessing data etc. 

For now, it is required to store 2 sets of data, 1 set containing all Views and the other containing all Datasets.

The Views will basically contain details like Name, Datasets in the view, Zoom of the map, Center location of the map - lat, lon.

The Dataset will contain Name, Form version Id of the form on which the query is created, sql query, GPS columns - lat, lon/combined gps question.

I basically want to discuss how the tables should be created and how the data for GIS will fit in as system tables in OpenXdata.

There are various options that I am considering:

1. Create 2 different tables, one for Views and one for Dataset.

2. Create a single GIS table which will contain all data as key-value pairs (something like Settings table)

3. Any other suggestion that somebody can think of

Regards

Raghu

[Dagmar Timler]

Hi Raghu

Thanks for raising this via the developers chat. I am sorry that I forgot to follow up on your previous meeting request on this topic.

The two options you gave both have advantages and disadvantages.

 1. This option creates tables that are easy to read and understand, but for other modules there could be a lot of new tables which could make the oxd database cluttered

 2. This option allows us to limit modules to one table, but these tables are more difficult to read.

I would say that we should choose option 1 and find some way to keep module tables together so we don't clutter the oxd database. The simplest option would be to prefix a module identifier to the table name.

I am interested to hear what others think.

Thanks

Dagmar

Raghu

--
You received this message because you are subscribed to the Google Groups "openXdata Developers" group.
To post to this group, send email to openxd...@googlegroups.com.
To unsubscribe from this group, send email to openxdata-de...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openxdata-dev?hl=en.

[Sarah Bird]

Hi,

From the semi-technical user / non-dev perspective. I would prefer Option 1. Two tables e.g. module_gis_views and module_gis_datasets. 

I think it's ok to have a long list of tables as long as they're well organized and clearly named like this. I am working with a new piece of open-source software lately. It has 288 tables in the DB. But it has rarely been a problem to find what I'm looking for when I need to dig in the back-end.

Best,

Bird

[Shashank Garg]

I also agree with Option 1: module_gis_views, module_gis_datasets.

Shashank

[Omar Ahmed]

Hi Raghu, 

I haven't been following the discussions related to GIS very closely so can't comment on whether Views and Datasets individually themselves but  by looking at it I would definitely go for Option1. 

Dagmar raised the issue of creating more tables but if individual tables are prefixed "module_modName_tableName" wouldn't this avoid the confusion? I have module development experience on OpenMRS (which has a highly modular architecture) and supports a lot of module development and they follow this convention without any confusion. My two cents.

Regards,

Omar 

Raghu

--

You received this message because you are subscribed to the Google Groups "openXdata Developers" group.
To post to this group, send email to openxd...@googlegroups.com.
To unsubscribe from this group, send email to openxdata-de...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openxdata-dev?hl=en.

--

______________________________________________________________
Omar Ahmed
Engineer,
 
Interactive Research and Development (IRD)
Suite 508, Ibrahim Trade Tower
Main Shahrah-e-Faisal
T: +92(21) 34327697
W: www.irdresearch.org

[Raghu Mittal]

Thanks Dagmar, Sarah, Shashank, Omar

I definitely like the idea of calling the tables - module_gis_views and module_gis_datasets. I will start creating the tables.

Regards

Raghu