The Movie Database Support
Support → API Support
Inaccurate results for "with_runtime.lte" in discover/movies
posted by AnimagusCatSTAFFMOD on October 25, 2019 at 4:43 AM
Hi, I'm new to using this db and still figuring things out. When I tried to run a discover for movies with runtime less than 60mins, the result I get is returning some movies with more than 60mins runtime.
https://api.themoviedb.org/3/discover/movie?api_key=MYAPIKEY&language=en-US&include_adult=false&include_video=false&page=1&with_runtime.lte=60
Result includes movies "Hereditary", "K-PAX", "Dances with Wolves" and more which have runtime of 127mins, 120mins, 181mins respectively.
Is there something wrong with my query?
Reply by talestalker
on October 25, 2019 at 9:00 AM
Hi,
this was already discussed here. Your query is fine, but:
I've corrected all above mentioned records, but unless @travisbell change how discover method with "&with_runtime=" parameter works (e.g. by taking into account query language), it may happen.
Reply by AnimagusCat
on October 27, 2019 at 5:12 AM
Alright, thanks for clarifying!
After looking through the API forum it seems that it's a known bug that discover/movies could return some inaccurate runtimes.
Guess I'll just figure out a way to get around this.
Reply by Travis Bell
on October 27, 2019 at 1:42 PM
Just for extra clarification, there's two separate issues being discussed/mentioned here.
First is how discover now indexes runtimes, which is by looking at all of the available values. This is the correct way to do it, and won't be changing.
Second is to do with a bug that I know about with regards to querying runtimes with discover. That bug is being tracked here, which you can follow/vote for if you wish. It will be getting fixed in the next few weeks.
Reply by Travis Bell
on November 1, 2019 at 3:47 PM
I believe the runtime query issues have been fixed, please let me know if you see it not working.
Cheers.
Reply by AnimagusCat
on November 4, 2019 at 7:42 AM
Hi Travis,
Thanks for the update!
I ran the same query again as above and although the result did show some movies that are less than 60 mins, it did include those that are over that runtime as well.
For example, the first result shows Cars which actually has a runtime of 117 mins.
Other results that came up were Deadpool (108 mins), Logan (137 mins), The Lion King (89mins), The Fate of the Furious (196 mins), Forrest Gump (142 mins), Harry Potter and the Prisoner of Azkaban (141 mins), Ted 2(115 mins), Goosebumps 2: Haunted Halloween (90 mins)..
This was only the first page but I suppose this issue might appear for the other pages as well unfortunately.
Reply by talestalker
on November 4, 2019 at 8:13 AM
@AnimagusCat
It's the same issue again:
and so on...
I've corrected the 3 above mentioned movies, but I'm not able to check them all. If I understand it correctly, this is intended behavior of the API, so it is on us to correct all wrong runtimes...
Reply by talestalker
on November 6, 2019 at 2:38 PM
I've removed over 800 invalid movie runtimes, so discover with "&with_runtime.lte" should return more relevant results now.
Reply by Travis Bell
on November 6, 2019 at 3:03 PM
Thanks @talestalker. I have a pretty simple way to help catch bad inputs that I’ll end up rolling out in the next few weeks. That will also improve things.