Uncategorized

Where 2 Now: Pics, GeoRSS, tips and debug tricks

  • Spanaut took lots of great pictures of Google’s Geo Developer Day and put them on Flickr.
  • Mikel Maron’s GeoRSS talk at Where 2.0 is getting good airplay: O’Reilly Radar succinctly lists Mikel’s top four reasons for using GeoRSS:
    • Linking systems. (One more less thing to find agreement on)
    • Monitoring geographic wikis (like OpenStreetMap or Tagzania)
    • Syndicating sensor data
    • Tearing down the walls (through standardization)

    GeoRSS Blog links to Mikel’s PowerPoint presentation. Must read!

    BTW, considering how none of Google’s product announcements involved support for GeoRSS, did anybody ask a Google person about the company’s plans regarding the emerging standard?

  • On Google Earth Community, notable developer rsgrillo discovers:

    The kml files generated by the new GE 4 uses a linefeed CHR(10) character to terminate a line.

    In the previous versions the lines were terminated by a carriage return CHR(13).

    If you’re a developer, read the rest.

  • PenguinOpus nudges developers towards a wonderful new debugging feature — you can copy and paste KML between Google Earth and the clipboard. Valery35 spells it out in a comment:

    1. Select placemark, folder etc

    2. Copy to clipboard (Ctrl+C, Ctrl+X)

    3. Paste into Notepad or other text editor (Ctrl+V)

    4. Change KML text. You can use Search+Replace, Undo etc commands.

    5. Select text and copy to clipboard. You can select part of text, if it correct KML

    &lt:folder>…&lt:/folder>, &lt:document>…&lt:/document> etc. If you copy KML with error, then it is simple not pasted.

    6. Paste into GE. Enjoy!

  • Mapdex’s Jeremy wishes Google developers had some more GIS background. He explains.
  • Another Where 2.0 KML-related press release: Media Machines announces KML2X3D, where X3D is an ISO standard for 3D computer graphics. (Too much going on right now for me to read up on this, but I will when Where 2.0 is over.) My hunch is that the support for X3D announced today, which dovetails Google’s embrace of COLLADA for textures in KML yesterday, is the beginning of far more game-like uses for Google Earth. (More on X3D)
  • They announced it last week, but are announcing it again at Where 2.0, for good measure, or something: AutoDesk Civil 3D 2007 has an extension for exporting KML. At least it’s garnering a good blog review at Between the Poles.
  • BTW, Anything GeoSpatial has been doing some great liveblogging of Where 2.0, in case you’re not there.