New Features in the Virtual Earth API and New Data Released

Over the weekend we released new features in the Virtual Earth API as well as new data.

New Features in the API:

  1. The VEDataType.VECollection supports now the import of 3D-collections
  2. Import of KML-data into a VEShapeLayer is now possible through VEDataType.ImportXML. Import of GPX-data works as well but is not officially supported yet.
  3. Localized Geocoding (‘Nizza’ the German word for ‘Nice’) is now found in France rather than as Niiza in Japan)
  4. Localized Driving Directions
    Just add the market to the URL for the VE MapControl like this where XX-YY can be
    1. en-ca,
    2. en-gb,
    3. en-us,
    4. ja-jp,
    5. cs-cz,
    6. da-dk,
    7. nl-nl,
    8. fi-fi,
    9. fr-fr,
    10. de-de,
    11. it-it,
    12. nb-no,
    13. pt-pt,
    14. es-es,
    15. sv-se,
    16. (zh-cn)

To use the localized driving directions you will have to set the routing options as folows:

var options = new VERouteOptions();
options.UseMWS =


Data Release

I’m sure you will find the whole list shortly on Steve Lombardi’s and Chris Pendleton’s blogs but as a teaser:

  • There is new high resolution imagery for England, Scotland and Wales, the US, Canada and Japan
  • More oblique aerial images in the US and Canada as well as in Europe (Germany: 5 cities, Spain: 19 cities, Sweden: 19 cities, Denmark: 1 city, Norway: 1 city, Belgium: 1 city, Switzerland: 2 cities, Finland 1 city). For a full list of available Bird’s Eye imagery outside North America see
  • A lot of 1m satellite imagery all over the world

In total the data release contained another 33.7 TB of data.

Technorati Tags: , , ,
This entry was posted in Uncategorized. Bookmark the permalink.

3 Responses to New Features in the Virtual Earth API and New Data Released

  1. John says:

    Thanks for the update Johannes! The SSL version has been a very common request.

  2. Martin says:

    Is there any special reason, why there is no 1m satelitte imagery nor any cities in birds-eye-veiw available in Austria?
    What I think is odd is that on the border to Italy for example, the higher res imagery ends and it seems to be cut by hand since it follows the border and not the tiles (the image tiles seem to be cut, as soon as a part of the tile covers austria). Why is this so? Legal reasons? Do you plan to update austria imagery any time soon?
    thanks for any answer!

  3. Unknown says:

    Import of KML-data into a VEShapeLayer is great news ! 
    It would be good to know what level of KML support is provided from KML 2.1 spec ? 

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s