Map Feature Language (MFL) Specification. Version 1.0

The Map Feature Language, MFL, is an XML language that enables content providers to provide map-based content without supplying the entire map. It supports a model where content from different providers can be overlaid on the same map. MFL was defined as part of the MapWeb project at IBM’s T. J. Watson Research Center.

MFL was designed to enable commonly portrayed map features to be defined textually. Currently, MFL supports the following kinds of features: icons, point-shapes, text, linestrings, polygons, multi-linestrings, multi-polygons, and image tiles. The geometry of each feature is described in geographic coordinates. (MFL allows the geometries to be described in any well-known geographic coordinate system, but MFL viewers are only
required to support the common latitude and longitude of WGS-84 coordinates.) The presentation of each feature is described using presentation attributes such as color, linewidth, font and font-size. This integration of geographic coordinates with presentation information is what gives MFL its unique role as presentation language for map features.

Feature geometry in MFL is specified with elements from the Basic Features specification of the Geography Markup Language (GML), defined by the Open Geospatial Consortium. Implementors of MFL interpreters should consult the GML specification directly [GML]. For convenience, some elements of GML are described here. Readers should note that the descriptions here are based on GML 2, whereas the latest version is GML 3. Some elements of GML 2 are deprecated in GML 3.

By: Jonathan P. Munson

Published in: RC24318 in 2007

LIMITED DISTRIBUTION NOTICE:

This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.

RC24318.pdf

Questions about this service can be mailed to reports@us.ibm.com .