Talk:Key:interval

Why are the sign 'ː' — which is a very specific phonetics sign — used instead of the regular colon ':' ?

Thanks for noticing thatǃ I have absolutely no idea why that happened, but it just did for some reason. I have replaced all cases of 'ː' with colons. -- LeifRasmussen (talk) 23:20, 13 January 2019 (UTC)

sql parser

hello, do you have any sql parser which would return the interval on "tuesday between 17:00 and 17:59". generally I would need an info similar to 'headway:rush_hour' which is just one integer. see https://epsilon.sk/cyklokoalicia/mhd.html for an output --MichalP (talk) 13:09, 23 January 2019 (UTC)

No, I don't. The way to write this would to create a program like followsː

: : If only tag interval present and no intervalːconditional

: : : return interval value

: : else

: : : separate the semicolon separated values and check each one's opening hours syntax using https://github.com/opening-hours/opening_hours.js or other parser.

: : for each semicolon separated value

: : : check to see if the value matches the time frame inputted.

: : : if yes

: : : : return that interval value

: : if none of the intervalːconditional opening hours syntax match the inputted time frame, return the value of the interval tag.

Good luck on your projectǃ --LeifRasmussen (talk) 13:44, 23 January 2019 (UTC)

Decimal minutes

If a bus leaves every seven and a half minutes (9 times an hour), can I then write interval=7.5, or must I write interval=00:07:30 (following the format HH:MM:SS)? This can be confusing when other bus lines have interval=10 and interval=5. --Pbb (talk) 16:42, 25 August 2019 (UTC)

Yes, decimal minutes are fine. The reason for also having the option of adding seconds was to support all formats that mappers might want to use.

Semi-colon for (repeating) sequences

How to tag a sequence of e.g. 35+25 minutes each hour?

Is interval=00:35;00:25 useful ?

Or even interval:conditional=(00:35;00:25) @ (Mo-Fr 09:00-12:00,15:30-18:30 --Skyper (talk) 16:31, 25 June 2020 (UTC)

More examples with opening_hours=*

If a route is only served a few times a day it might be better to try to solve it with a sequence in opening_hours=* instead using interval=* and interval:conditional=*, e.g. opening_hours=Mo-Fr 06:04-06:27,10:31-10:54,18:55-19:20; PH,Su off.

Not sure if overlapping sequences are allowed if the one trip ends after the next one starts. --Skyper (talk) 16:49, 25 June 2020 (UTC)

Rendering

Does anybody know why the interval key has never made it into rendering in the transport map? This has been discussed before apparently without success, but there is at least one example where just this is being done (by means of Maperitive) and I think the arguments from 2012 are still convincing: true, people won't look for precise timetable data in OSM data, but a transport map that shows whether there is a frequent or not-so-frequent service (e.g. by fat/narrow/dotted lines) has surely got its practical benefits? --Alfons234 (talk) 16:45, 6 November 2021 (UTC)

Not someone who have worked on a renderer: Headway or frequency is a relative concept. 15min = 4ph may frequent in a US city, but only average in Asia or even Europe. Frequency mapping by line thickness will depend on the mix in the location, needing more complete data. There's no absolute definition. Considering the common meaning of dotted or dashed lines, you will need opening_hours=* to show limited service. ---- Kovposch (talk) 08:38, 7 November 2021 (UTC)

I prefer to use thickness instead of virtual and solid to express the interval between buses, because for some routes that may exist for more than two or three hours, if the proportion of alternating dotted and solid lines is determined according to the length of the interval, will they appear in the entire route? A dilemma not found on tiles? --快乐的老鼠宝宝 (talk) 11:31, 7 November 2023 (UTC)

AFAIK i was one of the earliest mappers who used interval=* in conjunction with service_times=* as starting point for a good-enough-timetable-service. The idea is that you want most times want to know what route is the fastest for the vehicles witch operate on this time, not really the exact times from the timetable.

So if you want travel from A with interval=10 over B with interval=30 to C, you know that the journey took you a mean waiting time on A of 5 minutes and 15 minutes at B in addition to the duration for the real trip. In the worst case you have to wait 38 minutes. As more interchanges your journey has, as more are the waiting times really the mean. --Fabi2 (talk) 14:57, 17 November 2021 (UTC)

If you ever wondered why there is the the "/"-syntax in the opening_hours=*-specification for the interval, these use for public transport intervals was one of the ideas we had at the creation of the Netzwolf-syntax on the german forum. --Fabi2 (talk) 15:48, 17 November 2021 (UTC)

Interesting! This is a more ambitious usecase than I was thinking of. I never thought of calculating approximate journey times, only of getting a first overview of where there are more or less regular services. So when Kovposch points out that the concept is relative, I do agree but still feel there might be potential for compromise. I mean, Asia has rural areas too. So I dare say that, as a compromise, 15 minutes might be the limit for a potential "most frequent" band worldwide, seeing that at the moment the map does not make a difference whether the bus runs every 10 minutes or once a day. It's a shame, though, that we have (unlike hiking routes) no tag to show whether the bus route is local, regional or nationwide, because obviously different frequencies are to be expected in terms of these. --Alfons234 (talk) 14:24, 6 November 2023 (UTC)

Proposal:Differentiation for routes of public transport existed, but isn't very good yet. passenger=* is used for railways. I don't like the list of service=* used in Key:service#Train_Routes , as there are too much overlap.
—— Kovposch (talk) 08:58, 7 November 2023 (UTC)