Share via

Requirements for Polygon Data Sources

  • Article

IMPORTANT: MapPoint Web Service was retired on November 18, 2011. Please see https://msdn.microsoft.com/en-us/library/dd877180.aspx for a list of current Bing Maps APIs.

Note

Numbers given below are in the U.S. format, where a comma separates thousands.

Your polygon data source files must meet the following requirements:

  • File type Your file must be a valid XML file in Microsoft Office Access 2002 or Microsoft Office Access 2003 XML format with an embedded schema. Delimited flat files are not supported. In addition to the standard World Wide Web Consortium (W3C) namespace declaration, the file must include the Microsoft Access namespace declaration as shown here: <root xmlns:xsd='https://www.w3.org/2001/XMLSchema' xmlns:od='urn:schemas-microsoft-com:officedata'>. Also, the schema must include the tag <xsd:any namespace='##other' /> to indicate that polygon geometry is included in the file.

  • Field definitions Fields in the data source must be defined according to Microsoft Access field types and field sizes. For example, <xsd:element name='EntityID' minOccurs='0' od:jetType='integer' od:sqlSType='smallint' type='xsd:short'/>.

  • File size Each polygon data source must contain at least one entity, and the file cannot exceed 100 megabytes (MB). If any values in the first row of data are not valid, the file cannot be uploaded. If the values in the first row are valid, errors in subsequent rows will not cause an upload job to fail, but the values that are not valid are either truncated or cleared.

    Files can be compressed into a zip file format. For additional information about the file schema and format, see Formatting a Polygon Data Source.

  • Required columns Your data source file must contain EntityID, EntityGeometry, Latitude and Longitude fields for each entity. For an explanation of the contents of these fields, see Formatting a Polygon Data Source.

  • Number of cells A data source can contain a maximum of 8.75 million searchable non-Boolean cells. This limit includes cells in the columns that are required (EntityID, EntityGeometry, Latitude, and Longitude). The total does not include cells of type info or keyword . In addition, the maximum number of Boolean fields for each entity is 200.

  • Number of entities Polygon data sources can contain a maximum of 100 entities, even if the total number of cells for that data source does not exceed the maximum.

  • Number of polygon vertices per entity Polygon data sources can contain a maximum of 500 vertices per polygon entity.

Note

MapPoint Web Service has a downloadable tool available for converting industry-standard polygon files to MapPoint format. If you are interested in accessing this tool, contact mpnet@microsoft.com.

See Also

Concepts

Formatting a Polygon Data Source
MapPoint Web Service Customer Data Sources