-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve continuity between NE and OSM localities #2020
Comments
Should be paired with #1906 for POV point of view for locality kinds and country capital and region capital tags. |
Let’s skip the backfill.
…On Wed, Jan 26, 2022 at 21:17 peitili ***@***.***> wrote:
@nvkelso <https://github.com/nvkelso> I found that the proposal to use NE
pop_min to backfill OSM population when this field is not available
conflicts with this change #1993
<#1993>. If we want to
keep both changes the default in 1993 and backfill logic here, it will be
non-trivial, because we need to differentiate whether the population field
is from the default or from the OSM in the transform function. Do we want
to remove the change in 1993 or do we want to not do the backfill using
pop_min?
—
Reply to this email directly, view it on GitHub
<#2020 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGQIOZVVAVGSX43A3NDI2LUYDIOBANCNFSM5JGLWXYQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I actually later found a way to accommodate both the logic will be: If the population is N/A, use NE pop_min, if NE pop_min is still unavailable use the estimate, I basically moved the estimate value from the yaml file to transform function. Let's wait for the integ tests to see how it goes. #2048 |
There's also a continuity problem where San Diego, California, drops between z7 & z7.999... because Natural Earth gives it a min_zoom of This means that the min_zoom, population_rank, population sort that happens in grid thinning doesn't have enough consistent information to work with, and it can get omitted from tiles at that one zoom. The solution is to also use the NE min_zoom for the OSM joined places. |
Fixed via #2048 |
When zooming across the NE <> OSM boundary around zoom 8, townspots shift position, population_rank values change, and min_zoom values change.
For country labels in the same places theme we do a join on WikidataID and apply the NE min_zoom to the OSM features.
We should do the same type of harvesting for localities. Namely:
population_rank
andmin_zoom
values from NE.population
value should not be adjusted, as that's for the incorporated area, while the NE population_rank is for the metro area and is more useful for label grading in the stylesheet.This is accomplished for countries with:
vector-datasource/data/functions.sql
Lines 996 to 1043 in 15a8fb3
vector-datasource/vectordatasource/transform.py
Lines 8717 to 8752 in 2eb4486
vector-datasource/queries.yaml
Lines 675 to 679 in 2eb4486
The text was updated successfully, but these errors were encountered: