@article{
nais2007,
   Author = {Williams, K. B.},
   Title = {RFP for the Nationwide Automatic Identification System Increment 2, Phase 1},
   Journal = {USCG},
   Volume = {1.0},
   Pages = {262},
   Year = {2007} }



@article{
   Author = {Vachon, P.W. and English, R.A. and Wolfe, J.},
   Title = {Ship Signatures in RADARSAT-1 ScanSAR Narrow B Imagery: Analysis with AISLive Data},
   Journal = {Defence Research and Development Canada - Ottawa Technical Memorandum},
   Volume = {TM 2007-052},
   Pages = {70},
   Year = {2007} }



@article{
treadwell2007,
   Author = {Treadwell, M.},
   Title = {U.S. Research Goals With an Accessible Artic Ocean},
   Pages = {30},
   Year = {2007} }



@misc{
noaadata-py,
   Author = {Schwehr, K.},
   Title = {noaadata-py},
   Abstract = {noaadata-py is a suite of python tools for data used by or produced by NOAA. As of May 2007, the package contains code for marine Automatic Identification System (AIS) messages, extensions for the National AIS (N-AIS) network, and CO-OPS/PORTS waterlevel OpenDAP/SOAP.},
 Year = {2007} }



@article{
schwehr2007g,
   Author = {Schwehr, K. and Alexander, L.},
   Title = {Encoding AIS Binary Messages in XML Format for Providing Hydrographic-related Information},
   Journal = {Internation Hydrographic Review},
   Volume = {8},
   Number = {2},
   Pages = {37-57},
   Year = {2007} }



@article{
schwehr2007f,
   Author = {Schwehr, K.},
   Title = {AIS Binary Messages, Domain Examples and A case for a XML message definition language},
   Journal = {RTCM SC121 Working Group on Expanded Use of AIS with VTS},
   Volume = {15-Nov-2007},
   Pages = {47},
   Year = {2007} }



@inproceedings{
schwehr2007e,
   Author = {Schwehr, K. and Hatch, L. and Thompson, M. and Wiley, D.},
   Title = {Google Earth Visualizations of the Marine Automatic Identification System (AIS): Monitoring Ship Traffic in National Marine Sanctuaries},
   BookTitle = {AGU Fall 2007},
   Address= {San Francisco},
   Publisher = {AGU},
   Abstract = {The Automatic Identification System (AIS) is a new technology that provides ship position reports with location, time, and identity information without human intervention from ships carrying the transponders to any receiver listening to the broadcasts.  In collaboration with the USCG's Research and Development Center, NOAA's Stellwagen Bank National Marine Sanctuary (SBNMS) has installed 3 AIS receivers around Massachusetts Bay to monitor ship traffic transiting the sanctuary and surrounding waters.  The SBNMS and the USCG also worked together propose the shifting the shipping lanes (termed the traffic separation scheme; TSS) that transit the sanctuary slightly to the north to reduce the probability of ship strikes of whales that frequent the sanctuary.  Following approval by the United Nation's International Maritime Organization, AIS provided a means for NOAA to assess changes in the distribution of shipping traffic caused by formal change in the TSS effective July 1, 2007.  However, there was no easy way to visualize this type of time series data.

We have created a software package called noaadata-py to process the AIS ship reports and produce KML files for viewing in Google Earth.  Ship tracks can be shown changing over time to allow the viewer to feel the motion of traffic through the sanctuary.  The ship tracks can also be gridded to create ship traffic density reports for specified periods of time.  The density is displayed as map draped on the sea surface or as vertical histogram columns.  Additional visualizations such as bathymetry images, S57 nautical charts, and USCG Marine Information for Safety and Law Enforcement (MISLE) can be combined with the ship traffic visualizations to give a more complete picture of the maritime environment.

AIS traffic analyses have the potential to give managers throughout NOAA's National Marine Sanctuaries an improved ability to assess the impacts of ship traffic on the marine resources they seek to protect.  Viewing ship traffic data through Google Earth provides ease and efficiency for people not trained in GIS data processing.},
 Year = {2007} }



@article{
schwehr2007d,
   Author = {Schwehr, K. D. and McGillivary, P. A.},
   Title = {Marine Ship Automatic Identification System (AIS) for Enhanced Coastal Security Capabilities: An Oil Spill Tracking Application},
   Journal = {Oceans07 MTS/IEEE},
   Pages = {9},
   Year = {2007} }



@inproceedings{
schwehr2007c,
   Author = {Schwehr, Kurt and Alexander, Lee},
   Title = {Specification Format for AIS Binary Messages for Providing Hydrographic-related Information},
   BookTitle = {US Hydro},
   Editor = {Gee, Lindsay},
   Address= {Norfolk, VA},
   Abstract = {UNH is working with the USCG and NOAA to use XML (Extensible Markup Language) to define binary messages for maritime-based AIS (Automatic Identification System).  The draft specification format will enable hydrographic and maritime safety agencies to define message contents by providing a bit level description in XML (informally the "AIS Binary Message Decoder Ring").  This format improves the clarity of message specifications aiding both people defining the messages and software engineers implementing maritime systems. 
	The XML file specifies of the order, length, and type of fields following a subset of that used by the ITU-R.M.1371-1.  To reduce issues with accidents and errors caused by miscommunication (e.g., the Mars Climate Orbiter loss in 1999), units are declared for the numerical values, along with the standard descriptions and notes.  The specification is independent of programming language (e.g., can be implemented in C, C++, C#, Java, Python, etc.) to allow vendors to integrate the system into their individual design requirements. Along with the XML specification, the draft specification contains a reference implementation of an AIS XML to Python compiler written in Python that has been released as open source under the GNU General Public License (GPL) version 2. A XML schema and an additional program will provide validation of the XML message definitions.  A XSLT style sheet produces reference documentation in 'html' format.  Although the XML message definition file specifies the order, size, and type of the bit stream, it does not specify semantics or how binary messages should be presented on an ECDIS or other display device.  
	A demonstration of this specification for sending tide/water level messages will be part of the Elizabeth River Demonstration Project at the US HYDRO 2007.},
 Year = {2007} }



@inproceedings{
schwehr2007b,
   Author = {Schwehr, Kurt and Sullivan, Briana and Gardner, James V.},
   Title = {Google Earth Visualizations: Preview and Delivery of Hydrographic and Other Marine Datasets},
   BookTitle = {US Hydro},
   Address= {Norfolk},
   Note  = {Accepted 06 Feb 2007},
   Abstract = {Existing hydrographic data analysis and visualization tools are very powerful, but lack easy access to web data management tools. Virtual globe software provides a gateway to a host of important data products in formats usable by specialized tools such as CARIS, Fledermaus, and Arc/Info.  With virtual globe interfaces, users see complimentary and consistent geographic representations of available data in an easy-to-navigate format.  We present a preview of visualizations that build upon virtual globe software.  These examples are viewed in Google Earth, but could also be implemented in a number of alternative programs (e.g. NASA World Wind, Dapple, OSSIM Planet).
We have assembled Google Earth visualizations from three datasets to illustrate each of the four primary types of data (handle point, line, area, and time data).  The USCG Marine Information for Safety and Law Enforcement (MISLE) database of ship incidents illustrates point data.  A short sample of the USCG National Automatic Identification System logs (N-AIS) demonstrates rendering of line data.  Area data is exemplified in the United Nations Convention f the Law of the Sea (UNCLOS) multibeam bathymetry.  Point, line and area data are combined to present a preview of S57 chart information.  Finally, the MISLE database uses time to show maritime incidents that occurred in US waterways. 
The visualizations for our initial work were created with hand coding and small scripts.  However, tools such as Fledermaus and RockWare have added Google Earth export functionality that makes authoring Google Earth resources easy to construct. For large dataset that require additional processing and analyses, Google Earth visualizations can offer users a range of download formats and suggest what software to use.  We believe that this virtual globe-based-approach can make geospatial data sets more widely accessible via the world-wide-web.},
 Year = {2007} }



@article{
norris2007,
   Author = {Norris, A.},
   Title = {AIS Implementation - Success or Failure?},
   Journal = {The Journal of Navigation},
   Volume = {60},
   Pages = {1-10},
   Year = {2007} }



@article{
   Author = {Noggle, J. and Royal, J.},
   Title = {Hawkeye Technology and the Sensor Manager},
   Journal = {USCG PierSystem},
   Year = {2007} }



@article{
ds2007,
   Author = {Navigation, Electronics &},
   Title = {Satellite AIS from USCG},
   Journal = {Digital Ship},
   Pages = {26},
   Year = {2007} }



@article{
harati2007,
   Author = {Marati-Mokhtari, A. and Wall, A. and Brooks, P. and Wang, J.},
   Title = {Automatic Identifcation System (AIS): Data Reliability and Human Error Implications},
   Journal = {The Journal of Navigation},
   Volume = {60},
   Pages = {373-389},
   Year = {2007} }



@article{
itu1371-2007,
   Author = {ITU},
   Title = {Recommendation ITU-R M.1371-3
Technical characteristics for an automatic identification system using time division multiple access in the VHF maritime mobile band},
   Journal = {ITU},
   Volume = {ITU-R M.1371},
   Number = {3},
   Pages = {133},
   Year = {2007} }



@article{
   Author = {IMO},
   Title = {Guidelines on Annual Testing or the Automatic Identification System (AIS)},
   Journal = {IMO},
   Volume = {MSC.1/Circ.1252},
   Pages = {5},
   Year = {2007} }



@techreport{
80_465_CDV,
   Author = {IEC},
   Title = {IEC 62320-2 Ed.1: Maritime navigation and radiocommunication equipment and systems Ð Automatic identification system (AIS) Ð Part 2: AIS AtoN stations Ð Minimum operational and performance requirements, methods of testing and required test results},
   Institution = {IEC},
   Note = {Draft not for use},
   Number = {80/465/CDV},
   Type = {Committee Draft For Vote},
   Month= {2007-01-12},
 Year = {2007} }



@article{
   Author = {Group, Notices to Skippers Expert},
   Title = {Notices to Skippers for Inland Navigation},
   Journal = {?},
   Volume = {Edition 1.2.1},
   Year = {2007} }



@techreport{
fidus2007,
   Author = {fidus},
   Title = {AIS: A Guide to System Development
Thoughts on AIS System Design from an R&D Perspective},
   Institution = {fidus},
   Type = {Version 1.0},
   Month= {July 10, 2007},
   Abstract = {This document addresses design challenges for Automatic
Identification Systems (AIS). Designed to prevent marine
collisions, AIS is a marine band data network based on a selforganizing
TDMA access protocol. The SOTDMA protocol poses
significant hurdles for electronic designers. In this paper we
discuss and clarify protocol structures and specifications, as
well as architecture implementation. We present a step-by-step
process for encoding or decoding AIS messages. We highlight
key, system-level considerations for the data-link layer, GPS and
transmit synchronization, DSC and AIS channel deviation, power
challenges and testing. As well, we shed light on NMEA 0183Õs
frequently misconstrued terms concerning back-end interface
design. We outline a new, software-defined radio approach to
AIS design, developed by RF experts at Fidus Systems.
AIS: A Guide to System Development provides practical
guidance for design engineers, project managers and
engineering leaders in the fields of AIS, RF and
software-defined radio.},
 Keywords = {Automatic Identification System
AIS
DSC
RF
software defined radio
data link layer
VHF marine band data network
marine band channels
VDL
VDM
VDO
search and rescue (SAR) aircraft
ITU
IALA
IMO
UTC synchronization
SOTDMA
ITDMA
RATDMA
NMEA 0183 protocol},
   Year = {2007} }



@article{
ferraro2007,
   Author = {Ferraro, G. and Bernardini, A. and David, M. and Meyer-Roux, S. and Meuellenhoff, O. and Perkovic, M. and Tarchi, D. and Topouzelis, K.},
   Title = {Towards an operational use of space imagery for oil pollution monitoring in the Mediterranean basin: A demonstration in the Adriatic Sea},
   Journal = {Marine Pollution Bulletin},
   Volume = {54},
   Pages = {403-422},
   Year = {2007} }



@article{
ellison2007,
   Author = {Ellison, B},
   Title = {Class B AIS is coming, growing pains included},
   Journal = {Professional Mariner},
   Volume = {104},
   Pages = {59-61},
   Year = {2007} }



@article{
eide2007,
   Author = {Eide, M. S. and Endresen, O. and Brett, P. O. and Ervik, J. L. and Roand, K.},
   Title = {Intelligent ship traffic monitoring for oil spill prevention: Risk based decision support build on AIS},
   Journal = {Marine Pollution Bulletin},
   Volume = {52},
   Pages = {145-148},
   Year = {2007} }



@article{
   Author = {Dryden, S. D.},
   Title = {Statement of Stephen D. Dryden On Maritime Domain Awareness and Vessel Tracking Before the U.S. House of Representatives Committee on Homeland Security Subcommittee on Border, Maritime, and Global Counterterrorism},
   Pages = {4},
   Year = {2007} }



@inproceedings{
brennan2007,
   Author = {Brennan, Rick and Gallagher, Barry and Riley, Jack and Schwehr, Kurt and Alexander, Lee},
   Title = {Tide Aware ENC: Demonstration of an Operational Concept},
   BookTitle = {US Hydro},
   Editor = {Gee, Lindsay},
   Address= {Norfolk, VA},
   Note  = {Have not heard if this abstract was accepted.},
   Abstract = {The size and draft of ships calling on United States ports has steadily grown over the past 50 years.  Today's vessels may be transiting into port with as little as 0.3 meters (one foot) beneath their keel.  This increase in the size of the vessel has caused the mariner to ask questions of the chart and its data that the tradition products, both paper and electronic versions, are incapable of answering.  An operational solution to this problem may be constructed using existing technologies.  High resolution bathymetry and their associated uncertainties provide the foundation for using algorithmic cartography to render the data in new, more intuitive ways.  When this high resolution bathymetric foundation is combined with real-time water levels, telemetered to the underway vessel via the Automatic Identification System (AIS), it is possible to create an electronic navigational chart which is capable of displaying a Òtide-awareÓ ship's safe contour to the mariner.  Since both the bathymetry and the water level interpolation method have a computed uncertainty value, an expressed uncertainty of the charted display may also be presented.  

This paper describes an operational model for how this may achieved and discusses results from initial field trials.  In particular, tidal information is provided in XML format and relayed via AIS to all vessels underway within radio range of the shoreside AIS transmitter.  Once this data is received aboard the vessel, it is utilized by a software engine developed in Coast Survey's Hydrographic Systems and Technology Program (HSTP) which computes a water surface model based on the Tidal Constituent and Residual Interpolation (TCARI) method.  This water surface model is then provided to navigation software also developed in HSTP called ECS++ (for Electronic Chart System with enhancements).  This software then combines the high resolution bathymetry with the water surface to arrive at a bathymetric model with values representative of the actual water depths.  This model is in turn displayed in the ECS++ display window to show the available water within the navigational theater, based on modeled water levels.   Using this methodology, ECS++ is capable of estimating the water level at a vessel's position for any location and instance in time.},
 Year = {2007} }



@article{
   Author = {(CCNR), Central Commision for the Navigation of the Rhine},
   Title = {Notices to Skippers for Inland Navigation 
International Standard},
   Volume = {1.2.1},
   Pages = {142},
   Year = {2007} }



@inproceedings{
   Author = {Vorbach, J.E. III},
   Title = {Vessel Identification Systems and Port Security},
   BookTitle = {Transportation Research Board of the National Academies},
   Address= {Washington, DC},
   Publisher = {TRB},
   Volume = {86th Annual Meeting},
   Pages = {29},
   Abstract = {Situate Vessel Tracking Efforts in the context of the totality of layered maritime security effort and pursuit of Maritime Domain Awareness
Update developments in AIS systems
Update NAIS implementation and future plans
Concluding assessment:
Accomplishments
Challenges
Future},
 Year = {2006} }



@article{
tetreault2006,
   Author = {Tetreault, B.},
   Title = {Automatic Identification System: The use of AIS in support of Maritime Domain Awareness},
   Journal = {USCG Prceedings},
   Volume = {Fall},
   Pages = {27-30},
   Year = {2006} }



@article{
   Author = {plc, AEA Technology},
   Title = {Overview of collision detection in the UKCS},
   Journal = {Health and Safety Executive},
   Volume = {RR514},
   Pages = {92},
   Year = {2006} }



@article{
pecar2006,
   Author = {Pecar-Ilic, J. and Ruzic, I.},
   Title = {Application of GIS and Web technologies for Danube waterway data management in Croatia},
   Journal = {Environmental Modeling & Software},
   Volume = {21},
   Pages = {1562-1571},
   Year = {2006} }



@inproceedings{
mcgillivary2006b,
   Author = {McGillivary, P. A. and Curcio, Joseph and Fall, Kevin and Maffei, Andy and Schwehr, K. and Kitts, Chris and Twiggs, Bob},
   Title = {Autonomous Surface Vessels for Ais-Sea Flux and Satellite Calibration / Validation Studies},
   BookTitle = {1st Joint GOSUD/SAMOS Workshop},
   Address= {Bolder, CO},
   Publisher = {Shipboard Automated Meteorilogical and Oceanographic System initiative and Global Ocean Surface Underway Data project},
 Year = {2006} }



@techreport{
luft2006,
   Author = {Luft, L. and Spaulding, J.},
   Title = {AIVDM metadata snr toa ss id time},
   Institution = {USCG RDC},
   Type = {Unofficial Specification},
   Month= {20 April 2006},
   Abstract = {Prodivides the definition of the N-AIS rev 0 NMEA extension fields},
 Year = {2006} }



@article{
hammond2006,
   Author = {Hammond, T. and McIntyre, M. and Lapinski, L. and Chapman, D.},
   Title = {The Role of Self-Reporting Systems in Marine Security for Special National Events},
   Journal = {Defense R&D Canada},
   Pages = {15},
   Year = {2006} }



@article{
mdadscoi2006,
   Author = {group, MDA DS COI working},
   Title = {The Maritime Domain Awareness Data Sharing Comminity of Interest Pilot: Data Vocabulary and Schemas},
   Journal = {MDA DS COI},
   Volume = {1},
   Number = {0},
   Pages = {53},
   Year = {2006} }



@article{
davenport110,
   Author = {Davenport, M. and Risley, C.},
   Title = {Information Visualization: The State of the Art for Maritime Domain Awareness},
   Journal = {Defence Research and Development Canada - Atlantic},
   Volume = {CR 2006-122},
   Pages = {180},
   Year = {2006} }



@techreport{
unris2006,
   Author = {Committee, Inland Transport},
   Title = {Establishment of Common Principles and Technical Requirements for a Pan-European River Information Services (RIS)
International Standard for Tracking and Tracing on Inland Waterways (VTT)},
   Institution = {UN Economic Commission for Europe},
   Note = {ECE-TRANS-SC3-2006-10e-RIS.pdf},
   Number = {ECE/TRANS/SC.3/2006/10},
   Type = {UN Report},
   Month= {11-13 Oct 2006},
   Abstract = {The concept of River Information Services (RIS) has emerged from several European research projects, aiming at increasing safety and efficiency of inland waterway transport.

The European Commission, the CCNR and the Danube Commission have recognized the need for means of automatic exchange of navigational data between ships and between ship and shore for automatic identification and tracking and tracing solutions in inland navigation.

In maritime navigation, IMO has introduced the Automatic Identification System (AIS). All seagoing vessels on international voyage falling under SOLAS convention Chapter 5 have to be equipped with AIS since the end of 2004. The Guidelines and Recommendations for River Information Services (RIS Guidelines 2004) of PIANC and CCNR define Inland-AIS as important technology.

The European RIS Platform established in 2003 the expert group for tracking and tracing. The main task of this expert group is the development and maintenance of a European wide harmonised vessel tracking and tracing standard for inland navigation. Because of mixed traffic areas it is important that the standards and procedures for inland shipping are compatible with already defined standards and procedures for seagoing navigation.

To serve the specific requirements of inland navigation, AIS has been further developed to the so called Inland AIS Standard while preserving full compatibility with IMOÕs maritime AIS and already existing standards in inland navigation.

Future developments could lead to alternative vessel tracking and tracing systems, which however have to be compatible with maritime AIS.

In this document chapter 1 describes the functional specifications related to vessel tracking and tracing in inland navigation. In chapter 2, the inland AIS standard is described, including the standard inland tracking and tracing messages. An overview of definitions of services and players is given in ANNEX A: DEFINITIONS.},
 Year = {2006} }



@inproceedings{
   Author = {Kuiters, L.},
   Title = {Vessel Tracking and Tracing Standards: Development and Functionality of Tracking and Tracing},
   BookTitle = {COMRIS},
   Pages = {16},
 Year = {2005} }



@inproceedings{
jandrisits2005,
   Author = {Jandrisits, M. and de Mateo, J. C. and Abwerzger, G.},
   Title = {EGNOS Terrestrial Regional Augmentation Networds Based on AIS for River Information Services},
   BookTitle = {ION GNSS International Technical Meeting of the Satellite Division},
   Address= {Long Beach, CA},
   Volume = {18},
   Pages = {827-832},
   Abstract = {Within the ESA Advanced Research Telecommunications 
program ARTES-5, the project GALEWAT (Galileo and 
EGNOS for Waterway Transport) aims at introducing 
EGNOS into River Information Services (RIS) through 
the Automatic Identification System (AIS), a link that is 
mandatory for seagoing vessels above 300 GT.   
 
The GALEWAT project comprises several phases: 
During the initial definition phase, the system architecture 
and user equipment have been defined in line with 
standards and international recommendations. This phase 
was followed by the implementation phase, aiming at 
developing and setting up the equipment. Finally, the 
project will be completed by an extensive demonstration 
phase, which is currently under execution. Up to now, 
public GALEWAT demonstrations in Vienna (Austria), 
and Lisbon (Portugal) have been successfully executed. 
The last demonstration in Constanta (Romania) will take 
place in fall 2005. These demonstration sites have been 
chosen to test and demonstrate the GALEWAT system in 
different environments: river navigation, harbour approach, and open sea operations.

The paper gives a short idea of River Information 
Services and an overview of the GALEWAT project. The 
main part concentrates on the presentation of field 
measurement results, which were collected in Lisbon, to 
show the performance of the GALEWAT concept. 
Finally, the paper presents an overview of user feedback 
resulting from the first two public demonstrations.},
 Year = {2005} }



@techreport{
80_427_CDV,
   Author = {IEC},
   Title = {Maritime navigation and radiocommunication equipment and systems - Automatic Identification Systems - Part 1: AIS Base Stations - Minimum operational and performance requirements - methods of test and required test results},
   Institution = {IEC},
   Note = {Draft not for use},
   Number = {80/427/CDV},
   Type = {Committee Draft for Vote (CDV)},
   Month= {2005-12-16},
 Year = {2005} }



@techreport{
80_405_CDV,
   Author = {IEC},
   Title = {Maritime navigation and radiocommunication equipment and systems - Class B shipborne equipment of the Automatic Identification System (AIS) using CSTDMA techniques - Operational and performance requirements, methods of test and required test results},
   Institution = {IEC},
   Note = {Draft should not be used},
   Number = {80/405/CDV},
   Type = {Committee Draft for Vote (CDV)},
   Month= {2005-03-11},
 Year = {2005} }



@article{
iala1050-2005,
   Author = {IALA},
   Title = {IALA Guideline No. 1050 On the Management and Monitoring of AIS Information},
   Journal = {IALA},
   Volume = {1050},
   Number = {1},
   Pages = {8},
   Year = {2005} }



@article{
ialaA124-2005,
   Author = {IALA},
   Title = {IALA Recommendation A-124 On Automatic Identification System (AIS) Shore Station and Networking Aspect relating to the AIS Service},
   Journal = {IALA},
   Volume = {A-124},
   Number = {1.2},
   Pages = {220},
   Year = {2005} }



@inproceedings{
bober2005,
   Author = {Bober, S.},
   Title = {AIS for Inland Navigation: Development of the Inland AIS standard},
   BookTitle = {COMPRES workshop on Automatic Identification in Inland Navigation},
 Year = {2005} }



@article{
page2004,
   Author = {Page, E.},
   Title = {Automated Secure Vessel Tracking System (ASVTS)},
   Journal = {Marine Exchange of Alaska},
   Pages = {2,4},
   Year = {2004} }



@inproceedings{
obad2004,
   Author = {Obad, D. and Bosnjak-Cihlar},
   Title = {Benefits of Automatic Identification System within Frame of River Information Services},
   BookTitle = {International Symposium Electronics in Marine},
   Address= {Zadar, Croatia},
   Volume = {46},
   Pages = {5},
   Abstract = {The paper deals with the framework architecture of the River Information Services, the main objectives and the application design. Three RIS information levels and the Vessel Traffic Services were explained and the benefits of using AIS within these services were given.  The functionality of Inland AIS was defined and compared to the maritime standard.},
 Keywords = {River Information Services
RIS
Automatic Identification System
AIS
Fairway Information
FI
Tactical Traffic Information
VI
Stra tegic Traffic Image
STI
Vessel Traffic Services
VTS},
   Year = {2004} }



@article{
ris2004,
   Author = {Inland Transport Committee, Working Party on Inland Water Transport},
   Title = {Geuidlines and Recommendations for River Information Services},
   Journal = {Economic Commission for Europe},
   Volume = {TRANS/SC.3/165},
   Number = {Resulution No. 57},
   Pages = {46},
   Year = {2004} }



@article{
ialav125-2004,
   Author = {IALA},
   Title = {The use and presentation of symbology at a VTS Centre (including AIS)},
   Journal = {IALA},
   Volume = {V-125},
   Number = {2},
   Pages = {13},
   Year = {2004} }



@article{
iala1028-2004,
   Author = {IALA},
   Title = {IALA Guideline No. 1028 On The Automatic Indentification System (AIS): Operational Issues, Edition 1.3},
   Volume = {1},
   Number = {I},
   Pages = {131},
   Year = {2004} }



@article{
   Author = {Center, NOAA NWS National Data Buoy},
   Title = {USCG/NOAA Automatic Identification System (AIS) on Data Buoys and C-Man Stations: System Requirements Specification},
   Year = {2004} }



@article{
   Author = {Systems, Committee for Evaluating Shipboard Display of Automatic Identification},
   Title = {Shipboard Automatic Identification System Displays: Meeting the Needs of Mariners},
   Journal = {Transportation Research Board of the National Academies},
   Volume = {SR},
   Number = {273},
   Pages = {213},
   Year = {2003} }



@article{
imo227-2003,
   Author = {IMO},
   Title = {Guidelines for the Installation of a Shipborne Automatic Identification System (AIS)},
   Journal = {IMO},
   Volume = {SN/Circ. 227},
   Number = {E},
   Pages = {14},
   Year = {2003} }



@article{
ialaA126-2003,
   Author = {IALA},
   Title = {IALA Recommendation A-126 On The Use of the Automatic Identification System (AIS) in Marine Aids to Navigation, Edition 1},
   Journal = {IALA},
   Volume = {A-126},
   Number = {1},
   Pages = {24},
   Year = {2003} }



@article{
sls2002,
   Author = {USDOT, Volve Transportation System Center},
   Title = {St. Lawrence Seaway AIS Data Messaging Formats and Speficiations
Harmonized with U.S. Coast Guard PAWSS AIS Messages},
   Volume = {Revision 4.0A},
   Year = {2002} }



@techreport{
   Author = {Lewandowski, M. J. and Pietraszewski, D. J.},
   Title = {Automatic Identification System
A General Discussion of Development, Application, and Implementation},
   Note = {For USCG R&D Center Project 2410.5-Vessel Traffic Management Research},
   Month= {June 20, 2002},
   Abstract = {This introduces the Automatic Identification System (AIS) and discusses implementation issues. Class A international shipborne device standards are complete, and work continues on Class B and base station standards. This material is current as of June 2002. The paper addresses some Coast Guard specific issues but may interest other members of the Marine Transportation System (MTS) community. 

An Automatic Identification System (AIS) has been under development since 1997 when the International Maritime Organization (IMO) drafted performance recommendations for a worldwide system. The IMO AIS recommendations state that AIS should improve safety Òby assisting navigation of ships, protection of the environment, and operation of Vessel Traffic Services (VTS), by satisfying the following functional requirements: in a ship-to-ship mode for 
collision avoidance; as a means for littoral States to obtain information about a ship and its cargo; and as a VTS tool, i.e. ship-to-shore (traffic management).Ó1 

In 1998, the Coast Guard Research and Development Center (R&DC) began participation Òin the international development of AIS technology through the related work of organizations, including the International Electrotechnical Commission (IEC), International Telecommunications Union (ITU), National Marine Electronics Association (NMEA), etc.,Ó and began to develop Òtools, including a computer simulation, to assess the capability and capacity of a network of AIS devices.Ó2 Since then, R&DC emphasis has been on direct support for the 
international development and deployment of AIS technology. The R&DC is also active in the International Association of Marine Aids to Navigation and Lighthouse Authorities (IALA) development of the definition and description of AIS base-stations and infrastructure. IALA has been the primary organization for sponsoring and coordinating AIS development.},
 Year = {2002} }



@article{
ialaA123-2002,
   Author = {IALA},
   Title = {Recommendation on the Provision Of Shore Based Automatic Identification Systems (AIS)},
   Journal = {IALA Recommendation},
   Volume = {A-123},
   Pages = {5},
   Year = {2002} }



@article{
iala2002,
   Author = {IALA},
   Title = {IALA Guidelines on the Universal Automatic Identification System (AIS): Technical Issues Edition 1.1},
   Journal = {IALA},
   Volume = {1},
   Number = {II},
   Pages = {134},
   Year = {2002} }



@article{
   Author = {Consulting, Marine Management},
   Title = {2002 Test of AIS
A step on the path to AIS-Aided Navigation},
   Pages = {47},
   Year = {2002} }



@techreport{
80_330e_PAS,
   Author = {IEC},
   Title = {Maritime navigation and radiocommunication equipment and systems - Digital interfaces - Part 100: Single talker and multiple listeners - Extra requirements to IEC 61162-1 for the UAIS},
   Institution = {IEC},
   Note = {This is a draft only and should not be used},
   Number = {IEC/PAS 61162-100 Ed.1},
   Type = {Draft Publicly Available Specification},
   Month= {2001-12-07},
 Year = {2001} }



@article{
sole1999,
   Author = {Sole, R. L. and Bedford, B. and Patrick, G.},
   Title = {Lower Mississippi River Ports and Waterways Safety System (PAWSS) RF Coverage Test Results},
   Journal = {NTIA Report},
   Volume = {00},
   Number = {374},
   Pages = {29},
   Year = {1999} }



@article{
nmea0183-1992,
   Author = {NMEA},
   Title = {NMEA 0183: Standard for Interfacing Marine Electronic Devices},
   Journal = {NMEA},
   Volume = {2.00},
   Pages = {81},
   Year = {1992} }