**Unofficial .NET library for MarineTraffic.com's API. **
**Project status: beta. **
License: not yet decided
Nuget: MarineTrafficApi
Open to contributions! Are you using MT already? What would you like to see in this library? Do you have some codes that may be added here? Feel free to open an issue.
- Add a nuget reference to:
MarineTrafficApi - Create a client object and keep it across calls.
var client = new MarineTrafficApiClient("your-api-key"); - Create a request for you needs
var request = new ExportVesselsV8Request(); ... - Execute the request to get the result
var result = request.Execute(client); - Always check for errors
if (result.Succeed) { ... } else { /* display result.Errors */ }
- PS01: Vessel Historical Track
- PS02: Vessel Positions of a Static Fleet
- PS03: Vessel Positions of a Dynamic Fleet
- PS04: Vessel Positions within a Port
- PS05: Vessel Positions in a Predefined Area
- PS06: Vessel Positions in a Custom Area
- PS07: Single Vessel Positions
- EV01: Port Calls
- EV02: Vessel Events
- EV03: Berth Calls
- VD01: Vessel Photos
- VD02: Vessel Particulars
- VD03: Search Vessel
- VI01: Voyage Forecasts
- VI02: Expected Arrivals
- VI03: Port Distances and Routes
- VI04: Predictive Destinations
- VI05: Predictive Arrivals
- VI06: Port Congestion
- VI07: ETA to Port
- PU01: Change Fleet
- PU02: Vessels in a Fleet
- PU03: Fleets
- PU04: Credits Balance
- PU05: Clear Fleet
Where can I get an API key?
- See MT credits.
Something is missing in this library, can I contribute? Yes. Here are the main steps.
- Fork this repository.
- Clone your fork on your PC.
- Make a branch for you new feature with a name like:
dev/*new-feature-title* - Code your feature.
- Coding style is StyleCop's.
- Commit and push your changes on your fork.
- Submit a pull request on this repo to discuss and share your changes.
Why use the CSV export format?
- CSV is the most lightweight format available. It works real well for objects without a structure tree.