> Given that the Gmaps v2 compression method for is now no longer
> available, is my idea the correct strategy?
It is a bit of a hack but you are still able to use classic
"fromEncded" polys.
See:
http://www.polylib.us/polycluster/coast/encoded.html
It uses the "points" string. It ignores the "levels" string.
The "zoom string" was always confusing. It adds 50% to the total
payload. It does not shrink the poly itself. Its purpose was
marginal at best. Both the API & PolyCluster perform "on the fly"
point reduction without auxilliary help.
You might consider using an HTA to edit your polys. You will be stuck
with Internet Explorer but you will be able to use the
ActiveXObject("Scripting.FileSystemObject") to directly read/write
your hard drive.
Once your edits are complete, you can save in JSON format without the
use of a database manager. Basically, it is just a bunch of files
with unique URLs. Access speed is improved because it does not
require a database manager. Your monthly web host fee will be reduced
also.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-maps-js-api-v3?hl=en.
