Location: INVALID about tinygpsplus

[TD-er]

Nope, NOT calling serial.available() is faster as you need to query something that's for sure a call to some hardware.
And it might be possible you keep on running longer when checking again for new available bytes, where in the first code example you only check this once and just assume no more bytes have entered the serial buffer.

[JasonPittenger]

I see you define the baud for GPS, but that is never used again.

static const uint32_t GPSBaud = 9600;

That's fine, because you later initialize two serial ports at 9600 baud.
Serial.begin(9600);
Serial2.begin(9600);

It looks like Serial is your debugging port, based on usage in your code.
I assume then that Serial2 is your GPS serial port.
I only see you reading it inside the function display(), which is called in loop()

void display()
{
gps.encode(Serial2.read());
}

This will not work.
The read() function returns the first byte of incoming serial data available (or -1 if no data is available).
This means you're only grabbing a single byte and trying to display the data.
Instead, put this inside loop()

uint16_t GPSbytesAvailable;
GPSbytesAvailable = Serial2.available();
if(GPSbytesAvailable)
{
	while(GPSbytesAvailable--)
	{
		gps.encode(Serial2.read());
	}
}

or

while (Serial2.available() > 0)
{
	gps.encode(Serial2.read);
}

The first code is a little faster because it doesn't repeatedly call Serial2.available();

[svdrummer]

I was wondering why "GPSbytesAvailable--" is faster?