-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Missing presets - Gas-stations #1987
Comments
|
I added the fields for fuel types, and some other things that are commonly found around gas stations in d46e340. What @ingalls said too. If you want to really map a lot of detail, you can tag the area of the gas station as |
Don't forget fuel:octane_92 and fuel:octane_80, which are both common. In North America, you'll find 87 common too. I'd suggest not using names for "Regular Gasoline" for what varies from region to region. |
Maybe we should just forget the fuels for now? I don't think it's something we'll be able to get 100% correct. |
You need to refer to them by number, and there's 6-7 common ones. Unfortunately, only 3 or 4 will ever be found at a particular gas station. |
It's worse too because in US the pump numbers are AKI, which don't match the UK-ish octane numbers in the OSM tags. see: https://en.wikipedia.org/wiki/Octane_rating I really just picked the common fuel tags on the OSM wiki and mapped them to what they would be called in the USA. |
The common use is to tag what it says on the pump as the octane usage, not to worry about AKI to RON conversion, because we map the pumps say. |
Ok, gotcha. So as not to block any other development, I think I'm going to just remove the gasoline fuel checkbox fields for now and maybe add a better fuel field later that maps numbers entered to octane_nn tags. |
Missing presets for Gas-stations:
fuel:diesel, fuel:e10 etc.
Maybe also car_wash, car_repair, car_parts,
as well as kiosk / shop=newsagent / shop=convenience / lottery=*
because many gas-stations around here offer a lot more than just gas.
The text was updated successfully, but these errors were encountered: