 |
GoogleEarthGS.zip
| May 8 |
|
Passages_A_Niveau_TomTomax.kml
| May 6 |
Kml Bugs
| May 5 |
|
Kml Feature Requests
| Apr 30 |
|
testPoly1.kml
| Apr 30 |
|
石家庄市第一制药厂职工宿舍.kml
| Apr 30 |
|
苹果城.kml
| Apr 30 |
|
君晓家园.kml
| Apr 30 |
|
观澜豪庭.kml
| Apr 30 |
|
E-Park.kml
| Apr 28 |
|
Is there a feature that you really want KML to support? If its listed here, write your username next to it in support. If it's not listed, append it to the end. We make no guarantee that any features will get into KML or the COM API. This is a good place to give feedback to Google about what you would like to see. Google does not disclose any new features before release, so even if a feature you requested will get implemented, no one at Google will tell you before it is released. Request Format: *************************************** Feature: Brief description of feature Comments: Any comments on feature Requested by: your username in this group Supported By: Anyone else who supports you can add their usernames *************************************** Feature: HTML Form support in descriptions Comments: GE needs to be able to fully support HTML forms in description "popups" at least such that GE would post said form data to the user's external browser of choice the way HREF links send the user to an outside browser.. Requested by: EnvironmentalChemistry Supported By: *************************************** Feature: Copy coordinates of cursor by right mouse click Comments: It would be really nice to be able to copy the full decimal/DMS coordinates of the cursor location by simply right mouse clicking and selecting an option like "copy coordinates". Requested by: EnvironmentalChemistry Supported By: Frank4 **************************************** Feature: Set Touring Paramaters in KML It would be extremely useful and more user-friendly if in addition to users being able to set touring parameters (camera angle, range, speed) they could be set directly from KML so that when the PLAY button was clicked these parameters were used. Requested by: clyde@clydeford.com Addendum: We've now test-marketed a demo GE app among potential users and the common complaint is that it's too cumbersome. While we've found creative ways to use Network Links to remind users how to set-up their GE environment, all of this additional work has turned them off to GE. Being able to set touring parameters dynamically through our KML files would be a great help. **************************************** **************************************** Feature: <TimeLocal> Tag Comments: How about adding a new Tag that derives from TimePrimative which automatically converts UTC time to the users local time zone. Requested by: dlarmitage@gmail.com Supported By: Gregory ****************************************
**************************************** Feature: an "Export Google Maps compatible KML" option Comments: I have a simple data set (imported into GE Plus with a CSV file). When I export to KML, it is not Maps compatible--"could not be displayed" error. Requested by: Dr. E. B. Supported By: (unofficial) **************************************** **************************************** Feature: Allow for simple FORMs in NetworkLink descriptions that will get/post back to the NetworkLink itself. Comments: How about a feature where simple forms (in a NetworkLink's description HTML) could be submitted back to the containing NetworkLink? This would allow for a small amount of interactivy within GE without having to spawn the dreaded extra browser and move the user in and out of the GE experience. Requested by: xailor Supported By: **************************************** **************************************** Feature: GE should HTTP Accept-Encoding of GZIP for compressed data transfer. Comments: To speed large data sets, GE does not accept HTTP GZIP streamed data from NetworkLinks. Almost all browsers (interactive and non) accept GZIP data streams, GE should definetely join them. Requested by: xailor Supported By: (unofficial) Addendum: except GE supports KMZ which already is a compressed datastream :) - barryhunter Addendum: But pkzip-style compression format is not formally streamable nor concatenatable and why browsers don't support this format. **************************************** **************************************** Feature: Allow for browser icon override in Folder and NetworkLink tags. Comments: Allow the the reference of an icon href for Folder and NetworkLink entities to have the icon dispaly in the browser. Requested by: xailor Supported By: (unofficial) **************************************** **************************************** 1. Feature: Object based KML Comments: Clicking on lines and polygons should open a description window lika a click on a placemark does. Requested by: Bigga Supported By: (unofficial), Bernd Addendum: You can already do it using ctrl+clik on polygon or linestring **************************************** **************************************** 2. Feature: Object based KML Comments: Allow KML display on Google Map and still allow public (no Google account) user to search for an address Requested by: unknown Supported By: (unofficial) **************************************** **************************************** 3. Feature: Ability to generate text in the screen overlay. Comments: Right now we are generating pictures containing text and showing them as overlays. It would be greatly beneficial if we could send ASCII text and Google Earth could display them as a screen overlay to save bandwidth. If we could even use HTML so we could adjust the text look and feel it would be even better! Requested by: powwow Supported By: tobedetermined,xailor, clyde@clydeford.com **************************************** **************************************** 4. Feature: Balloon doesn't get destroyed on refresh of network link. Comments: This is a big user issue. If a user opens a placemark balloon, the balloon could become destroyed when the network link refreshes. Everyone who uses the system complains about it. Maybe we can have a flag of some sort to keep the balloon open even if the network link is refreshed? Requested by: powwow, Frank4 Supported By: ryanagler,xailor **************************************** **************************************** 5. Feature: Event handling capability, GUI capability, modifying right-click menu Comments:This is a big request, but maybe we could capture mouse events on the map or screen overlay and to perform certain actions. Some actions could: show and and hide layers, show and hide placemarks, add placemarks to the map, etc. Maybe we could also have the ability to generate GUI such as check boxes and text fields on the map so we can get user interaction data and execute commands with event handling. Perhaps we couuld get user interaction data with a right click menu? We also need the ability to submit web forms. Requested by: powwow Supported By:gifrate, ryanagler, tobedetermined **************************************** **************************************** 6. Feature: Ability to add and remove modules in the left sidebar. Comments: Not all applications need the "directions" module. Not all applications need the "layers" module. Can we have a way to remove this from the G.E. application? This will make applications more customizable. It would be extremely cool if we could add our own sidebar/module! :-) Requested by: powwow Supported By: (unofficial) **************************************** **************************************** 7. Feature: Remove flicker when the Google Earth reloads a network link. Comments:When a network link refreshes and the placemarks load again, it flickers. Users have complained that the flickering is annoying so we had to increase the time it updated so it flickered less. Can we remove the flicker upon upate? Requested by: powwow Supported By: ryanagler **************************************** **************************************** 8. Feature: Web browser in G.E. unpredictable...can we make it so it only loads in G.E.? Comments:When I go to Tools->Web sometimes the web browser opens on the bottom half of the G.E. map. On some computers it opens an entirely new web browser as a separate program. Can we make it so it only opens in the bottom half of the map? Requested by: powwow Supported By: (unofficial) **************************************** **************************************** 9. Feature: Embed Google Earth in web browser. Comments: I noticed there was a third party tool that embedded Google Earth in an I.E./Firefox web browser. They basically used a Google Earth dll and make a Mozillaplugin + ActiveX control out of it. It was pretty neat to see it in Internet Explorer/Firefox. Can you officially support this feature? Requested by: powwow Supported By: gifrate, ryanagler,luca63, tobedetermined, clyde@clydeford.com, Frank4 **************************************** **************************************** 10. Feature: Allow ability to go to a specific point in time in time slider. Comments: It is very hard to use the time slider to go to a specific point in time. Can we support in the KML to go to a specific point in time? Also, can we add a text field or controls to the time control GUI to go to an exact date (instead of sliding the control?) Requested by: powwow Supported By: MarcGG, tobedetermined **************************************** **************************************** 11. Feature: HTML table support in placemarks Comments: HTML table tags don't work in the placemarks. Can G.E. support this? Requested by: powwow Supported By: (unofficial) Comment: Yes they do! - BarryHunter **************************************** **************************************** 12. Feature: Name next to placemark optional (with boolean flag) Comments: The name next to the placemark (that identifies the placemark) fades in an out and moves around the icon when you zoom in and out. When there are hundreds of icons this can get annoying. Can you make this name optional? We are generating text around the icon we make and the automatic text G.E. produces interferes with it. Requested by: powwow Supported By: (unofficial) Comment: If I understand this correctly, its already possible with the <LabelStyle> tag, you can even make it hover only using the StyleMap - BarryHunter LableStyle does not have an "on" or "off" for the label. Unless we can scale the label to "0"? - powwow Yes use scale 0 or visisblity (part of the colour tag) to totally transparent. - BarryBunter **************************************** **************************************** 13. Feature: Permit other file formats to be packed into kmz files Comments: It would be useful to be able to include local text or even html documents directly in the kmz package so they need not be online. Requested by: LuciaM Supported By: (unofficial) **************************************** **************************************** 14. Feature: Allow local images used for BalloonStyles headers to be packed into the kmz file. Comments: Right now it appears that only local images used in <description> are added to the kmz file. Requested by: LuciaM Supported By: (unofficial) **************************************** **************************************** 15. Feature: Allow data sets to have dangling <end> <TimeSpan>. Comments: This is different from just omitting the <end> tag. During animation, the rendering of a data set is controlled by the <begin> tag. If an <end> tag exists, then the data set will stop being rendered once the time slider window no longer includes the date specified by the <end> tag. However, what I am suggesting is that a feature be added to allow the end time of a data set to be determined by the <begin> time of the next data set in a sequence. Possibly this could be accomplished by using the ID attribute so that more recent data sets having the same ID replace older data sets. This would be useful when the <begin> and <end> times are not periodic. The <begin> time is known when the data is processed, but the <end> time will not be known until the next data set is processed. Requested by: drafnel Supported By: (unofficial) **************************************** **************************************** 16. Feature: Rich balloons editor (see Mymaps in GMaps) Comments: See http://maps.google.com http://maps.google.com/help/maps/userguide/index.html#public Requested by: Valery35 Supported By: (unofficial) **************************************** **************************************** 17. Feature: Tags near of <IFrame>, <embed> in balloons Comments: See http://maps.google.com/help/maps/userguide/index.html#videos Requested by: Valery35 Supported By: mickmel, Frank4 **************************************** **************************************** 18. Feature: Time Fade in time animation Comments: See Fade to region Extent in http://earth.google.com/kml/kml_21tutorial.html Requested by: Valery35 Supported By: (unofficial) **************************************** **************************************** 19. Feature: Uses Schema values in balloon (balloon style) Comments: http://earth.google.com/kml/kml_tags_21.html#schema Requested by: Valery35 Supported By: JasonBirch Feedback: [JasonBirch] Valery35, this appears to be supported in the current version of Google Earth. Have a look at my recent post for details and example: http://www.jasonbirch.com/nodes/2007/06/29/101/i-heart-kml-schema/ **************************************** **************************************** 20. Feature: Support of a rich engine for full web support within kml Comments:in addition to Feature #5:Event handling capability, GUI capability, modifying right-click menu, it would be nice to create interactive interfaces as overlays as controls for users. Technologies such as javascript, AJAX, XUL, Google web toolkit should be included. Requested by: gifrate@gmail.com Supported By: mickmel, ryanagler, Jason Birch (mostly interested in using JavaScript to modify the KML DOM dynamically - remote JSON support would be nice too),clyde@clydeford.com, Frank4 **************************************** 21. Feature: Support data protection in KMZ files Comments: Would like to be able to distribute KMZ files with a "secure" feature so that recipients/viewers can see the information included in the placemark, but can not edit or manipulate the underlying data. Requested by: StudleyGIS Supported By: rnisthal **************************************** 22.) Feature: Allow Ground overlay rendering in Google Earth Mobile. Any knowledge of this being planned? Will change by development strategy. Requested by: Mainfan Supported By:
**************************************** 23.) Feature: Allow ScreenOverlays to be more than an image Comments: It would be really convenient if ScreenOverlays could contain simple html. (E.g.: it would be nice if the image could be a hyperlink as well.) Requested by: Funda (lafeber@gmail.com) Supported By: tobedetermined! (similar to #3), clyde@clydeford.com **************************************** 24.) Feature: Allow CSS style formating in balloons Comments: For example: <span style="font-size: x-small">this would look smaller</span>. Would also be nice if balloons could use CSS classes. For example: <span class="myclass">this would be formatted text</span>. We would need a tag similar to <StyleMap> that would let us define global CSS rules for all of the balloons in the KML file. Requested by: OwyheeRover(bclark@earthpoint.us) **************************************** 25.) Feature: Google Earth COM API - IFeature improvment Comments: Would be nice to get/set the ID, the Description and the Location of IFeature instances. With API it's possible to search a feature by its HREF/ID but not get the HREF of an highlighted feature, strange isn't it?. It would also be usefull that API allow to edit the location of a marker or of a path without generate and load a new KML. Requested by: mathprod (mathieu.ocana@gmail.com) Supported By: ryanagler **************************************** 26.) Feature: Google Earth COM API - Improvments Comments: In addition of Feature Request #25 a) IApplicationGE should have a GetFeatureById(id) method which allow to use the <Feature id=### />. Due to many KML files can be loaded, it can exist more than one elements for an Id, so GetFeatureById() return the fist element with the wanted ID, assuming all features have a GUID in a collection of KML files. IApplicationGE::GetFeatureByHRef(href) need to know the loaded KML files (href=filename#id), so IApplicationGE should provide a collection which contains the filepath of loaded KML files. b) IFeatureGE should have ID, Location, Description (+ metadata string if possible) and Style get/set properties. Style could be the ID or the href of a defined style. The HideShowDescriptionBalloons() methods could be added to IFeatureGE c) IApplicationGE could also provide a collection of available style, so provide a IStyleGE class with ID get property and iconstyle, linecolor, linewidth, labelcolor, labelsize get/set properties. ------- Maybe not feasible, strongly dependant of the current implementation d) For track/path representation, IFeatureGE should provide a collection of point location which contains each point of the path as an IPointOnTerrainGE instance. If possible a new class (IPathGE or something like that) derivated from IFeatureCollectionGE and IFeatureGE and dedicated for path/track handling could be added, with ID, description (+metadata) and Style get/set properties. e) Furthermore It may be usefull if IApplicationGE::LoadKmlData() returns a IFeatureCollectionGE which contain the features of the KML file. The collection in part a) could contain the filepath and the a reference to the feature collection associated with loaded KML files. f) Add event handling capabilities (join feature request #5). For IFeatureGE, event Click, MouseOver, MouseLeave (feasible with Highlight method),... I don't know exactly how to implement this, but it can works with delegate or function pointer... Requested by: mathprod (mathieu.ocana@gmail.com) Supported By **************************************** 27.) Feature: KML <coordinate(s)> Comments: In case of path/track, the locations of all points are concatenated between <coordinates>...</coordinates>. It could be easier to read and to parse if a new mark <coordinate/> exists. Lists of points could be stored as: <coordinates> <coordinate> #######,#########,# </coordinate> (or <coordinate lat="#####" long="#####" alt="#####" />, cool but hard to keep backward compatibility with this) [...] </coordinates> Requested by: mathprod (mathieu.ocana@gmail.com) Supported By: **************************************** 28.) Feature: Prevent Redundant NetworkLinks Comments: When a kml file containing a NetworkLink is loaded, if there is an existing NetworkLink with the exact same "href" and ID, the existing NetworkLink should be updated, rather than an entirely new unnecessary-bandwidth-hogging redundant NetworkLink created. Requested by: ryanagler (ryanagler@gmail.com) Supported By: hessu@hes.iki.fi, Insaniac99,xailor **************************************** 29.) Feature: Allow KML to Delete NetworkLinks Comments: A NetworkLinkControl should be allowed to delete NetworkLinks, including its calling NetworkLink. This would not be a security issue if the NetworkLinks a NetworkLinkControl can delete are limited to those that have the same href Requested by: ryanagler (ryanagler@gmail.com) Supported By:powwow, Insaniac99, rnisthal,xailor,clyde@clydeford.com **************************************** 30.) Feature: The NetworkLink loading a purely Updating NetworkLinkControl should NOT appear in Temporary Places Comments: This just adds clutter and confusion. An NetworkLinkControl update is not a place on the map, and its caller should be automatically deleted from temporary places as soon as the Update is done if there is no refreshInterval specified. Requested by: ryanagler (ryanagler@gmail.com) Supported By: rnisthal *************************************** 31.) Feature: httpPost (exactly like httpQuery) Comments: It would be nice to be albe to use POST (I propose a new "httpPost" element) requests for Link instead of GET (current done by "httpQuery" element). GET limits the size of the data you can send to the server. Requested by: ryanagler (ryanagler@gmail.com) Supported By: dc3denny *************************************** **************************************** 32. Feature: Support rotation of rasters in GMaps Comments: Wanted one features in GE and GMaps Requested by: Valery35 Supported By: (unofficial) **************************************** 33. Feature: Allow sending <viewFormat> data using <refreshMode>onInterval</refreshMode> Comments: Sofar, it is possible to send <viewFormat> data using the <viewRefreshMode>onStop</viewRefreshMode> but this has a low temporal resolution and does not work when the user continuously moves. Using the onInterval option will help here. Having a subsecond onInterval period will also help. Requested by: tobedetermined Supported By: (unofficial) ****************************************
**************************************** 34. Can we have Colour Coded Pushpins Will it be possible to have colour coded pushpins coded into the KML files, this would be really useful for displaying different groups of addresses. Requested by: VeeWhy Comment: KML already supports this using the IconStyle tag (ManoM) **************************************** 35. Feature: Allow <Change> to add coordinates instead of replacing them Comments: In the KML reference the following is stated: When <Change> is applied to a set of coordinates, the new coordinates replace the current coordinates." Would be nice if the <Change> tag also allows to add coordinates instead of replacing the existing ones. Requested by: tobedetermined Supported By: (unofficial) **************************************** 36. Feature: LineStyle arrows Comments: It would be nice if there was a LineStyle element that could be turned on which would inert arrows along a LineString so that you could indicate the LineString's direction of travel. Requested by: ryanagler (ryanagler@gmail.com) Supported By: Simon Charest (SimonCharest@gmail.com) rnisthal Comments: I am regularly mapping very precise paths (including adresses, longitudes, latitudes, directions, lengths, etc). The only way I can tell them apart from one another is by creating folders/groups (per path, per week, per day, etc), allocating them a different color each and then connecting them with lines. I just wish I could use arrows to make the paths more visual (instead of adding a unique incrementing number). ****************************************
37. Feature: Add KML and KMZ as default MIME types for all servers and operating systems Requested by: OwyheeRover(bclark@earthpoint.us) Comment: Still, it would be worth asking. (OwyheeRover)
**************************************** 38. Feature: Allow coordinates to be added to a LineString without having to resend the old coordinates Comments: If you use a LineString together with a networklink it's impossible to add one or mulitple points to the path. To update the path you need to update all the points.This causes lots of overhead when the path contains lots of coordinates Requested by: lucvh Supported by:
****************************************
39. Feature: Add dashed lines to <LineStyle> Requested by: OwyheeRover(bclark@earthpoint.us)
****************************************
40. Feature: Allow each shape in a <MultiGeometry> to have its own style Requested by: OwyheeRover(bclark@earthpoint.us) Supported By: Jeff, Matelot
**************************************** 41. Feature: Function to make map center and zoom on KML overlay Requested by: Truck3r Supported By: (unofficial) ****************************************
42. Feature: Ability to specify a different icon for bundled placemarks Requested by: Joshua Stewart Supported By: (unofficial) ****************************************
43. Feature: Filled polygons that follow irregular ground Comments: I'm trying to show a phenomenon that follows the earth's surface. The method I'm using is to draw a tessellated polygon and fill it. The outer boundary of the polygon follows the earth's surface very well, but the fill color doesn't - high points poke through the fill. Example is at http://www.thewebsitedoctor.net/avalanche/UtahAvalancheMap.kmz It would be nice to have some way to clamp the fill to the ground. Requested by: Walt Haas Supported By: Jeff Daily
API in Google Earth or way to define a replacement type in a schema Thanks for the consideration.
**************************************** 46. Feature: Enhance Camera tag to remove dependancy on Placemark Comments:
I find the fact that Camera is a singleton child of PlaceMark to be somewhat constraining:
To allow for these cases, I propose that the Camera tag be disassociated from the PlaceMark tag, and made into a primary object under the Document tag, similar to Style, and that Google Earth be enhanced to recognise the Camera tag in its Tour mode. Requested by: Jason Birch Supported By: Valery35, Rich Treves ****************************************
47. Feature: Enhance Camera and Placemark to allow referencing, similar to the Style tag Comments:
If combined with Feature 46, this would allow Camera tags to be referenced by Placemarks, and would allow multiple placemarks to reference a single Camera. An additional tag (CameraCollection?) could be used to associate multiple cameras with a single Placemark.
Requested by: Jason Birch Supported By: Valery35, Rich Treves ****************************************
48. Feature: Network link to placemark in KML by ID. Comments: In KML 2.2 i see link to style as http://.../file.kml#id and link from balloon to need placemark. I hope we can use this feature from Network link.
Requested by: Valery35 Supported By: (unofficial) **************************************** 49. Feature: KML in Notebook Comments: It is more to Google notebook (Docs) team. If we can uses permanent link to notebook bookmarks (or Google documents bookmarks) and paste (upload) texts of KML files then we can make and debug very interactive Google GEO projects.
Requested by: Valery35 Supported By: (unofficial) **************************************** 50. Feature: FADE IN and FADE OUT for COLLADA models Comments: Collada models (at least the ones with textures) are not sensible to the fade in and fade out configuration of the "Level Of Detail" parmeters for an object so they appear and disappear suddenlly and not smoothly.Requested by: pyarza Supported By: (unofficial) **************************************** 51. Feature: FADE IN and FADE OUT ability for new PHOTO Overlay objects defined in the KML 2.2 DRAFT DOCUMENTATION Comments: It would be nice that the new photo overlays are made sensible to the fade in and fade out configuration of the "Level Of Detail" parmeters for an object so they appear and disappear smoothly if you configure them that way (the current documentation draft doen't says if this will be the way it is supposed to work).Requested by: pyarza Supported By: (unofficial) **************************************** 52. Feature: REGIONS and their LOD to be defined so that they are not rectangles oriented north Comments: Actually the REGION LonLatAltBox paremters only allows to make areas that with their sides parallel to north-south and east-west directions, and in some cases it can be usefull that this areas can be defined with a parameter like orientation so we can have a LonLatAltBox that is oriented as needed (even more it should be maybe defined as nort an oriented rectangle but as a generic polygon).Requested by: pyarza Supported By: (unofficial) **************************************** 53. Feature: Ability to resume trip (flight) over a linear feature from other point that is not the begining of the line Comments: AS an example, If a line feature represents a road and the user stops in the middle of the trip over that line and selects something else (another feature he is looking at) the "focus" over the line trip is lost and the trip restarts from the begining of the linear feature.(he should be able to resume the trip in the same point where he has stopped). (Actually I don't know if this is a KML request or a feature request for the GEapplication)Requested by: pyarza Supported By: kmlEditor@NorthGates.Ca ****************************************54. Feature: Google Earth COM API - Improvments Comments: It would be useful to have an event that occur when the feature properties dialog opens and closes. Also if the event could return the feature xml text (just like right-click and Copy feature xml) when it closes and perhaps return empty xml if the user canceled or no changes occured. The event could be limited to a specific loaded file (by href#id) or kmldata and limited to the temporary places too. Instead of an event if GE isn't going to provide events, if we could have the above info to query when we need it.Requested by: kmlEditor@NorthGates.Ca Supported By: (unofficial) **************************************** 55. Feedback: Google Earth COM API - Developer Group Comments: It would be useful to have a quick running status of what GE developer group is doing, ie.: Reviewing KML Feature Request#, Implemented Interface by GE version, etc.. Just a one pager running log link from COM API web page. Requested by: kmlEditor@NorthGates.Ca Supported By: (unofficial) **************************************** 56. Feature: Faster Google Enterprise/Pro Client Update Rate Comments: I have an application where I use the GE Client to display results from my simulation. I load 3D models of aircraft and have them fly around in Google Earth. The motion is very jerky, however, because the GE Client only refreshes network links at a maximum of one Hz. It would look much better if the GE Client supported a faster refresh of up to 60Hz. I understand that this would be a concern for the free client, as it could be used to overwhelm a server. Would it be possible to allow faster updates in the Enterprise Client when used with an internal server? Requested by: Bob Case Supported By: (unofficial)
Comment: You can use the Earth API's SetCameraParams() function to update the current camera's view from an external application at any rate you like. Your external app will need the info from each simulation point and periodically update the view with calls to SetCameraParams(). -doug
**************************************** 57. Feature: Google time stamp to include BC time At the moment time stamps can only go back to 0AD, lots of earth science applications require animations before this and to perform them at the moment we have to work around by using AD time only. Not only is this fiddly for the developer, its confusing for the user as the time line is putting out the wrong (AD) numbers. Requested by: Rich Treves Comment: (ManoM) Actually, you can, simply put a minus sign in front of the date and it will show up as BCE. **************************************** 58. Documentation: Please clarify the use of the SimpleArrayField and Obj types within Schema Comments: Currently, only the SimpleField is documented as to how it is structured. I would really like to see more documentation on how to use these more advanced types, and also how to integrate them into the BalloonStyle element. And for crying out loud, please don't deprecate the Schema element! Requested by: Jason Birch **************************************** *************************************** 59. Feature: <Geometry> elements contained by <MultiGeometry> should inherit its properties Comments: Currently (KML2.1), it appears that <extrude>, <tesselate>, and <altitudeMode> are ignored if defined for <MultiGeometry>. Instead, for each <Geometry> element within, those properties must be defined even if they never change from <Geometry> to <Geometry>. Here's my use case: I'm trying to draw realistic-looking 3D clouds. If a cloud has many, many <Polygon>s defined, I have to set <altitudeMode> for each <Polygon> to something other than clampToGround. Feature request 40 is loosely related. Combined, these two requests show a need for enhanced <Geometry> flexibility. Requested by: Jeff Daily,Matelot Supported By: Matelot Addendum: Something like VRML would be very welcome **************************************** *************************************** 60. Feature: Redefinition of default values Comments: Somewhat of a generalization of request 59 above, it would be nice to allow a KML element's default property values to be redefined for an entire KML document. I can see something like a declaration towards the beginning of the KML file, or a declaration for the first instance of an element, resetting the default value. For example, the <Geometry>'s <altitudeMode> property. Wouldn't it be nice to say somewhere in the KML, "From here on out, the default value for <altitudeMode> is not clampToGround?" Requested by: Jeff Daily Supported By: **************************************** **************************************** 61. Feature: Sorting objects in places-folder Background: The polygons I exported to KML are sorted according to their ID in the GIS-software (Manifold Systems) I've been using. I couldn't find an easy way (at least not yet) to do the sorting before exporting the polygons to KML. I discussed the sorting possibilities in the developer support forums (thanks again for your help!) and was directed to post this message to the feature request page. Requested by: falsuhail@hotmail.com **************************************** **************************************** 62. Feature: Ceiling and Floor (altitude band) control over polygons Background: When building a 3D polygon that does not have a floor of the ground (extrude=1), individual panels must be built. Please include a capability to specify a polygon and a floor and ceiling altitude to simplify the creation of 3D volumes that are not on the ground. Requested by: greg_roughriders@yahoo.com **************************************** **************************************** 63. Feature: Altitude indicator or slice Background: In addition to providing the altitude of the "eye", can you add a method to evaluate the altitude of objects within the view. For extruded polygons and lines, having insight into the altitude values can be useful. Requested by: greg_roughriders@yahoo.com **************************************** **************************************** 64. Feature: Add support for ground overlays that do not use a rectangular latutide/longitude grid Background: I work on OMI (Ozone Monitoring Instrument) which is the Dutch/Finnish contribution to NASA's EOS-Aura satellite. This satellite circles the earth is a so-called sun synchronous orbit. It measures on a grid that is rotated with respect to the local meridian. Right now we display the daily measurements by drawing the ~1 million measurements by plotting them on a large rectangular grid (see the www.temis.nl website for examples). We would like to plot the individual orbits using the grid native to OMI, reducing the size of the downloads, and increasing the fidelity of the display (hey, win-win). This request is relevant for other space-borne satellite instruments as well (sun-synchronous, like MODIS, GOME-2, Sciamachy, and others). Geostationary weather satellites will require a different mapping method. Requested by: Maarten Sneep
I work with a variety of climate satellites, including CALIPSO. CALIPSO is sun-synchronous and part of the A-train. Instead of scanning wide swaths of the earth's surface, it makes detailed vertical profiles of aerosols using a laser. The images created using this satellite are best viewed tied to the ground like an overlay but sorta stood on end. Specifying the corners of a picture would require lat, long, and alt where each pair of corners would share lat and lon, but have different altitudes(one at the ground and one at TOA). Mapping could be done using great circles. We could handle earth rotation under the satellite by making a series of images that would blend seamlessly. Combining this with regular rectangular ground overlays would allow us to more easily compare features observed by different satellites and show them to the public. Requested by: Don Garber
To add to this: The display of the 'curtain' through the atmosphere also applies to CloudSat (which uses a Radar to measure cloud profiles). Of course things can be harder still: OMI will eventually produce ozone profiles as well, producing a full 3D field of Ozone. I'm not sure whether and how to display this data in Google Earth. By the way, I think people at Google are aware of these type of issues, or at least they can be if they attended this Google Tech talk. Added note by Maarten Sneep **************************************** **************************************** 65. Feature: Force description to be shown as text, html or auto Background: I wish to add much <html>, <a href=>, <img src=> and I want it would shown as text and they would not be parsed as HTML. Even if I escape them as <html> I wish that that it would be added attribute type to description and similar tags, also to style maybe. <description type="text"><CDATA[[<html>]]></description> Requested by: Edgaras **************************************** **************************************** 66. Feature: Hide display of names for placemarks containing points Background: Some of our KML models contain 100s to 1000s of points. Each point represents a physical feature - for example trees. Currently, when we assign each point a name - GE draws all the points on the screen with their names. This is very distracting to the user. We currently dont assign point features a name - which makes it hard for the user to find a certain point from table of contents(TOC). It would be great if you could add tag that would tell GE whether to display the name in the 3D viewer or not. This problem does not occur with polygons and polylines - as their names do not get shown in the viewer. Requested by: Raj.Rao Comments: (ManoM) You can do this already. Use <LabelStyle><scale>0</scale></LabelStyle> **************************************** 67. Feature: Autosave Folder Background: I would like to be able to set a .kml (or .kmz) file that a folder automatically saves back to each time I update it. In conjunction with network links, It would allow our municipal government operations (traffic and emergency personnel) to communicate geographically in real-time. For instance, when the traffic department closes a street, simply adding a line to the closed street will refresh the information to anyone that has the kml network linked, such as dispatchers, fire and police, and the public. Right now they have to manually save it, which, if not saved properly, can ruin the file. Requested by: Carey Stranahan ****************************************
***************************************
*************************************** Comments: it seems when networklinks are downloaded/parsed, it might be the built-in vector data in GE (roads, boundaries etc) never have this the smoothness of the GE rendering is one of those intangible items Requested by: Brian Flood *************************************** ***************************************
Comments: We've had panoramic tours available on our website, linked from MapGuide, for quite a while now. Although users can pop out of one pano and then enter another, one of the best features of for our users is that once inside the pano, they can navigate from one pano to another by just clicking on hotspots within the image. As well, they can open external HTML pages from inside the pano for additional information on historic buildings, etc.
It appears that the new PhotoOverlay tag allows for displaying spherical and cylindrical panoramic views. However, there doesn't appear to be a linking (or link positioning) component, removing the ability to create proper virtual tours.
Please add the ability to place hotspots within panos. These should be able to link to internal locations with an anchor reference #pano-id-3232, to external KML files with http://www.example.com/pano123.kml#pano-id-123, or to external web pages with http://www.example.com/building_description.html
Requested by: Jason Birch 71. Feature: Ability to use <embed> and <object> tags in kml infowindows. This way we could display swfs, flvs and other types of files. Comments: You can now use embed for flash applications, in the Windows 4.2 client. Requested by: gyorgy.chityil@gmail.com Supported By: dc3denny, kmlEditor@NorthGates.Ca
*************************************** 72. Feature: <Camera> KML tag tilt view of 180 deg should be capable with COM API SetCameraParams() Comments: Currently the COM API functions SetCamera() and SetCameraParams only let you tilt your view 90 to 0 degrees. Since the new KML <camera> element allows the ability to view straight down to up (0 to 180 deg), the COM API camera functions should do so as well. Requested by: dougec Supported By: **************************************** *************************************** 73. Feature: Support/maintain Http Session/Cookies between subsequent requests to a network link. Even better: share the http session with the web browser if the base url goes to the same webapp as the network link (via url re-writing or similar) Comments: Currently I have to hack my own session maintenance with url re-writing in order to get a network link to pass information to other web pages that will be launched through the web browser. At a minimum though, I think its reasonable to expect GoogleEarth to at least maintain the session (via cookies or url-rewriting) between subsequent requests to a single network link. Requested by: BenG Supported By: xailor **************************************** *************************************** 74. Plugin API interface Comments: GoogleEarth doesn't have a publicly available plugin interface. Getting information out of google earth and submitting it to web services is usually difficult resulting in a poor user interface. An API allowing developers to write extensions that define new menu options etc. would greatly increase the ease of integration. Requested by: BenG Supported By: kmlEditor@NorthGates.Ca **************************************** *************************************** 75. GoogleEarth Security & Authentication Model Comments: We need a complete understanding of the authentication mechanisms supported by the GE client. The goal is to have authenticated network links and services made available using a single sign on. To support this GE would need to cache the credentials provided by services/data feeds in a web environment and provide the authentication information along with any future requests. Requested by: BenG Supported By: xailor **************************************** *************************************** 76. Network Link & Time Slider Integration (plus allow user to select a time span outside current range) Comments: We would like to use the Google Earth time slider as a query filter for network links. The key enhancement required to do this would be to pass the time span from the slider as a URL parameter (much like the view bounding box). The Google Earth client should also be modified allowing a user to select a time span outside of the current range (i.e. move the slider off the current scale) Requested by: BenG Supported By: **************************************** *************************************** 77. Support for Negative Elevations Comments: Support for negative elevation on the Google Earth globe Requested by: BenG Supported By: NR (and several others attending GDD 07), Jonathan van Tuijl (Not related much to KML, but I'd really appreciate it if ground below sea level wasn't raised) **************************************** *************************************** 78. Annotation within PhotoOverlays Comments: PhotoOverlays can potentially contain a huge amount of detail. I would like to see some method of applying annotations to points or areas of the PhotoOverlay, along the lines of the 'Add Note' facility at flickr. On a broader theme, if the 'surface' of a PhotoOverlay could be treated in the same way as the surface of the GE globe, you could apply any GE annotation methods such as pushpins (including perhaps other PhotoOverlays). Actually, this could apply equally well to ScreenOverlay and GroundOverlay elements, as well as surfaces of 3D models - in fact anything to which a coordinate system can be applied. This would opens up GE to 'Worlds within Worlds' possibilities. Requested by: PhilRichards Supported By: Anyone else who supports you can add their usernames **************************************** *************************************** 79. Feature: More control over an icon's heading Comments: Currently you can define one heading for an icon. The only sensible way for GE to handle that is by drawing it on the ground, then rotating about the "horizon axis" so it faces the user. That's great for emulating GE's compass on Earth (or perhaps in the sky). However, if you want the icon to point at something, it becomes clear that "directional distortion" balanced over all directions doesn't help when you only care about one direction. I propose a way to specify that one direction. Requested by: Jonathan van Tuijl Supported By: **************************************** **************************************** 80. Feature: Ability for KML file to control time slider's range Comments: A newly loaded KML file with TimeSpan information will come up with the time slider pegged on the left (to the beginning time). That can be a bit irritating, as a better default would be to have it include the whole time span. And, if a user is not familiar with the control, he will not see the track line that is in the KML file and will not intuitively know to expand the time slide control to the right. Requested by: Felix **************************************** 81. Feature: Mix MSL and AGL Altitudes in Co-ordinate List The altitude mode is set way back before the co-ordinates. I need to draw a line from an absolute (above Sea Level [MSL}) to a relative (above Ground [AGL]) altitude point. Requested by: Stareagyl Supported by: **************************************** 82. Feature: Draw 3-D Swash/Tube/Pipe/... Would like to draw a translucent pipe or chute in the air - i.e. would like to specify a LineString with a height or a radius. I'm not seeing my line in the air when I don't <extrude> Requested by: Stareagyl Supported by: **************************************** 83. Feature: RegularPolygon, Circle, Star Elements Comments: While Polygon is fine, there isn't any support (that I saw anyways) for regular polygons, circles and whatnot. It's very non trivial to compute "make a circle centered at (long,lat), radius 10,000 meters" I whipped up a little python script to generate this at http://code.google.com/p/kmlcircle/ I used a spherical model, which seems to work ok for radius < 1,000,000m or so. It's a bit more work to do the full elipsoidal model, but whatev. Anyways, me thinks that <RegularPolygon>, etc would be great additions to KML.
poyom: This would especially be nice when doing dynamic updates so the vertices don't have to be sent every poll. And don't forget about ellipses and arcs. Requested by: nickg [at] modp [dot] com Supported by: Poyom **************************************** 84. Feature: Support zipfile passwords on KMZ Comments: OK, so this isn't really a KML suggestion. But I would really like to be able to apply a zip password to the KMZ file and have Google Earth prompt for the password. What the user does once they open it doesn't really mater (similar to the approach to http auth) just that they were authorized to open in the first place. I know this goes counter to the Google mantra--you can't access the data without breaking the password--but it sure would be handy for distributing proof-of-concept files without having to worry about them being viewed by casual users.
Requested by: Jason Birch Supported by: **************************************** 85. Feature: Making holes or excavation on GE Many engineers or surveiors need to see their project into GE. If you use absolute mode por height you discover you cant see the parts excavated. It is neccesary a 'cutting' object or property to 'adapt' the GE surface. In fact many projects exported from Autocad, MX roads, ISTRAM, etc cant be seen correctly. I'm sure this feature will give a few oportunities, perahps in GE Plus or PRO of course .
Please notify me your opinion. And in any case I will answer the questions you have. Requested by: Antonio Pérez tonnot1166@gmail.com Supported by: ****************************************
86. Feature: Re-implement ability to display non-Flash content using OBJECT/EMBED tags in balloons. For a short time it was possible on the Windows platform to embed a Windows Media Player object within balloons allowing for MP3, MPG, AVI and other compatible formats to be rendered. The latest release eliminated this ability. By re-implementing it, along with possible support for other plug-in players (such as Quicktime) it would extend the functionality of the tags and allow for broader market penetration of developer content. Requested by: wndrin Supported By: lars **************************************** 87. Bug - FOV (Field of View) in Spherical PhotoOverlay is too small Supported by: ******************************************* 88. Feature: Combining styles
Requested by: ecornips Supported by: Manx ******************************************* 89. Enabling the possibility to choose which website to share/post The menu share/post when you right click on a feature send your kmz on a fixed website (http://bbs.keyhole.com/ubb). Choosing which website to post will enable huge capabilities for geo-collaboration. Requested by: gershwinou Comments: [ManoM] Wouldn't that require log-in information for other sites? And have those sites integrate directly with Google Earth? Currently, you can save the KML and upload it using whatever mechanism your site provides for that data. gershwinou: Well that is breaking somehow the user experience. To tell the truth, i have developed a collaboration/versioning tool that people can use (ie, watch, change and commit) from within ge (a bit like SVNised geographic tool) however the 2 only decent possibilites to do it properly is 1. sens as email (not connected way) or share/post (connected). share:post is working very fine but need to hack a bit ge... Any other suggestions welcome Supported by: *******************************************
*************************************** 90. animated gif and/or flash content for overlays,screenoverlays and/or sketchup mappings Comments: It where super if it where possible to use animated mapping datas (and why not, interactives , ex: flash); in more, because the flash format is vectorial, it's cool to using it in large scale datas. Requested by: Cdriko Supported By: ****************************************
**************************************** 91. A version of a LatLonBox and LatLonAltBox that specifies corners rather than sides and rotation for positioning Comments: While it is possible to use the latitude and longitude boundaries with a rotation to specify the position of a ground-overlay, it can be more convenient to specify the latitude and longitude coordinates of each of the four corners of an image. Requested by: Maarten Sneep **************************************** 92. "Maps" and "Hybrid" layers should be added as an alternative to just imagery backgroundsComments: Requested by: Mangocrate Supported By: ***************************************
*************************************** 93. Feature: Ability to use NetworkLink ID in <targetHref> instead of URL (in <Update>...</Update>) to allow <Change> of NetworkLink elements, including it's URL Comments: Example: <NetworkLinkControl> </Change> Supported By: ****************************************
*************************************** 94. Feature: A new <Merge> operator for <Update> to combine <Change> and <Create> functions Comments: This new <Merge> operator should work as <Change> if element already exists, else will <Create> new element with specified ID. ****************************************
*************************************** 95. Feature: Control of a fog distance(s) in <Camera> or <Lookat> objects Comments: this parameter should control the atmosphere opacity to get nice perspective views near the <minFadeExtent> or <maxFadeExtent> but applied to all objects in the field of view Requested By: CdrikO ***************************************
*************************************** 96. Feature: Larger font size when editing Description Comments: This is not exactly a KML request. In Google Earth, when a feature is right-clicked we can open the properies window. It sure would be nice if the font size for the Description was bigger! It is quite difficult to read... Requested by: owyheerover Supported By: ****************************************
*************************************** *************************************** Comments: Use of 'coordinates' greatly increases the complexity of KML parsers with limited resources (e.g. in J2ME this adds an additional 1 or 2K of bytecode to the application) and passes validation to an additional layer in the parser code rather than the XML parser. Would break backwards compatibility. Requested by: Sam Halliday
*************************************** 99. Feature: BBOX parameters when using Google Maps Mobile Comments: Allow for example <viewRefreshMode>onStop</viewRefreshMode> <viewRefreshTime>5</viewRefreshTime> inside a NetworkLink so that a server-side script receives the BBOX parameters of the mobile user to provide more localized results Requested by: Dean Maslic Supported By: ****************************************
*************************************** 100. Feature: Render images in Google Maps Mobile Comments: Render (scaled-down if needed) images inside the info window of a marker, eg. view geocoded flickr photos using GMM Requested by: Dean Maslic Supported By: ****************************************
*************************************** 101. Feature: BASE URL Tag Comments: This would function the same as the BASE tag in HTML - used to resolve un-found relative URLs for links and images in KML. (In KMZ - with assets included in the ZIP - if the asset is not included within the ZIP then the base URL would be applied ) i.e. With <BASE href="http://mysite.com/projects/"> (at the KML root-level) The following link: <description><![CDATA[The development at <a href="coast-park/">Somerton Park</a> is coming soon]]></description> Would resolve to: http://mysite.com/projects/coast-park/ Requested by: David Whiterod Supported By: ****************************************
*************************************** *************************************** 103. Feature: HTTP Authorization support Comments: Google Earth / KML to provide a way to access URLs (i.e. <NetworkLink>) which require the HTTP Authorization header to be present (maybe a login dialog?) when the URL (<NetworkLink>) is refreshed. Requested by: kmlBob ***************************************
*************************************** 104. Feature: Tesselation support for extruded polygons Comments: I would like to be able to add areas of vegetation cover as polygons with extruded height equal to the vegetation height (e.g. for tree cover). It would mean that Google Earth could then be used to assess the visual impact of proposed projects. JOS: tessellation should also work with non-extruded, relativeToGround/absolute polygons as well; ie: floating flat polygons that follow the curvature of the earth Requested by: nix Supported By: Jos *************************************** *************************************** 105. Feature: More FOV/focal length/zoom control Comments (Jonathan): Right now you can make a <PhotoOverlay> with a <ViewVolume>, but GE will only show it approximately and I couldn't find a way to animate it (update in realtime with a <NetworkLink>, to be specific). I'd like to see something like a <Camera> extension and ideally also UI control. This has been requested before a few times. Addition (Jonathan): I just tried the PhotoOverlay technique I described in the thread again and the image border updated (I used a transparent PNG so only the border is visible). Nonetheless not very useful because GE doesn't adjust its FOV. If the new FOV is larger it might encompass GE's actual FOV so part is out of view, and if it shrinks it becomes small on screen. GE didn't allow me to zoom in/out manually with various UI methods, including right-dragging, using the +/- slider at the top right, or pressing +/- on the keyboard (might have to do with the transparent image I used being 1x1). Thread: http://groups.google.com/group/kml-support-advanced/browse_thread/thread/6155190fdc087e10 Requested by: Jonathan van Tuijl, Tiziano Fiorenzani (thread starter, added by Jonathan) Supported By: ***************** **************************************** 106. Feature: COM API: Switch off Camera Inertia Comments: GE camera shows inertia and avoidance movements when close to terrain. It should be possible to turn this behaviour off if the SetCameraParam method of the COM API is used ! Requested by: Tobias Supported By: **************************************** **************************************** 107. Feature: LineString and Polygons to have rollover features Comments: The current feature is to CTRL+click the LineString's endpoints or anywhere on the Polygon. It would be great if the CTRL+ could be dropped and have the object be completely rollover-based. Also, when any object is rolled over, having more flexilibility (instead of just stylesmaps) would be appreciated (IE. hovering the mouse over a line could display a textbox or balloon) Requested by: Jos Supported By: SylviaA **************************************** *************************************** 108. Feature: CSS-like Style replacement Comments: Currently you can only specify one Style with absolutely no flexibility in combining styles in any way. Each and every combination of styles needs its own full-blown Style that specifies the common properties over and over. CSS is more compact than Style in the worst case, gets orders of magnitude more compact when Style becomes excessively redundant, is very flexible, and has StyleMap-like functionality built-in. It can also support line widths and such in absolute units, something that has been requested a few times, with relative ease. It's also less of a chore to write and web people will be familiar. I could probably go on for a while. This is like request #88 but more extensive. Maybe #24 can be worked on at the same time. If/when styles get overhauled anyway (KML 3?), #40 or equivalent functionality is also worth looking into. [Manx] Need cascading styles - ie. the ability to set a default style/icon in a Folder, and that style to be inherited by all the placemarks within that folder. It should be possible to be possible to change (say) just the colour of an icon, without defining a completely new style for a single placemark within that folder. Requested by: Jonathan van Tuijl Supported By: Manx *************************************** *************************************** 109. Feature: Point spread could try to maintain relations between points Comments: In a recent post someone wanted to control the positions points spread to when they're located at exactly the same spot. I tried to offset the points slightly (I created 8 points, N, NE, E, etc. and offset each slightly in the corresponding direction) to see if Google Earth maintains relative relationships between points, but it didn't even try as far as I can tell. It would be nice if the spread would be more like a distorted map that nonetheless is topologically similar. Now that I think of it, this is related more to GE than KML. If there's a better place, by all means put it there with my support. Requested by: Jonathan van Tuijl Supported By: ****************************************************************************** 110. Ability to have multiple time events for one marker. As far as I can tell, I can only have a start and an end for a <TimeSpan> tag. It would be useful if I can have multiple 'events' associated for a single placemarker - ie:
<begin>1836</begin> <!-- Building built --> <event>1944 <Icon>/new-icon.png</Icon></event> <!-- Building damaged; no longer in use (but physically present.) --> <end>1968</end> <!-- Building demolished --> Currently, this is only possible using multiple placemarks for each time-span, using the same point data (which although works, is the wrong approach when you have a database sorted by unique lat/lon indexes!) Requested by: Manx Supported By: *************************************** *************************************** 111: Support for External Entities in Google Earth Strictly speaking this is not a KML feature request - it requires no changes to the KML language at all. However, it would be very nice if the Google Earth KML parser properly resolved references to external entities. This would enable the use of well-balanced, but not-well-formed, fragments of KML. See, for example: http://groups.google.com/group/kml-support-advanced/browse_thread/thread/35dc620a561cb5e Requested by: tow Supported By: *************************************** *************************************** 112: Change Handling of HTTP Status Code 406 in Google Earth Another non-KML request. When using MultiViews in Apache, while serving PHP content via MultiViews (e.g., http://host.com/my_kml_content vs. http://host.com/my_kml_content.php), GE causes a 406 and chokes on it. This could be avoided by GE in at least three ways:
This can of course be dealt with on the server in a number of ways, or by the content provider, but it'd be nice if Google Earth could cope with it all by itself. Requested by: D. Berge Supported By: *************************************** *************************************** 113: Add Time Query Capability to WMS Layers Comments: Some WMS servers have a capability to accept time as a parameter, allowing you to filter millions of datapoints or imagery sets down to a smaller sub-set. Being able to pass the time slider as a range of time to the WMS layer, rather than trying to use it as a means of filtering after you've downloaded enough information to potentially bring GE to a crawl, seems like a helpful idea. Requested by: ecuguru Supported By: *************************************** *************************************** 114: Feature: Support subterranean surface Comments: The minimum altitude of anything in GE (terrain, placemark, etc.) is currently limited to 0 (check out Dead Sea, elev reads 0 whereas wikipedia says -420m). This is a severe limitation in terms of the ability to support features that goes below "sea-level" or whatever altitude/elevation of 0 means. Requested by: locksmith Supported By: *************************************** *************************************** 115. Feature: Support terrain overlay Comments: GE should support the concept of a terrain overlay. Analogous to an image overlay, one should be able to replace parts of the terrain with user-supplied terrain of possibly higher accuracy. Requested by: locksmith ********************************************* ********************************************* 116. Feature: Extension of the 'Time Slider' for basic data analysis Comments: GE natively understands the format for TimeSpan kml objects, and allows for basic manipulation of data based on date. I'd love to see this feature extended to other basic data types. Implementation may differ, but here's an example: When custom data is defined via a <Schema> and <SimpleData>, add an additional parameter to SimpleData (i.e. span_id) that identifies this field as being "data that should be put into a slider called 'span_id'". This feature should only work on SimpleData datatypes that have a natural ordering (ints, doubles, strings) so that GE will automagically range the entries in a predictable manner. Multiple 'span bars' should collapse in the GE interface to avoid clutter (similar to how the navigation compass minimizes when not under the cursor). This feature would allow for basic data analysis of user-provided data in a natural and convenient manner. Requested by: nicodemussunrise Supported by:
|
|
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2008 Google |