Instead of going through Babel to support KML files in Exhibit (which essentially views KML as a distinct data source and container of items), I'd like to look at it from another perspective.
Why can't we support KML simply as a field in the items[] array of an existing data source? The same with GeoRSS for that matter. How about something simple, like ex:kml = field_name_with_link_to_kml ex:georss = field_name_with_link_to_georss Google Maps supports KML and GeoRSS natively using the GGeoXml() function. Take a look at these two examples: http://code.google.com/apis/maps/documentation/examples/geoxml-rss.html http://code.google.com/apis/maps/documentation/examples/geoxml-kml.html To me, this is identical to adding points (GMarker), lines (GPolyline) and polygons (Gpolygon.) Ideally, you would like to have any/all of them displayed on a map at the same time. That could even be a geotype or geometery facet..."show me all items that are polygon based" or "show me all georss feeds." I know KML can be a monster. It's really a beautiful format as it can support raw geometry (2d and 3d), cartographic information, and remote data sources. The full GeoRSS GML spec also gets complicated. However, I believe supporting simple features only in KML/GeoRSS can go a long way. Are there any obvious problems to supporting geo in this way? I do not know the Exhibit code so this method may not even be possible. - John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
