Add location fields validation

[lechup]

As stated by @zen we could add some validation for location fields in Station and Project models.

My idea would be use Google Maps Geocoding API to verify if given location exists I don't know how reliable it would be.

@grillazz @khasinski @zen any other ideas?

[zen]

I would go even further and make it choice fields down to city level

[lechup]

I think it would be to complicated - should we support adding unexisting cities / regions?

We definately need some research or guadiance by someone who tested location libraries. I know only django-cities but I doubt that geonamed database is comparable with Google Maps Geocoding API...

Let's wait for others, maybe they will have better ideas?

[zen]

Why support adding unexisting places?

[lechup]

I guess there is no lib that guarantees having full support for location names. It will be quite likely we would need to support adding Kozia Wólka or other places we won't have in lib database.

[khasinski]

Google Geocoding API should be OK. We might want to use GPS coordinates as well when adding a new station to reduce the number of mistakes. Also this: https://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/

[zen]

Couple of libs I checked were backed by official national location names databases. They supported every location that was official.

[lechup]

@zen can You recommend any location lib for django You would use? What was the result of Your research?

PS: So I see You do not want to support adding any location that is not in chosen lib.

[zen]

Unfortunately I don't remember what libraries I was checking. As for adding locations, I don't have hard opinion here, but I think it would be easier to use some library and only allow existing placed to be added