diff --git a/documentation/slate/source/includes/interface.md b/documentation/slate/source/includes/interface.md index c32e8a0df8..99087809ea 100644 --- a/documentation/slate/source/includes/interface.md +++ b/documentation/slate/source/includes/interface.md @@ -4,7 +4,7 @@ Interface The base URL for **navitia.io** is: -We aim to implement [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS) +We aim to implement [HATEOAS](https://en.wikipedia.org/wiki/HATEOAS) concept with Navitia. Every resource returns a response containing a links object, a paging diff --git a/documentation/slate/source/includes/objects.md b/documentation/slate/source/includes/objects.md index dffbb464bb..152ca6997d 100644 --- a/documentation/slate/source/includes/objects.md +++ b/documentation/slate/source/includes/objects.md @@ -538,7 +538,7 @@ Severity object can be used to make visual grouping. | Field | Type | Description |---------------|------------|--------------------------------------------- | id |string |Identifier of the address -| content_type |string |Like text/html, you know? Otherwise, take a look at +| content_type |string |Like text/html, you know? Otherwise, take a look at | name |string |name of the Channel ### Period @@ -666,7 +666,7 @@ You can find pathways in [journeys](#journeys) service, where there is some "via |zip_code|string|Zip code of the admin| Cities are mainly on the 8 level, dependant on the country -() +() ### Equipment reports diff --git a/documentation/slate/source/includes/realtime.md b/documentation/slate/source/includes/realtime.md index f8ec5a1a58..bbde4ed01d 100644 --- a/documentation/slate/source/includes/realtime.md +++ b/documentation/slate/source/includes/realtime.md @@ -39,7 +39,7 @@ A disruption is present in the response of the endpoints described if the reques Several public transport objects have separate collections for `base_schedule` and `realtime`.
So the data_freshness parameter may affect the number of objects returned depending on the request. -For example when looking for a specific circulation with the collection vehicle_journey using the request:
`http://api.navitia.io/v1/coverage//vehicle_journeys?since=20191008T100000&until=20191008T200000&data_freshness=base_schedule`. +For example when looking for a specific circulation with the collection vehicle_journey using the request:
`https://api.navitia.io/v1/coverage//vehicle_journeys?since=20191008T100000&until=20191008T200000&data_freshness=base_schedule`. A vehicle_journey circulating between since and until that is **fully deleted** (NO_SERVICE) by a disruption will of course be **visible** if `data_freshness=base_schedule`.
But it **will not appear** with the parameter `data_freshness=realtime` as it does not exist in that collection. @@ -85,7 +85,7 @@ See the [disruption](#disruption) objects section for its full content and descr ``` shell # Request example for /journeys -http://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime +https://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime ``` ``` shell @@ -165,7 +165,7 @@ A list of the disruptions impacting the journey is also present at the root leve ``` shell # Request example for /departures (data_freshness=realtime by default) -http://api.navitia.io/v1/coverage//physical_modes//stop_areas//departures?from_datetime=&data_freshness=realtime +https://api.navitia.io/v1/coverage//physical_modes//stop_areas//departures?from_datetime=&data_freshness=realtime ``` ``` shell @@ -220,7 +220,7 @@ A list of the disruptions impacting the departures is also present at the root l ``` shell # Request example for /stop_schedules (data_freshness=realtime by default) -http://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//stop_schedules?from_datetime=&data_freshness=realtime +https://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//stop_schedules?from_datetime=&data_freshness=realtime ``` ``` shell @@ -365,7 +365,7 @@ In the disruption, new stop points can be found in the list of "impacted_stops" ``` shell # Request example for /journeys -http://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime +https://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime ``` ``` shell @@ -464,7 +464,7 @@ In the disruption, every stops served by the new train can be found in the list ``` shell # Request example for /journeys -http://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime +https://api.navitia.io/v1/coverage//journeys?from=&to=&data_freshness=realtime ``` ``` shell @@ -567,7 +567,7 @@ When requesting a journey that was previously disrupted and is now back to norma ``` shell # Request example for /departures (data_freshness=realtime by default) -http://api.navitia.io/v1/coverage//physical_modes//stop_areas//departures?from_datetime=&data_freshness=realtime +https://api.navitia.io/v1/coverage//physical_modes//stop_areas//departures?from_datetime=&data_freshness=realtime ``` ``` shell @@ -613,7 +613,7 @@ No disruption is present at the root level of the response and so, in the sectio ``` shell # Request example for /stop_schedules (data_freshness=realtime by default) -http://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//stop_schedules?from_datetime=&data_freshness=realtime +https://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//stop_schedules?from_datetime=&data_freshness=realtime ``` ``` shell @@ -651,7 +651,7 @@ No disruption is present at the root level of the response and so, in the sectio ``` shell # Request example for /terminus_schedules (data_freshness=base_schedule by default) -http://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//terminus_schedules?from_datetime=&data_freshness=realtime +https://api.navitia.io/v1/coverage//physical_modes//lines//stop_areas//terminus_schedules?from_datetime=&data_freshness=realtime ``` ``` shell diff --git a/documentation/slate/source/includes/stuff.md b/documentation/slate/source/includes/stuff.md index 65189f28e7..a73e4c0b54 100644 --- a/documentation/slate/source/includes/stuff.md +++ b/documentation/slate/source/includes/stuff.md @@ -7,14 +7,14 @@ Multiple journeys Navitia can compute several kind of journeys with a journey query. The -[RAPTOR](http://research.microsoft.com/apps/pubs/default.aspx?id=156567) +[RAPTOR](https://www.microsoft.com/en-us/research/publication/round-based-public-transit-routing) algorithm used in Navitia is a multi-objective algorithm. Thus it might return multiple journeys if it cannot know that one is better than the other. For example it cannot decide that a one hour journey with no connection is better than a 45 minutes journey with one connection (it is called the [pareto front](http://en.wikipedia.org/wiki/Pareto_efficiency)). -Navitia uses multiple objectives : arrival datetime, the number of transfers, -the duration of "walking" (transfers and fallback), reliability of lines, crowd, etc. +Navitia uses multiple objectives : arrival datetime, the number of transfers, +the duration of "walking" (transfers and fallback), reliability of lines, occupancy, etc. If the user asks for more journeys than the number of journeys given by RAPTOR (with the parameter `min_nb_journeys` or `count`), Navitia will