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
add fire hydrant position quest #3368
add fire hydrant position quest #3368
Conversation
Thank you again for your work. But please before you continue, we need to determine if collecting this information satisfies the quest guidelines. In particular, where is this key documented? What sense does it make to record this information? |
updated description |
It seems to me |
Kind of. If you seach for a hydrant (assuming a firefighter or else) and you have reached the rough coordinate of the node and you now search for the hydrant it might be useful to know were it is located. If you see, it is located on the street you will find it much faster, since you only have too look on the street. Mapping the surounding grass patch would take much longer than just adding the position key. |
Hmm, is there no dedicated documentation for the key? Where did you get the pictures from? Did you make them yourself? There is a authors.txt also in the /res/ directory, you can add the author + license there. Maybe if you created them yourself, you also want to add them to the wiki and properly document the tag as it is used? |
ping |
Yep, still on my list, but no time for now. Could be closed and reopened later.
17.11.2021 16:59:45 Tobias Zwick ***@***.***>:
… ping
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub[#3368 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AK7SSGUAEMYRUELWUZEA4HTUMPGO5ANCNFSM5FYYUH7Q].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Verfolgungsbild][https://github.com/notifications/beacon/AK7SSGUVF7EIL7MSNAE2ATLUMPGO5A5CNFSM5FYYUH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHHVUFGA.gif]
|
Now the Tags are properly documented in the wiki along with pictures |
Nice! I think that type of image is fine for the lane. However, it should be more centered-- that particular image has the hydrant so close to the bottom that it is partially covered by the text! For phrasing:
|
What about just "On a road" ? |
Better wordings are IMO:
|
app/src/main/java/de/westnordost/streetcomplete/quests/fire_hydrant/AddFireHydrantPosition.kt
Show resolved
Hide resolved
I also took some new pictures: https://commons.wikimedia.org/wiki/File:Fire_hydrant_on_road_side.jpg What do you think about using these? |
Are you sure, that "In a parking area" wouldn't be better? |
I don't know |
"In a parking" sounds awkward, similar to this: ✔️ "It is for parking" Unfortunately, I am not sure exactly how the grammar works here 😬. Going by "it sounds right", the only two situations that I can think of off hand where "parking" stands alone as a noun are "What type of parking is this?" and "Where is the parking [for this store]?" (bracketed part sometimes implied rather than spoken). Otherwise, it is an adjective and thus needs a noun to go with it (spot, space, lane, area…). "Area" is the most broad. I would prefer a more specific word, but only if it is correct. |
…drant/AddFireHydrantPosition.kt well, yep Co-authored-by: Flo Edelmann <florian-edelmann@online.de>
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.
Nice!
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.
Hmm, one more thing: I noticed that the pictures seem to be very large, both in file size and in pixel size.
The pictures have a size of 384x384 dp. That is as large as they'd need to be if each picture should cover the whole form in width. So actually, they can be half the size:
mdpi: 192x192
hdpi: 288x288
xhdpi: 384x384
xxhdpi: 576x576
Also note that the JPEG quality doesn't need to be 90, depending on the image displayed, it can be lower without visible artifacts. (When saving with GIMP, you can compare how the image would look by adjusting the slider.)
👍 |
I wonder, would it make sense to do the same improvement for this quest as done in #3608 ? |
That's a good Idea. I would say this is another task for @tiptoptom... |
Why tiptoptom? |
Because he was visiting me and did all the work, but I commited it.
31.12.2021 01:18:36 Tobias Zwick ***@***.***>:
… Why tiptoptom?
—
Reply to this email directly, view it on GitHub[#3368 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AK7SSGRUZ2DGJITPL666PADUTTZFVANCNFSM5FYYUH7Q].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you authored the thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Verfolgungsbild][https://github.com/notifications/beacon/AK7SSGSIJH3WXPGBPFUGVPDUTTZFVA5CNFSM5FYYUH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHPF6YZI.gif]
|
But I had a lot of help from @thefeiter 😁🙈 |
It would be preferable to mention authors in Note that link is present but file may be deleted/moved/renamed in the future and the license requires attribution. Also, the license info likely should be in https://github.com/streetcomplete/StreetComplete/blob/bb71ae91976ce4f16c22c7ce09ecdcc388a649e1/app/src/main/res/authors.txt |
Do you mean the authors of the images?
And also add this to the file you mentioned? Is that what you mean? |
Already moved the attribution to the other authors.txt |
Am I right that the Position quest does not currently show neighboring hydrants like the other hydrant quests? |
@tiptoptom Good point, changed: 1d809c1 |
Hm, I suppose this would be an improvement. Pillar hydrants are probably also never in parkings and never on the street surface, so for pillar hydrants, it could be just two images. |
Maybe on streets that don't have a sidewalk, a pillar hydrant may be located on one side of the road? |
Maybe... would be hard to find an example photo i imagine
On 28 January 2022 14:24:19 CET, Flo Edelmann ***@***.***> wrote:
> never on the street surface
Maybe on streets that don't have a sidewalk, a pillar hydrant may be
located on one side of the road?
--
Reply to this email directly or view it on GitHub:
#3368 (comment)
You are receiving this because you modified the open/close state.
Message ID:
***@***.***>
…--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
Maybe overpass to find hydrants tagged the way @FloEdelmann describes;
then Google Street View to check if they are in fact on the street;
then someone could visit to take a freely-licensed photo. If we can't
find one within travel distance of one of us, then maybe it's rare
enough that it doesn't matter.
…not sure if it is worth the effort, though.
On Fri, Jan 28 2022 at 05:48:08 AM -0800, Tobias Zwick
***@***.***> wrote:
… Maybe... would be hard to find an example photo i imagine
On 28 January 2022 14:24:19 CET, Flo Edelmann ***@***.***> wrote:
>> never on the street surface
>
>Maybe on streets that don't have a sidewalk, a pillar hydrant may be
>located on one side of the road?
>
>--
>Reply to this email directly or view it on GitHub:
>#3368 (comment)
>You are receiving this because you modified the open/close state.
>
>Message ID:
***@***.***>
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail
gesendet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID:
***@***.***>
|
@smichel17 See #3686: I already found one (via Wikimedia Commons): https://commons.wikimedia.org/wiki/File:Fire-fighting-facility_node-6464454770.jpg The OSM node (https://www.openstreetmap.org/node/6464454770) is tagged |
Actually surprising percentage of pillars so far (I've just started mapping those, though) for me seems to be on parking lots (although I wholeheartedly agree that is probably not very smart idea - but it does not look like particularly good idea for underground ones either). Eg. https://www.openstreetmap.org/node/3423554061 and https://www.openstreetmap.org/node/3423477857 just the other day. (Obviously it is at the far end of parking or between parking places). I can go take picture of that one if wanted. |
So far it should be already quite usable. I used the fire_hydrant:type quest as a template and changed imaged and strings.
The tag used by this quest is
fire_hydrant:position
(wiki, under optional tags)This Could be useful to find a hydrant faster and is a fast to answer quest.
I just need an image for the "parking_lot" position.