Skip to content
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.

Extract Bikelanes Presence into Separate Table #145

Merged
merged 1 commit into from
Jul 15, 2024

Conversation

rush42
Copy link
Contributor

@rush42 rush42 commented Jun 12, 2024

Extract Bikelanes Presenceinto a separate table. It won't add streets where all three sides are not_expected. This reduces the data for Berlin by ~ 27% from 71k to 52k objects.

@rush42 rush42 force-pushed the refactor/extractPresence branch from 6370cdf to 41c12e0 Compare June 12, 2024 11:58
@rush42 rush42 force-pushed the refactor/extractPresence branch from 41c12e0 to 886bd72 Compare July 15, 2024 10:17
@rush42 rush42 force-pushed the refactor/extractPresence branch from 886bd72 to 237cb69 Compare July 15, 2024 10:19
@rush42 rush42 merged commit 8ef9f7b into develop Jul 15, 2024
1 check passed
@rush42 rush42 deleted the refactor/extractPresence branch July 15, 2024 10:21
rush42 added a commit to FixMyBerlin/atlas-app that referenced this pull request Jul 15, 2024
…#145)

Extract Bikelanes Presenceinto a separate table. It won't add streets
where all three sides are `not_expected`. This reduces the data for
Berlin by ~ 27% from 71k to 52k objects.
rush42 added a commit to FixMyBerlin/atlas-app that referenced this pull request Jul 15, 2024
…#145)

Extract Bikelanes Presenceinto a separate table. It won't add streets
where all three sides are `not_expected`. This reduces the data for
Berlin by ~ 27% from 71k to 52k objects.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants