{"id":1242,"date":"2011-09-14T23:14:30","date_gmt":"2011-09-14T22:14:30","guid":{"rendered":"https:\/\/www.entropywins.wtf\/blog\/?p=1242"},"modified":"2014-03-17T23:15:05","modified_gmt":"2014-03-17T22:15:05","slug":"earth-and-kml-support-in-semantic-maps-1-0-3","status":"publish","type":"post","link":"https:\/\/www.entropywins.wtf\/blog\/2011\/09\/14\/earth-and-kml-support-in-semantic-maps-1-0-3\/","title":{"rendered":"Earth and KML support in (Semantic) Maps 1.0.3"},"content":{"rendered":"
\n

Yesterday I released version 1.0.3 of the Maps<\/a> and Semantic Maps<\/a> MediaWiki extensions. This release re-introduces Google Earth support, this time for Google Maps v3, and enhances the KML\/KMZ support for this mapping service as well. Many thanks go to Jon Povey for funding the implementation of these features! Since I didn\u2019t make any release announcements for 1.0.1 or 1.0.2, I\u2019ll just include changes made in these versions as well, effectively treating this as the release after 1.0.<\/p>\n

KML\/KMZ support<\/strong><\/p>\n

The Google Maps v3 service now supports 2 new KML related parameters: kml and gkml. Both accept a url pointing to a KML (or KMLZ) file. The first one uses a KML parsing library (geoxml3<\/a>) included in the extension to translate the features described in the KML file into elements to place onto the map. This is very nice for people that do not want to be dependent on third party services, but sadly enough, the library is somewhat limited. It lacks support for more advanced KML features such as polygons and paths. The gkml parameter uses Googles KML service, which pulls the KML file to some Google server, and then decides if it should be send to the client (for simple and small files), or if it should be rendered server side and send as tiles to the client (for big files or files containing advanced features such as polygons).<\/p>\n

You can now also choose if you want the map to rezoom after the KML layers have been loaded or not using the kmlrezoom parameter. KML layers will load a bit after the map, since they require extra resources to be loaded, and there is no need to let the user wait to see the normal map until those are done loading.<\/p>\n

\"A<\/a><\/p>\n

Google Earth support<\/strong><\/p>\n

Maps already has support for Google Earth since on of it\u2019s earliest versions. This was quite easy to achieve as Google Maps v2 natively supported it. Now with the switch to Google Maps v3 in Maps 1.0, people asked for Google Maps support in that as well. Unfortunately Google Earth is not natively supported here. Maps now provides support for GE using the Google Maps utility library v3<\/a>. The earth type can be enabled by adding \u201cearth\u201d to the types parameter, or setting it as the default type using \u201ctype\u201d. Do however note that due to this not being officially supported by Google, it has some deficiencies. For one, when switching to GE, the map controls won\u2019t be displayed any more, preventing you from switching back. Also, the GE plugin is only supported on Windows and Mac, so won\u2019t be usable for mobile or Linux users.<\/p>\n

A completely new thing added in 1.0.3 is the tilt parameter, which, as you can probably guess, allows you to set the initial tilt of the GE layer.<\/p>\n

\"Google<\/a><\/p>\n

Full list of changes since 1.0:<\/strong><\/p>\n