Google
Official Google Earth Download Site

Google Earth Community System Reliability: HIGH

Support and Answers >> Collected Google Earth Wisdom (read only)

Jump to first unread post. Pages: 1
simon_a
Master Guide


Reged: 08/21/05
Posts: 1773
Loc: London, UK
Managing your Google Earth data
      #696307 - 11/24/06 01:25 PM

Hello,

If you only have a small number of placemarks in your My Places folder – maybe where you and you friends live and a few holiday destinations – you’re probably not too worried about how you manage and protect that data (although, if it’s important to you, making a backup every now and again would be useful).

However, if you’ve built up collections of placemarks, paths or polygons and your My Places folder has begun to grow, you should really consider how this data is managed.

This thread details some of the problems you might find with using just My Places to contain your data and then presents some suggestions to help manage your data more simply and more securely.

Let’s start by looking at problems with a large My Places folder


(If you have any suggestions about this article, please send me a Private Message )

Edited by simon_a (11/24/06 02:02 PM)


Post Extras: Print Post   Remind Me!   Report this Post  
simon_a
Master Guide


Reged: 08/21/05
Posts: 1773
Loc: London, UK
1 - Problems with a large My Places folder [Re: simon_a]
      #696327 - 11/24/06 01:47 PM

A large My Places folder can become a problem for the following reasons:
  • Extended time for the application to start-up
  • Difficulty in resolving problems with the file

    When Google Earth starts it must load the myplaces.kml file, which is stored on your hard drive in a user-specific application data folder. The more data in this file, the longer it will take for the application to read it into its internal data structure and display the hierarchy in the Places pane. Imagine what it would be like if, every time you opened your word processing application, it opened every document you’d ever written! It is clearly inefficient if you are not likely to work with most of the content of the My Places file.

    If things go wrong and the myplaces.kml file gets corrupted, you will probably find that Google Earth fails to load it on start up with a parse error, which means that the data structure presented in the file doesn’t make sense to the application. The file is a simple text file; KML has an XML-like structure and can be viewed with a XML editor or a simple text editor, which means that it is possible to view the file and look for the likely cause of the parse error. This becomes increasingly difficult the larger this file becomes.

    Edited by simon_a (11/24/06 01:58 PM)


    Post Extras: Print Post   Remind Me!   Report this Post  
  • simon_a
    Master Guide


    Reged: 08/21/05
    Posts: 1773
    Loc: London, UK
    2 - Issues with only using My Places for your data [Re: simon_a]
          #696329 - 11/24/06 01:49 PM

    If you never make copies or backups of your work you might run into these problems:
  • Risk of software or hardware problems corrupting the file
  • Risk of user error corrupting the file

    No software application is perfect; sometimes things go wrong and data gets corrupted. Similarly, hardware can fail, causing an application to stop without closing down in a clean way. Google Earth makes a backup of your myplaces.kml file but probably not as often as you’d like. For example, GE will take a copy of myplaces.kml when it starts up; if it doesn’t close cleanly, you will likely go back to this version when the application restarts, losing any edits you made during the session. If GE can’t find a valid file to load and you have no other copy, the only way out is trying to fix a remaining file, which could be difficult if it is very large (as mentioned above).

    How many times have you deleted or edited something by accident? We all do it from time to time. If you make mistake and you didn’t save a recent version yourself, you are likely to be faced with going back to the copy of myplaces.kml that GE made when it started, therefore losing any good changes you made, or having to accept the bad edit.

    Now let's look at some suggestions for managing your data in part 3...

    Edited by simon_a (11/24/06 01:58 PM)


    Post Extras: Print Post   Remind Me!   Report this Post  
  • simon_a
    Master Guide


    Reged: 08/21/05
    Posts: 1773
    Loc: London, UK
    3 - Managing your data in a simple and secure way [Re: simon_a]
          #696330 - 11/24/06 01:50 PM

    Here are some things that you can do to help organise and protect your work:
  • Manage your data in smaller groups outside of GE in folders on you hard disk (or file server) and bring work into GE as and when you need it
  • Make regular point-in-time copies of your work to your hard disk
  • Make backups of your folders to somewhere not on the same disk

    Organising your data outside of the GE application
    Let’s look at managing your data on your hard disk, outside of My Places. I’m going to assume that you’re using Windows, as most people do, but the same concepts will apply to Linux and Mac users.

    Firstly create a folder somewhere on your hard drive to contain all your GE data:



    I’ve chosen to create a folder called “ge” under the C: drive but anywhere is fine. I’ve then added a number of sub-folders to contain various GE-related things:
  • icons – I keep all my custom icons here
  • images – Any images for description bubbles live here
  • kml – here is where I keep all the kml files
  • tools – Excel spreadsheets with VBA macros for generating KML and other tools
  • downloads – for GE stuff I’ve downloaded

    Now, let’s look inside the most important folder, “kml”:



    I’ve got a separate sub-folder in here for each logical group of placemarks, paths and polygons – each of these corresponds to a folder that could be in My Places, or a KML document.

    OK, so now we have a Windows folder for each GE collection or project – let’s have a look inside one:



    Inside the “sncf rail stations” folder you’ll find various KML and KMZ files of my French rail placemarks – so why are there so many of them?

    Making point-in-time copies
    It makes sense to take point-in-time copies of your work every now and again. If you make a mistake or if your computer has a problem, you should be able to go back to the last point you saved your data. How do you do this? That’s simple: right-click on the object or folder in GE and choose “Save as…” (or equivalent for Mac or Linux). Don’t overwrite previous versions of that data that you’ve written – create a new file each time; a simple approach is to append a new number on the end of the name each time you save. This way, if you make a mistake, you can go back though the versions you’ve saved to just before the point when the mistake was made and still have access to any other good changes made afterwards.

    How often should you make point-in-time copies? That’s simple too: as often as you think how awful it would be if you lost your data since the last one! If you’re adding a large number of placemarks manually, you might not mind having to redo the work of 5 of them – 50 might be something quite different.

    Hard disks are fairly large these days (well, compared to the size of the KML files I work with) but if you find space is running low, take a back up of your “ge” folder (maybe to a CD) and delete some of the older versions.

    Now when you want to work with one of your data collections, simply open the appropriate KML file; it will open into Temporary Places in GE but you can simply move it into My Places if you want to work on it for a while. Of course, once you’re finished and happy with it, save it as a new version – then you can delete it from My Places if you want.
    If your work becomes corrupted – maybe you get a parse error when you try to load it – you now have a more reasonable choice of going back to the previous version or trying to troubleshoot the code in a smaller KML file.

    I have KML and KMZ files here but I would recommend keeping your work as KML in general and converting to the smaller KMZ format before sending it across the Internet (for example, by email or posting to this forum) – this is because saving as KMZ copied images (including custom icons) into the compressed file and this can cause problems if you come to work with the file further (see this post for more about the differences between KML and KMZ).

    Backups
    If your data is important to you, it should be backed up in case you have a problem and loose it; even though we’re now organising our data outside of the application (not all in My Places), it’s still all on one hard disk. What happens if that disk breaks or gets accidentally written over?

    Every now again you should take a back up of your data (to somewhere other than the same hard drive!). Clearly this goes for all of your data – not just the you GE data; if you don’t already have a backup plan, it might be worth investing in a CD/DVD writer or an external USB drive.

    So, there you go!
    In summary then, if you have lots of data, it’s better to have lots of simple sets rather than one big complex one – and if it’s important to you, make lots of copies and back it up often.

    Have fun!



    Simon.

    Edited by simon_a (11/24/06 01:57 PM)


    Post Extras: Print Post   Remind Me!   Report this Post  
  • Pages: 1




    Extra information
    0 registered and 2 anonymous users are browsing this forum.

    Moderator:  Jumble, Hill, Kempster, mcshea98, jeffryv, dulce, esterrett, regionator, NormB, Frank_McVey, geus, ZeroDeeFeX, LaBelleTerre, vagabondsailor, SupersonicBuddha, DWebb, BeadieJay, TheLedge, Cyclonic, no_stranger, LuciaM, tekgergedan, cantarell, toponym2006, Noisette, danescombe, Michal_Drewniak, mutex, marinerfan, Delta102, bebop, MarkAubin 

    Print Topic

    Forum Permissions
          You cannot start new topics
          You cannot reply to topics
          HTML is disabled
          UBBCode is enabled

    Rating: ****
    Topic views: 27451

    Rate this topic

    Jump to

    earth.google.com    bbs.keyhole.com

    *
    UBB.threads™ 6.5.1.1