-
Notifications
You must be signed in to change notification settings - Fork 5
Vessel Insights Beta #80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mattyturner
wants to merge
1
commit into
master
Choose a base branch
from
vessel-insights-beta
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| --- | ||
| stoplight-id: 43gnp5d9g50ym | ||
| --- | ||
|
|
||
| # Vessel Insights API | ||
|
|
||
| Vessel Intelligence is a whole new area of the Terminal49 API that brings together numerous features to give you complete context and situational awareness of your containers' ocean transportation. | ||
|
|
||
| At the high level it is comprised of two components: | ||
|
|
||
| ## 1. Precise vessel location | ||
|
|
||
| We are gathering vessel positions for every container vessel from Terrestrial and Sattelite AIS to keep you informed of vessel positions. AIS positions are refreshed on an hourly basis. | ||
|
|
||
| > This is now released in the API directly in the [Vessel Model](https://developers.terminal49.com/docs/api/9ddff2198c387-vessel). Whenever a vessel is loaded or departs, you can use the GET Vessel endpoint to keep tracking that vessel location if you wish or you can request a vessel by it's IMO. | ||
| > | ||
|
|
||
| New vessel data includes: | ||
|
|
||
| **latitude and longitude** | ||
|
|
||
| **nautical_speed_knots -** The current speed of the ship in knots (nautical miles per hour) | ||
|
|
||
| **navigational_heading_degrees -** The current heading of the ship in degrees, where 0 is North, 90 is East, 180 is South, and 270 is West | ||
|
|
||
| **position_timestamp -** The timestamp of when the ship's position was last recorded | ||
|
|
||
| In addition to the most recent location, you can request historical positions to plot the course of a vessel over time. | ||
|
|
||
| [GET /V2/vessels/{id}/positions](url) | ||
|
|
||
| ## Container routing plan | ||
|
|
||
| The routing shows each port where the container changes vessel, the arrival arrival and departure vessels with ETA/ATA and ETD/ATD. | ||
|
|
||
| The container routing plan shows you all of the ports where your container changes vessel. You can use this in combination with the vessel positions endpoint to return both past, and future estimated events. | ||
|
|
||
| GET /v2/containers/{id}/route | ||
|
|
||
| route_location | ||
|
|
||
| ports_of_call | ||
2 changes: 1 addition & 1 deletion
2
.../In Depth Guides/Tracking-widget-embed.md → ...n Depth Guides/7-tracking-widget-embed.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| --- | ||
| stoplight-id: leasnylhe5su7 | ||
| stoplight-id: mf74iq4zfq0u3 | ||
| tags: [widget] | ||
| --- | ||
|
|
||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattyturner
I thought that we removed ports of calls?