Skip to content
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.

feature: use v2 enketo geocoder api #770

Closed

Conversation

green3g
Copy link

@green3g green3g commented Mar 17, 2021

https://github.com/enketo/enketo-express/issues/123

Utilize enketo-express geocoder api /api/v2/geocoder

To test this, I set up a simple proxy to enable communication between ee and core:

Proxy: localhost:3000
Enketo: localhost: 8006 (via config)
Core: localhost:8005

const express = require( 'express' );
const { createProxyMiddleware } = require( 'http-proxy-middleware' );

const PORT = 3000;
const app = express();
app.use( '/api', createProxyMiddleware( { target: 'http://localhost:8006', changeOrigin: true } ) );
app.use( '/', createProxyMiddleware( { target: 'http://localhost:8005', changeOrigin: true } ) );
app.listen(  PORT );
console.log( `Proxy is listening on port http://localhost:${PORT}/` );

@green3g
Copy link
Author

green3g commented Mar 17, 2021

Hmm - looks like google is used in a few cases here- as a basemap as well.

How do we want to handle this?

@MartijnR
Copy link
Member

Thanks! We should keep the google code for the map layers I think, and only change geocoding code.

@green3g
Copy link
Author

green3g commented May 3, 2021

Hi @MartijnR - I apologize in the delay in getting these fixed - I have fallen behind due to some other priorities at the moment. I will be following up though in May.

Just wanted to provide an update

@lognaturel lognaturel closed this Apr 21, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants