Make geodata service run locally and on quaoar1

[fsteeg]

Currently, the service is running on gaia. When running locally or on quaoar1 (where the other services run), it hangs. @philboeselager suggested this might be due to the fact that unlike gaia, they are not externally accessible. Any ideas about that, @dr0i?

[dr0i]

Don't know what is meant by "hanging" here. If it's meant to be not reachable: you should be able to connect to the service even if it's only reachable within the internal net.
If the problem is that the the NOMINATIM API is not reachable: could this be because the IP of the other server are blocked because of too massive querying? This could be determined by reading the http-status-code of the answer of the query.
Hope that helps ?

[fsteeg]

This issue is blocking not only the two issues linked above, but via #34 any new functionality. Moving to top of the ready column. @philboeselager: I think this would be the ticket to pick up if you have time to work on the geodata service.

[SBRitter]

I tested this: it runs both locally and on quaoar1. The service will be deployed with an embedded elasticsearch on quaoar1 (see #36).