There are many gaps in the final generated voronois, leading to 'null' responses when querying certain coords

[DanielJDufour]

Which server

• Dev
• Stage
• Prod
• Other (please specify) During local development

Describe the bug
See steps on how to reproduce

To Reproduce

I ran the following steps after pulling down the latest dev branch

• docker compose down -v
• docker compose build --no-cache
• docker compose up build

I try to create a project with the attached AOI, the following is POST'd to http://api.fmtm.localhost:7050/projects/stub?org_id=1

The API returns a 500, with the following error logged in the backend/Python:

Expected behavior
Project creation works

Screenshots
See screenshots in reproduction steps

Smartphone (please complete the following information):

• Device: [e.g. iPhone6] MacBook Pro
• OS: [e.g. iOS8.1] MacOS
• Browser [e.g. stock browser, safari] Chrome
• Version [e.g. 22]

Additional context
The AOI file's filename ends in .json not .geojson, which hasn't caused issues before.

stelmo-valid.json

[DanielJDufour]

This is blocking all my other work, so I'll start work on fixing this. Definitely open to suggestions!!!!!

[DanielJDufour]

Add a more descriptive Exception

[DanielJDufour]

Seems to be related to pg-nearest-city. It's possible I'm missing a preparation/setup step.

[DanielJDufour]

Looks like pg-nearest-city is reporting that database is already initialized

[DanielJDufour]

Trying a bounding box in Brazil also leads to the same error.

Additionally, the data is definitely there in the database. RunningSELECT * FROM pg_nearest_city_geocoding; returns data:

[DanielJDufour]

I tried to replicate the same SQL statement that pg-nearest-city will run it and it's returning zero records for some reason:

Here's how I got the SQL statement:

[DanielJDufour]

In order to debug further, I ran the following SQL:

SELECT ST_ASGEOJSON(ST_UNION(voronoi)) FROM pg_nearest_city_geocoding WHERE country = 'US';

And got the following after loading up the result in QGIS:

It appears as if there are some gaps in the voronoi data in the database. I'm not sure if that's an issue with the voronoi.wkb.gz, pg-nearest-city or something that I did. Still trying to figure out the root cause.

Here's a map zoomed into the point with the voronoi:

As you can see the point is in the gap of the voronoi polygons.

[spwoodcock]

You're testing via a curl API call instead of via the frontend?

[DanielJDufour]

Some gaps in Brazil, too, but not as many:

SELECT ST_ASGEOJSON(ST_UNION(voronoi)) FROM pg_nearest_city_geocoding WHERE country = 'BR';

*Created in QGIS with OSM baselayer

[spwoodcock]

Reproduced the same error - good catch & great debugging!

Don't worry about debugging further - I'll move this to pg-nearest-city & those involved in that project may be able to help debug further 😄