You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Currently, the way_tag_ranges stores the start and end indexes for tags for each way. This is twice as much data as required, we could just store the start (or end) position for each way, and use the previous way's value as the other end of the range. This would reduce memory requirements for this map by a factor of two.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the
way_tag_ranges
stores the start and end indexes for tags for each way. This is twice as much data as required, we could just store the start (or end) position for each way, and use the previous way's value as the other end of the range. This would reduce memory requirements for this map by a factor of two.The text was updated successfully, but these errors were encountered: