Skip to content
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.

Sign up for GitHub

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

add Footway Area area:highway label #329

Merged
merged 2 commits into from
Jan 6, 2022
Merged

add Footway Area area:highway label #329

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a4b841
add Footway Area area:highway label
matkoniecz Jan 5, 2022
fbb5e2d
Remove what is not needed
matkoniecz Jan 5, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions data/presets/area/footway.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"fields": [
"area/highway",
"surface"
],
"geometry": [
"area"
],
"terms": [
"area:highway",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By the way, this preset will already be searchable by “footway” regardless of language, because iD will match tag values: openstreetmap/iD#8869 (comment). If matching keys is also desired, maybe that should be a more general, non-preset-specific feature on the iD side, so other consumers like Overpass turbo can decide not to match keys if it doesn’t make sense for their use case.

"edge of pavement",
"footway area",
"footway shape",
"pavement",
"sidewalk shape",
"sidewalk area"
],
"tags": {
"area:highway": "footway"
},
"name": "Footway Area"
}