what3words integration

[kynan]

what3words is a unique combination of just 3 words that identifies a 3mx3m square. This is a sufficient resolution to uniquely identify a waterpoint (see also #15) and could therefore be used as an easy to remember ID.

Integration requires roughly:

• add a w3w field to the waterpoint_schema
• add w3w lookup when geolocating user
• add w3w input field in forms
• multi-lingual support for w3w (en,sw)
• display w3w on map tips

There are some open questions e.g. how to create a geospatial index on the w3w field.

[cazgp]

+1 Whoop! I was thinking it might be useful for Taarifa :)

[fayazv]

@kynan what do I do with the file you sent smime.p7s ?

[kynan]

Nothing, that's my digital signature.

[fayazv]

Ok. So what's the next step?

[kynan]

See the checklist above: start by modifying the schema.

[fayazv]

@kynan I've added the schema. Need some assistance on the second. I have used jquery to integrate w3w.

[kynan]

@fayazv You haven't pushed any code afaict. Which branch are you working on?

[fayazv]

I've created a new branch - fayaz-dev

[kynan]

OK, thanks. I'd rather call this branch feature/w3w-integration though.

[fayazv]

makes more sense.

[fayazv]

see commit: a6f96ae

[kynan]

Let's not close this before the feature is deployed.

[kynan]

@fayazv What's the progress on this?

[kynan]

The waterpoints file the w3w guys batch converted for us was based on the Sep 2014 data, so it's outdated compared to the Feb 2015 data we're now using.

There's another issue: if we want w3w in the database I think we need to keep both English and Kiswahili versions so we can show the right version based on language selection. Thoughts? @dgorissen

[fayazv]

Having the w3w in multiple languages is a good idea. But, might not be feasible for more than 3 languages. For instance: In the TaarifaTraders we have 4 languages (English, Swahili, Chichewa and Nyanja), though w3w isn't present in chichewa and nyanja.

[dgorissen]

Are we going to be needing thw w3w name one waterpoint at a time (ie, when
a user requests it) or are there times we need very many at once? In the
former why bother with w3w in the db at all and not just use the API?
In the latter adding different languages seems a bit like a hack (where
does it end?) but perhaps doable for 2-3 max. Or perhaps store only in one
language and use the w3w api for the others?

[kynan]

Valid points, I'm not sure either. Maybe using their API will be sufficient.

[fayazv]

@dirk thanks for the points. The w3w are going to be used in two ways, i. Adding waterpoint (one time request to the api), ii. Map (many requests for all the visible waterpoints), the w3w will be shown in the tips.

We could have english version stored in the db and use api requests for other languages (would be helpful for later use).