Web Features Service (WFS)

The WFS is a standard by the OGC which will be used for the WCNS

• Quick summary in german: https://de.wikipedia.org/wiki/Web_Feature_Service
• same in english: https://en.wikipedia.org/wiki/Web_Feature_Service
• full secification by the OGC: http://www.opengeospatial.org/standards/wfs

Application structure

There are several different ways how to implement this. In the beginning I was preffering application structure v2 but after considering all the use cases I think the approach in v1 would be easier to handle all the different data and the implementation. Here we should make a decision before starting to do the coding.

v1 - Single data provider, data is cached

• Pro:
  • Performance optimized
  • All data in one location
  • Single data provider for apps
  • Central management von IDs possible
• Con:
  • Data is stored double
  • Additional platform required

v2 - Multiple data providers, data live

• Pro:
  • No additional platform required
  • Each platform is independent
• Con:
  • Load directly on DBs
  • Apps must ask multiple data providers

v3 - One data provider, data live

• Pro:
  • Single data provider for apps
• Con:
  • Extra platform required
  • Load directly on DBs

Component Description

Conversation

• In the grafics above I used the box manipulation and conversation. The basic idea for conversation is the following, we have two tables, one with the source data from the existing DB and one with the CDS. We have for example the data "200m Einstiegshoehe" coming from the DB and in CDS we want to store only 200, so we need a kind of "strip_first_nr" script. Another script could be 1:1, another convert_time etc.

Manipulation

• Manipulation could be used for state or country names when they are not in a standard form. We could have a mapping table and apply this mapping to get only standard data afterwards. This could be applied on more data fields if necessary.

Admin UI

As a backend to the webservice should be a UI to do at least the following tasks

• add new db source (host/user/pass, sql view for data mapping)
• add new data for data manipulation
• Handle ID problems (for example same id but different canyon etc)
• Create data mapping between sql-view of source db and CDS and select which conversion scripts apply
• ...?

Comments