Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The ".googlemaps" folder #276

Closed
GoogleCodeExporter opened this issue Aug 28, 2015 · 3 comments
Closed

The ".googlemaps" folder #276

GoogleCodeExporter opened this issue Aug 28, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Email from Kevin Lo

Since we use Yahoo maps by default, here's a trivial diff to change
tiles path to ".yahoomaps" instead of ".googlemaps".
Does it make sense to you? If so, I'll commit it, thanks.

Original issue reported on code.google.com by heldersepu on 20 Jul 2011 at 12:36

Attachments:

@GoogleCodeExporter
Copy link
Author

Please do not commit just yet, that will create a backward
compatibility issue...

The ".googlemaps" folder holds all settings from the user:
 - gmapcatcher.conf
 - locations
 - markers

...and we already have an option to keep all tiles in individual
folders, see attached image.
it will create a tree structure similar to this:
+---.googlemaps
|   +---cloudmadeTiles
|   +---download
|   +---hyb_tiles
|   +---vemap
|   +---yahoohyb
|   +---yahoomap

The way I see it ".googlemaps" folder is a container for everything in
the application, and it should probably be called something else like
".GMapCatcher"

Original comment by heldersepu on 20 Jul 2011 at 12:37

Attachments:

@GoogleCodeExporter
Copy link
Author

I just commit some changes r1146 now new installations will use ".GMapCatcher"

Original comment by heldersepu on 2 Aug 2011 at 2:49

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by heldersepu on 27 Feb 2012 at 2:00

  • Added labels: Milestone-Release0.77

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant