NTS webservices Flanders

1

• NTS webservices Flanders
• By Eric Smets

2
Actual status

• Functional specifications ready(NTS)?
• Global overview of Webservices ready
• Technical requirements

3
Functional Specs

• All the available applications should be able to
  requests the notices to skippers based upon
• Geografical area
• Actual open Notices
• Type of Notice
• Route
• Display format
• Xml or pdf to print

4
What kind of specification ?

• Usage of plain SOAP standards
• As defined in the NTS German paper.
• Usage of geometry soap services
• Defined by the OGC

5
OGC

• References are made by
• http//www.opengeospatial.org/ References made by
  the open geospatial consortium
• Defines search services, webservices and basic
  infrastructure elements (points, curves)?

6
PRO/ CON OGC

• Gis related requests possible
• A lot of software and infrastructure available
• Integration with maps possible (without
  programming)

• More specifications to be followed
• Major modifications in the XML
• All the NTS messages have to geo objects
• More complex for home made B2B app.

7
OGC webservices

• Usage of gis database to store NTS
• Table layout to be compatible in all countries
• WFS (only this is needed)?
• Feature services implemented
• Catalogue where all the services are availabel