-
Notifications
You must be signed in to change notification settings - Fork 9
Visually Group User Visits with Work Areas on Microplanning Map #1144
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
Open
zandre-eng
wants to merge
7
commits into
main
Choose a base branch
from
ze/visit-work-area-grouping
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+96
−19
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4186fe6
refactor: track highlighted work area ids via selectedFeature watcher
zandre-eng e51783e
feat: include work_area_id in user visit vector tiles
zandre-eng 8d61c89
refactor: extract visit circle layer paint builder
zandre-eng 4d89126
feat: highlight selected visits as green diamonds
zandre-eng fae7941
feat: add hidden symbol layer for highlighted visits
zandre-eng f6b48a1
fix: refresh visit styling after visit layers are first added
zandre-eng 96b6eb9
style: use black halo on visit highlight diamonds
zandre-eng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can these be replaced with commonly available fonts or browser generics like "Sans", "Serif" etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got the following response after investigating it with Claude:
text-fonthere isn't a CSS font — Mapbox GL renders text from SDF glyphs served by the style'sglyphsendpoint, so the value has to match a font the active style actually ships. Generics likeSans/Serifaren't resolved and the layer would fail to render glyphs.DIN Pro Medium+Arial Unicode MS Regularare the fonts bundled with themapbox://styles/mapbox/standardstyle we're using (Arial Unicode is the standard CJK fallback). Happy to swap to another Mapbox-hosted stack if you'd prefer, but browser generics won't work here.Given the above, I'm opted to keep the current font as it ships with the Mapbox style. For verification I did switch it to
Sansfont and received a 404 error in the browser's dev console which confirms that generic fonts won't work.