WIP: New theme: public notice boards [v2] #2357
No reviewers
Labels
No labels
Android-shell
awaiting feedback
awaiting fix confirmation
bug
enhancement
Help Wanted
high-priority
huge
low-priority
Meta
NLNet
OSOC21:Cycling-OVL
Performance
question
search-ui-enhancement
Studio
Tailwind
Themes
UI
upstream-issue
usertest
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: MapComplete/MapComplete#2357
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "midgard/MapComplete:public_notice_boards2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from #2280 which got stale. I've been looking into this today.
The question selection I made for public notice boards is quite different from advertising.
So what I'm having in mind now, is to:
public_notice_boards
layer, but reference the overlapping questions with "builtin",advertising=board
access=yes
from theadvertising
layer, andpublic_notice_boards
in theadvertising
theme.Does that sound good?
I pushed some code already but haven't had the opportunity to test it yet.
This theme is about boards where the public can freely add posters for for example local events. Wikipedia page (fr). Info page about the boards in Ghent (nl). This theme was created in response to a question by someone from a cultural organization who is interested in mapping and seeing all the public notice boards in Ghent. There is overlap with the existing advertising theme, but this theme has a very different focus.
The tags of interest are
advertising=board
andaccess=yes
. A particular subtag ismessage=*
, this theme only showsshowbiz
,non_profit
,opinion
,religion
, since other values are seldom or never applicable for public notice boards.Since many public notice boards are still mapped without
access=yes
, at high zoom the theme shows alladvertising=board
s, using the override technique described in Making_Your_Own_Theme.md section "Don't: use a layer to filter".are read and followed
I tried to test but got a fatal error. I rebased locally on top of the latest release commit and tried again, but still the error, even after
npm run generate:translations
:7f0a127075
to606a7f53ae
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.