Definition
An ACAN is a public notice indicating to the supplier community that a department or agency intends to award a contract for goods, services or construction to a pre-identified supplier, thereby allowing other suppliers to signal their interest in bidding, by submitting a statement of capabilities. If no supplier submits a statement of capabilities that meets the requirements set out in the ACAN, on or before the closing date stated in the ACAN, the contracting officer may then proceed with the award to the pre-identified supplier.
Definition of Requirements
The department of Natural Resources Canada (NRCan) has a requirement to develop and promote the Map Markup Language (MapML) format, which supports the on-demand integration of important standardized services available from the Canadian Geospatial Data Infrastructure (CGDI). GeoServer and PostGIS are key open source components used by organizations participating in the CGDI. As such, the main objective of the proposed contract is to implement MapML in GeoServer, while at the same time analyzing the requirements for potential changes to PostGIS that could be used by the MapML engine in GeoServer and other CGDI software.
The GeoServer-related requirements for the project include the implementation of MapML (text/mapml) as a format offering for the GeoServer Web Map Service (WMS) and Web Feature Service (WFS) layer / feature collection service endpoints.
The PostGIS-related requirement for the project include analysis, design and PostGIS community review for suitability of MapML-related requirements related to the ST_SubDivide(geom) function.
The project requirements include communicating the development results in the form of blog posts and presentations.
2.1 GeoServer - Enable MapML specification (text/mapml) as a format offering for WMS and WFS.
The administrative interface for this function should allow the server admin to designate a layer as being available in MapML only if the layer is available in one of the MapML projections (EPSG:3978, EPSG:3857, EPSG:5936). Every MapML document should contain basic layer / feature collection metadata, in the form of <head>, <title>, <meta> and <link> elements.
The admin interface for WFS should allow a feature collection that is available as CRS84 to be serialized as a WGS84 MapML document containing a link@rel=features and appropriate associated inputs.
The admin interface should allow the administrator to enable the layer as templated tile or image based MapML link templates, at the option of the administrator. (Typically, the presence of labels in a layer would argue against making the layer available via tiled link templates, but this is a judgement that the administrator should make for herself).
The admin interface should allow WMS queryable layers to emit MapML markup allowing them to be queried (a link@rel=”query” template) by the client. If the administrator chooses to enable MapML query templates, the admin interface should OPTIONALLY allow the entry of a link@title value via a text input field.
If the administrator enables MapML queries for a layer or feature collection, the admin interface should OPTIONALLY allow the map author to specify a MapML template for the GetFeatureInfo and GetFeature responses as text/mapml. The template should be processed on each GetFeatureInfo / GetFeature request and template variables be substituted from the server configuration information and feature-specific information, prior to being returned to the client, if applicable.
The server shall, where appropriate and identified by the administrator via its configuration, enable the serialization of time and other map dimensions as one or more <select><option …></select> as specified by the MapML specification. This function allows the end-user to choose the date/time or other map dimension variable values from a list of alternative defined values valid for the map layer at the moment the end-user accesses the map layer.
The server shall allow the administrator to designate a variable as a hidden domain shard input, in accordance with the MapML specification.
If there are alternate styles for a WMS layer for which MapML responses are enabled, the server should automatically generate document links in the head (link@rel=”style”) of the MapML response, one for each alternate style. Dereferencing such links SHOULD return a MapML document for that layer in that named style, with the other named styles for that layer represented as alternate links (link@rel=”style”) in that document. The current named style that is selected by the client should be tagged in the set of alternative style links by the addition of a second rel value for that one style only : link@rel=”self style”.
The admin interface should allow the administrator to enter the attributes of a licensing link to be placed in the head of the MapML response document for the WMS as a whole, or to override its value on a per-layer basis.2.2 PostGIS – Design and validate MapML support in the ST_Subdivide(geom) function
As another polymorphic form of the function (or other means to be negotiated with developer), such that the segments that are added to the geometry by the function are identified as array offsets OR give the function the ability to return MapML-encoded feature with the added segments marked up with <span>, or other markup passed as an argument. This design should be validated by the PostGIS steering committee. The resulting design does not have to be MapML-specific, but it must be useable for the markup use case.
2.3 Communication
Blog post about MapML integration into GeoServer
Presentation about MapML integration into GeoServer developed and delivered in person at a geospatial-themed public conference or meeting, such as FOSS4G or other similar venue. Travel expenses are not included.
3. Criteria for Assessment of the Statement of Capabilities
Any interested supplier must demonstrate by way of a statement of capabilities that they meet the following requirements:
Must have an established working relationship to the GeoServer and PostGIS open source projects.
Must have an expert understanding of the WMS and WFS Open Geospatial Consortium (OGC) standards. Must have expert understanding of the Simple Features for SQL OGC standard. Must have expert understanding of the PostGIS spatial data engine for PostgreSQL relational database. This expert understanding would be demonstrable by previous experience in each of the pertinent domains of at least 5 years.
Must have personnel with experience related to the work required as described in paragraph 2 available to complete the work as per the requirements described above.
Must be willing to release intellectual property developed in this project to Canada.
4. Trade Agreements
Trade Agreements are not applicable.
5. Justification for the Pre-Identified Supplier
We intend to deal directly with the supplier mentioned in section 10 below as it is the only known supplier that meets the mandatory criteria set out in paragraph 3 above.
Should Canada receive a statement of capabilities from a supplier that contains sufficient information to indicate that it meets the requirements set forth in this ACAN, a competitive process will be triggered with a technical and financial evaluation methodology of the bids proposed by the potential bidders.
6. Exception to the Government Contracts Regulations and applicable trade agreements
In accordance with the Government Contract Regulations (GCR) exception, Part 1, Section 6, (d) only one person or firm is capable of performing the contract.
The identified provider, Refractions Research, is the only one able to meet all of the criteria identified in paragraph 3 above.
The suggested Contractor is the only contractor capable of performing the work as described in paragraph 2, which will be made available to the public via the GeoServer and PostGIS projects.
7. Ownership of Intellectual Property
Canada intends to retain ownership of any Foreground Intellectual Property arising out of the proposed contract on the basis that the main purpose of the contract is to generate knowledge and information for public dissemination.
8. Contract Period
The period of the contract will be from Contract Award Date to March 31, 2019.
9. Estimated Cost
The estimated cost of the contract will not exceed $54,000.00 plus GST.
10. Name and Address of the Proposed Contractor
Refractions Research Inc.
1207 Douglas Street, Suite 419
Victoria, BC
V8W 2E7
11. Suppliers’ right to submit a statement of capabilities
Suppliers who consider themselves fully qualified and available to provide the services/goods described herein, may submit a Statement of Capabilities in writing, preferably by e-mail, to the contact person identified in this Notice on or before the closing date and time of this Notice. The Statement of Capabilities must clearly demonstrate how the supplier meets the advertised requirements.
12. Closing Date
October 29, 2018 at 2:00 P.M. Eastern Daylight Saving Time (EDST).
13. Contract Authority
Lucie Lepage
Natural Resources Canada
Contracting Officer
580 Booth Street, room 5-D2-2
Ottawa, Ontario
K1A 0E4
Fax: 613-947-5477
E-mail: l••••••••@••••••.ca
