Skip to content
This repository has been archived by the owner on Aug 14, 2022. It is now read-only.

Suggestion for format of lat_long_to_octant.js output #35

Open
ecopirate opened this issue Sep 3, 2019 · 0 comments
Open

Suggestion for format of lat_long_to_octant.js output #35

ecopirate opened this issue Sep 3, 2019 · 0 comments

Comments

@ecopirate
Copy link

Greetings,

Many thanks for the absolutely awesome tool.
Just a quick suggestion for format of the lat_long_to_octant.js output:
Please include appropriate +/- symbol for Lat/Lon.
That might be particularly helpful at some stage for Qctants close to either the Equator Greenwich Meridian.

For example:

Octant Level: 17

{ n: 51.50115966796875,
s: 51.4984130859375,
w: 0.120849609375,
e: 0.1263427734375 }
30604240604272700 (Close to but west of the Greenwich Meridian.)

Should actually have negative coordinates for both west & east :

Octant Level: 17

{ n: 51.50115966796875,
s: 51.4984130859375,
w: -0.120849609375,
e: -0.1263427734375 }
30604240604272700

P.S. Even better a flat CSV output format such as: the following would allow even
easier GIS import:

Level_ID, Latitude, Longitude
LVL17_NW, 51.50115966796875,-0.120849609375
LVL17_NE, 51.50115966796875,-0.1263427734375
LVL17_SW, 51.4984130859375,-0.120849609375
LVL17_SE, 51.4984130859375,-0.1263427734375
LVL18_NW....
etc

Cheers,

Ian

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

No branches or pull requests

1 participant