Ilia Choly

We could use a pattern similar to the [database/sql#NullInt64](https://golang.org/pkg/database/sql/#NullFloat64). ``` go type Float64 struct { Float64 float64 Valid bool // Valid is true if Float64 is not NULL } //...

One option is to introduce the Null types along with methods on the `nmea.Parser` type. You could then override the default message types. Here's a modified version of the example...

I went though the existing types and it seems like we'd only need `Float64` and `Int64`. `Time` and `Date` are already nullable (they have a `Valid` field). `string` doesn't need...

@adrianmo take a look when you have a moment.

Looks like it's time for a v2.

Yep, I agree.

Not sure how to fix this without a breaking change.

@adrianmo can you enable the wiki?

I've tried starting this a few times and it's harder than I imagined.

It's really annoying that this vendor didn't follow the convention of prefixing proprietary message types with "P" talker id.