EVE Market Uploader ?

[Jimi]

I'm seeing messages in the EMDR feed with generator name 'EVE Markets Uploader' (v0.2).

Otaci, are you behind this?

[Daniel Connolly]

Nope, its not me, im not sending anything out yet. 

On Mon, Jun 18, 2012 at 10:46 PM, Jimi <jim...@gmail.com> wrote:

I'm seeing messages in the EMDR feed with generator name 'EVE Markets Uploader' (v0.2).

Otaci, are you behind this?

--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.
To view this discussion on the web visit https://groups.google.com/d/msg/eve-emdr/-/ou_pzOJgdaEJ.
To post to this group, send email to eve-...@googlegroups.com.
To unsubscribe from this group, send email to eve-emdr+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eve-emdr?hl=en.

[James Muscat]

Nope, that one is my fault... is there a problem?

James

[Jimi]

Mo prob, just wondering what format are you using?

[James Muscat]

I'm running my own custom cache reader and uploader. Only just added
support for the unified upload format so I'm half expecting someone to
tell me I'm doing it wrong(TM) at some point!

James

[Gregory Taylor]

Don't be too afraid, we need to be building up validation to prevent obviously invalid data from reaching the consumers. Just look at it as  helping test for us :)

Greg

--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.

To post to this group, send email to eve-...@googlegroups.com.

To unsubscribe from this group, send email to eve-emdr+unsubscribe@googlegroups.com.

[Jimi]

Well, times of generatedAt seem to be UTC+1 which is an issue. 'generatedAt' should be the time that the cache file was created in the cache folder and is taken from inside the parsed cache data.

[James Muscat]

OK, two separate things here...

Firstly, I was having problems extracting the timestamp from the cache
files, so I was using the system date in that field. Your comment made
me go back and spot my mistake (int != long!), so I'm now including the
actual value taken from the cache file :)

Is the timezone a problem? It's presumably because my system is running
in GMT+1 right now, but as long as it's accurate I don't see why that
should cause issues.

James

> --
> You received this message because you are subscribed to the Google
> Groups "EVE Market Data Relay" group.

> To view this discussion on the web visit

> https://groups.google.com/d/msg/eve-emdr/-/y74KbMyF070J.

> To post to this group, send email to eve-...@googlegroups.com.
> To unsubscribe from this group, send email to

> eve-emdr+u...@googlegroups.com.

[Gregory Taylor]

As long as you have the offset at the end, it's not a problem.

eve-emdr+unsubscribe@googlegroups.com.

For more options, visit this group at
http://groups.google.com/group/eve-emdr?hl=en.

--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.

To post to this group, send email to eve-...@googlegroups.com.

To unsubscribe from this group, send email to eve-emdr+unsubscribe@googlegroups.com.

[Jimi]

They do have the offset at the end but that value is still +00:00 instead of +01:00. the time value is off by +1 hour instead being the UTC value.

In order to help James the timestamp is in Win filetime format. What programming language are you using?

[Gregory Taylor]

It doesn't have to be +00, as long as it's correct. It only need be a valid ISO 8601 formatted date, which is it, so he's all good. 

Everyone needs to be doing the right thing and parsing the entire date, not just everything leading up to the offset. As long as that is done, the offset doesn't matter.

Also, the gateway converts it all to straight zero-offset UTC, anyway.

Greg

On Tue, Jun 19, 2012 at 2:56 AM, Jimi <jim...@gmail.com> wrote:

They do have the offset at the end but that value is still +00:00 instead of +01:00. the time value is off by +1 hour instead being the UTC value.

In order to help James the timestamp is in Win filetime format. What programming language are you using?

--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.

To view this discussion on the web visit https://groups.google.com/d/msg/eve-emdr/-/v2l0y_68-IgJ.

To post to this group, send email to eve-...@googlegroups.com.

To unsubscribe from this group, send email to eve-emdr+u...@googlegroups.com.

[Jimi]

It doesn't only have to be in the correct ISO format but also the data has to be correct. It's pretty clear that all times have to be UTC and in case of TZ deviation this is stated in the TZ offset.

So it's not OK.

[Gregory Taylor]

You are wrong, Jimi. The examples are 0 offset, but the spec only explicitly requires a valid ISO format date.

"The current data/time in ISO 8601 format (example 2011-10-22T15:46:00+00:00) when the JSON message was created."
"The data/time in ISO 8601 format (example 2011-10-22T15:46:00+00:00) when the rowset was created"
"The date/time the order was issued in ISO 8601 format (example 2011-12-03T10:53:26+00:00)"
"The date/time the history was issued in ISO 8601 format (example 2011-12-03T00:00:00+00:00)"

"So to clarify The ISO 8601 standard and how it should be used in this format. As in all the examples above it needs to be in full data and time including time zone offset format. The zone zone information is important as date/times without it are assumed to be in local time which will cause problems since often the data will be sent to sites in other time zones. The standard allows for the time offset to be done as just 'z' if using UTC but it is recommend everyone use the +00:00 form instead as it would make manual decoding of the offset easier. It is recommended that everyone writing a decode take both cases into consideration as using 'z' instead will not be considered invalid just not recommended per the format."

As long as there are valid offsets provided, you need not use 0 offsets. I'm not willing to let this silly discussion spam our members' inboxes much further, so let's please move on to something new and more interesting.

Greg

On Tue, Jun 19, 2012 at 8:53 AM, Jimi <jim...@gmail.com> wrote:

It doesn't only have to be in the correct ISO format but also the data has to be correct. It's pretty clear that all times have to be UTC and in case of TZ deviation this is stated in the TZ offset.

So it's not OK.

--

You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.

To view this discussion on the web visit https://groups.google.com/d/msg/eve-emdr/-/rLNwgakBYcUJ.

[Jimi]

What you don't get is that the datetime value in James messages was wrong in the sense of the time itself.

At the time I'm writing this the UTC is 17:10:29, so if I generate a message the 'generatedAt' field should be 2012-06-19T17:10: 29+00:00. James message was coming in as 2012-06-19T18:10: 29+00:00 which is obviously wrong as this is one UTC hour in the future. I hope you got it now.

[James Muscat]

Jimi,

I understand what you are saying and will check when I get home
tonight. (For some reason my employers don't appreciate me firing up
an EVE client to check things in work hours ;) )

James

> --
> You received this message because you are subscribed to the Google Groups
> "EVE Market Data Relay" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/eve-emdr/-/vMEzDcOSlw4J.

[James Muscat]

OK, so I just checked and I'm generating the dates correctly:

"generatedAt":"2012-06-19T22:41:52+01:00" from a message I just produced.

Could this be a repeat of the "strips timezone data from timestamps" bug
that was talked about with EVEMon earlier?

James

[Gregory Taylor]

Can you hop on IRC really quick? May be better to go over this there real fast.

Greg

eve-emdr+unsubscribe@googlegroups.com.

For more options, visit this group at
http://groups.google.com/group/eve-emdr?hl=en.

--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.

To post to this group, send email to eve-...@googlegroups.com.

To unsubscribe from this group, send email to eve-emdr+unsubscribe@googlegroups.com.