Hello, is it possible to import an observation list with LiveSky basic?
Thank you.
Olivier
Hello, is it possible to import an observation list with LiveSky basic?
Thank you.
Olivier
Oliver,
At the moment LiveSky.com can only export data. Importing data is next on the roadmap for LiveSky.com.
Thanks!
Oliver,
Note, importing data via LiveSky.com will probably require a premium subscription when the feature is available.
Thanks!
Thanks. In fact I'm looking to import lists into sky safari 6 pro. How can I do it?
Note: it's easy in sky safari 5 pro through iCloud. But I don't know how to do it in version 6. So I keep using version 5 while I purchased version 6.
iOS or Android?
iOS 9.3.5
Will any future update just be about importing lists or would it import observations? I now use LiveSky for all my observations but have past observations i have recorded and would like to add these into LiveSky so that when i target an object in Sky Safari i can see if it is one i have observed before i had Sky Safari.
Chris,
LiveSky import and export functionality will be much improved in the future. LiveSky is fundamental to all our apps.
Thanks!
OK so would you recommend that I don't laboriusly re-enter over 500 past target observations into LiveSky and wait for the upgrade?!!
Chris,
Options include:
https://knightware.biz/community/public/dsp7/kb/article-25.htm#converter
How To Create A Skylist File:
EndObject=SkyObject
SkyObject=BeginObject
EndObject=SkyObject
SkyObject=BeginObject
EndObject=SkyObject
SkyObject=BeginObject
EndObject=SkyObject
SkyObject=BeginObject
EndObject=SkyObject
Lines may be separated by a single linefeed (LF) character ('\n', ASCII hex code 0x0A, decimal value 10), or by carriage return (CR) characters ('\r', ASCII code 0x0D, decimal 13), or by CR-LF pairs. In other words, your text file may be a unix-style text file, or a classic Mac or DOS/Windows text file.
The first line must be SkySafariObservingListVersion=3.0
Observing list entries are groups of keyword=value pairs. Groups are demarcated by BeginObject
and EndObject
lines.
In the sample above, we've indented the keyword/value pairs within each object for clarity, but you don't have to. SkySafari strips out leading whitespace when importing the file.
The ObjectID
field is what SkySafari uses internally to identify the object. Since you don't know this, you can use the following:
1,-1,-1
2,-1,-1
4,-1,-1
SkySafari will try to find the object based on the CatalogNumber
or CommonName
values, and fix up the ObjectID
values internally after it imports the list.
The CatalogNumber
values are used preferentially instead of the name(s). Please use the same catalog abbreviations that SkySafari uses, e.g. Alpha CMa, HR 7001, M 97, NGC 1695. If the object has no CatalogNumber
(like Jupiter), then enter its name(s) in the CommonName
field. For asteroids, the asteroid number is the CatalogNumber
; use the CommonName
field for all other solar system object identifiers.
CatalogNumber
s and CommonName
s you've specified to import properly. This is how SkySafari resolves ambiguities between diffiferent objects with the same name: for example, comet Garradd (C/2009 P1) vs. comet Garradd (C/2008 J5), or the asteroid Europa (number 52) vs. Europa (Jupiter's moon, no number). In most cases, though, only a single CatalogNumber
or CommonName
should be required to uniquely identify the object.
DateObserved
and Comment
are optional. DateObserved
is the julian date on which your observation took place; Comment
is the notes you want associated with the object. Newlines in the notes should be indicated with a \n sequence.