# Timetables Complete GTFS Contains duplicates

**URL:** https://opendataforum.transport.nsw.gov.au/t/timetables-complete-gtfs-contains-duplicates/1865
**Category:** Real-time Public Transport
**Created:** [November 28, 2019, 5:04am UTC](https://opendataforum.transport.nsw.gov.au/t/timetables-complete-gtfs-contains-duplicates/1865 "2019-11-28T05:04:19Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![jxeeno](https://sea1.discourse-cdn.com/flex019/user_avatar/opendataforum.transport.nsw.gov.au/jxeeno/32/210_2.png) [@jxeeno](https://opendataforum.transport.nsw.gov.au/u/jxeeno)
#### Post date: [November 29, 2019, 9:03am UTC](https://opendataforum.transport.nsw.gov.au/t/timetables-complete-gtfs-contains-duplicates/1865/5 "2019-11-29T09:03:38Z")

</div>

This discussion here may also help 🙂

> [@Timetables Complete GTFS](https://opendataforum.transport.nsw.gov.au/t/timetables-complete-gtfs/883/18):
>
> Hmm, it shouldn’t be possible for the bundle to have both old and new trips. If you’re certain this is a fresh import into a blank sqlite database, maybe those are for separate services after all. The next thing to look at would be how are you handling calendar\_dates exceptions. Are you correctly determining which service IDs operate on which days based on entries in both calendar.txt and calendar\_dates.txt?

---

_[View the full topic](https://opendataforum.transport.nsw.gov.au/t/timetables-complete-gtfs-contains-duplicates/1865)._