External data services can be configured by group owners and administrators. These services can receive notifications for the messages sent to the group and optionally modify the message or even stop the message from being processed.
Existing services like SeenTags can be used as data services.
Developers can build their own as well or make adapters for common tools (Google Spreadsheets, Fusion Tables, etc)
We will use SeenTags as an an example of how to configure your group to use data reports.
You are done!
Messages with the right prefix will be sent to SeenTags and will be ready for parsing
(Note you can use any service for structured data reporting as long as it supports the POST protocol documented at the bottom of the page).
''?1: Kampot, ?2: 6, ?3: malaria''
should be edited to read:
''Province: Kampot, Cases: 6, Disease: malaria''
Other services can be implemented by exposing a HTTP endpoint somewhere in the internet. This endpoint will receive the messages as a HTTP POST request with the from, to and sender attributes in the query string, and the original text message in the request body.
The server can return special headers to indicate GeoChat how it should continue the processing of the message:
X-GeoChat-Action: [stop|continue|reply]: This header, when returned with a “stop” value, will indicate GeoChat to stop processing the message to be saved or sent to other group members. Using “reply” value will also stop the message but replying the originator with the content of the response body.X-GeoChat-Replace: [true|false]: If this header is returned with value “true”, the response body will be used as the new content for the message.