-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature Request: Hexadecimal #1
Comments
It probably would. Could you make a pull request with an example that illustrates that it's a more efficient format? |
(Translated by Google) Sorry, I do not use GIT . I can not send a 'Pull Request' . Anyway , I send my modified code . Originally I thought to save the values in Hexadecimal , to save a few bytes. But then , I see that 36 is the maximum possible value , to transform into Javascript, it says in http://www.w3schools.com/jsref/jsref_tostring_number.asp As an example of the savings, I mention that I have a file with 5 polygons . The file has more than 7200 coordinates. The size of the original file is ~ 212KB and finished ~ 82kb ( ~ 39 % ) These are the new / modified functions:
|
(Translated by Google)
Hi
It did not even save more space if you'll keep the numbers in hexadecimal format ?
The text was updated successfully, but these errors were encountered: