GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-02-03T16:45:13Z,
for the dataset file:///shared/jadrolinija_9e4f4e24.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
NPTHR
Feed Email:
N/A
Feed Language:
Croatian
Feed Start Date:
2026-02-02
Feed End Date:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 39
  • Shapes: 0
  • Stops: 160
  • Trips: 606

Specification Compliance report

1217 notices reported (0 errors, 1217 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 606

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

Only the first 50 of 606 affected records are displayed below.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "HR:JL:DayType:293561116:"
3 "HR:JL:DayType:293561117:"
4 "HR:JL:DayType:293581971:"
5 "HR:JL:DayType:293582060:"
6 "HR:JL:DayType:298783741:"
7 "HR:JL:DayType:298783746:"
8 "HR:JL:DayType:301425125:"
9 "HR:JL:DayType:301425126:"
10 "HR:JL:DayType:301425127:"
11 "HR:JL:DayType:301425128:"
12 "HR:JL:DayType:301425129:"
13 "HR:JL:DayType:301425130:"
14 "HR:JL:DayType:301425131:"
15 "HR:JL:DayType:301425132:"
16 "HR:JL:DayType:301425133:"
17 "HR:JL:DayType:301425134:"
18 "HR:JL:DayType:301425135:"
19 "HR:JL:DayType:301425136:"
20 "HR:JL:DayType:301425137:"
21 "HR:JL:DayType:301425138:"
22 "HR:JL:DayType:301425139:"
23 "HR:JL:DayType:301425140:"
24 "HR:JL:DayType:301425141:"
25 "HR:JL:DayType:301425142:"
26 "HR:JL:DayType:301425143:"
27 "HR:JL:DayType:301425144:"
28 "HR:JL:DayType:301425145:"
29 "HR:JL:DayType:301425146:"
30 "HR:JL:DayType:301425147:"
31 "HR:JL:DayType:301425148:"
32 "HR:JL:DayType:301556286:"
33 "HR:JL:DayType:301556312:"
34 "HR:JL:DayType:301556321:"
35 "HR:JL:DayType:301556512:"
36 "HR:JL:DayType:301556526:"
37 "HR:JL:DayType:301556544:"
38 "HR:JL:DayType:301556550:"
39 "HR:JL:DayType:301556616:"
40 "HR:JL:DayType:301556633:"
41 "HR:JL:DayType:301556649:"
42 "HR:JL:DayType:301556661:"
43 "HR:JL:DayType:301556710:"
44 "HR:JL:DayType:301556734:"
45 "HR:JL:DayType:301556745:"
46 "HR:JL:DayType:301556760:"
47 "HR:JL:DayType:301556764:"
48 "HR:JL:DayType:301556780:"
49 "HR:JL:DayType:301556832:"
50 "HR:JL:DayType:301556846:"
51 "HR:JL:DayType:301556860:"
missing_bike_allowance WARNING 606

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 606 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606050:"
3 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606051:"
4 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606052:"
5 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606053:"
6 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606054:"
7 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606055:"
8 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606056:"
9 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606507:"
10 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606508:"
11 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606509:"
12 "HR:JL:Line:310:" "HR:JL:ServiceJourney:310-606510:"
13 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605976:"
14 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605977:"
15 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605978:"
16 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605979:"
17 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605980:"
18 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605981:"
19 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605982:"
20 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605983:"
21 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605984:"
22 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605985:"
23 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605986:"
24 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605987:"
25 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605988:"
26 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605989:"
27 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605990:"
28 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605991:"
29 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605992:"
30 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605993:"
31 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605994:"
32 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605995:"
33 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605996:"
34 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605997:"
35 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605998:"
36 "HR:JL:Line:332:" "HR:JL:ServiceJourney:332-605999:"
37 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606396:"
38 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606397:"
39 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606398:"
40 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606399:"
41 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606400:"
42 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606401:"
43 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606402:"
44 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606403:"
45 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606404:"
46 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606405:"
47 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606406:"
48 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606407:"
49 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606408:"
50 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606409:"
51 "HR:JL:Line:334:" "HR:JL:ServiceJourney:334-606410:"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_end_date"
"feed_info.txt" 2 "feed_version"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260203" "20250530" "20250626"