I just played for a few days with the free version of Locus and, amongst others, also imported some POIs from KML/KMZ files. Though that's great stuff, I'd suggest some improvements for this:
Map sources to POIs
As it is now, one imports a KML/KMZ into a category. Multiple sources (i.e. KML/KMZ files in this context) can be imported into one category this way. But if one finds a better source for parts of them, or want to get rid of some for some other reason,, it is "all or nothing": One can either delete all POIs of a category, or none. Or one has to delete each POI separately, which can be quite annoying.
Now, if the source would be stored along (and here I mean the file name), one could remove all POIs of a given filename.
Multiple files in one KMZ
KMZ files are not simply a "zipped KML file". Sure, they can be this -- but they can be much more: One could include icons and images this way. And as Locus supports an offline mode, those additional files could be used along. For example, not only a textual description for a POI (using the KML <description> tag), but, say, a photo of the location, contained in the description using a relative path with an <IMG> tag. And for sure one could use specific icons.
With that, I could provide some of my KMZ files for the POI sources here. If an example KMZ file is needed, just let me know and I will provide it.
Map sources to POIs
As it is now, one imports a KML/KMZ into a category. Multiple sources (i.e. KML/KMZ files in this context) can be imported into one category this way. But if one finds a better source for parts of them, or want to get rid of some for some other reason,, it is "all or nothing": One can either delete all POIs of a category, or none. Or one has to delete each POI separately, which can be quite annoying.
Now, if the source would be stored along (and here I mean the file name), one could remove all POIs of a given filename.
Multiple files in one KMZ
KMZ files are not simply a "zipped KML file". Sure, they can be this -- but they can be much more: One could include icons and images this way. And as Locus supports an offline mode, those additional files could be used along. For example, not only a textual description for a POI (using the KML <description> tag), but, say, a photo of the location, contained in the description using a relative path with an <IMG> tag. And for sure one could use specific icons.
With that, I could provide some of my KMZ files for the POI sources here. If an example KMZ file is needed, just let me know and I will provide it.
