[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orekit Developers] OEMWriter Work
- To: orekit-developers@orekit.org
- Subject: Re: [Orekit Developers] OEMWriter Work
- From: Hank Grabowski <hank@applieddefense.com>
- Date: Tue, 27 Dec 2016 17:25:14 -0500
- Authentication-results: kepler.orekit.org; dkim=pass reason="2048-bit key; insecure key" header.d=applieddefense-com.20150623.gappssmtp.com header.i=@applieddefense-com.20150623.gappssmtp.com header.b=r2P8pNGm; dkim-adsp=none (insecure policy); dkim-atps=neutral
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=applieddefense-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=RzwNjkihzljBerwhEnIGyYE+2hh/nu72OPqtb4qJ07U=; b=r2P8pNGm6QvHH8I9Iax9qw6oYin/T3M9ME2sWg7zkkvJzI8XGmH8GqqmxhqHir7U9n 9Rs6MiPXMg8tDkcVWmmHDbcLc2QuRpNj5SEMOaXQK/BLXmKNE3Sz7eD3xs0RWLNvZ/86 J21Gn9CNkP+TP3Az9DpJFmYt+ajMEMCznzsb5PkOQtNbPHVmdHz2CmmCRZTYFIzThIwx SctlzzNenkR2cpZSDmajZrsrPUPQMFRTeNJt1fzam9ZNferpI0Pt0eAN+pL82JaB6wsP wHOXwrqIJW9ok1UpyuKrAGtHACKsuIo8jpmXSL7dO9WPHXJkTByw8mqxMzo18cXEWslP /94A==
- In-reply-to: <CAP2my4ayDvw-mynLn5D9RS_HUUT0P6k9b0BcqowNX5cp4fv2aQ@mail.gmail.com>
- References: <CAP2my4ZHhzSrDnUWkHX8jRGT41-9FKPk=fXFRozdSahbk17eOg@mail.gmail.com> <20161227191926.Horde.Udxza9ggN2TF9oY5362LmA1@messagerie.c-s.fr> <CAP2my4ayDvw-mynLn5D9RS_HUUT0P6k9b0BcqowNX5cp4fv2aQ@mail.gmail.com>
Along the lines of how I used it in my original project we need to take internally generated ephemeris and dump it to an OEM file. It doesn't jump out at me that there is a way to do that, but I missed the new EphemerisFile stuff and the corresponding linkage to the already written OEMParser so it wouldn't shock me if I missed this as well. If there isn't I'm thinking of making a second change where we implement an OrekitEphemerisFile or BoundedPropagatorEphemerisFile and a corresponding factory object that builds it to support at least rudimentary output of Orekit generated ephemeris out of the box.