Tuesday, November 29, 2011

Coast(less) City - A DC Cities Conundrum

If you're a regular reader, you know this blog has more than once explored the question of where DC's fictional cities could be. With the New52, everything is up in the air again, and the Internet has been abuzz for almost a week regarding this page from Josh Fialkov's I, Vampire #3:It looks from this "meanwhile in the various time zones" that goes from East to West, that both Star City and Coast City, both formerly on the West Coast, have been pushed eastward. Now that Green Arrow is back in Seattle, Star City can redefine itself, no problem. In fact, I'd love to see it resituated in Texas (Central Time), as the lone star of the Lone Star State. It's a state with a distinct flavor or four, and a unique environment for a would-be superhero. Perhaps somewhere El Paso's Blue Beetle could move to when he grows up.

The real problem, though, is Coast City now situated in Mountain Time. See, there's no coast in that time zone. Not unless the city's in Mexico, which it clearly isn't. We're left with four possibilities:
-It's a mistake. Ignore it.
-Part of Mexico has been annexed by the U.S. in the New DCU.
-"Coast" is ironic, much like "Greenland" is icy and "Iceland" is green.
-The definition of Coast has been extended to lakeside topography. Maybe Coast City is somehow facing Salt Lake City now.

For me, the missed opportunity was to do away with Coast City altogether. I mean, do we really need it? Hal Jordan's job always took him to some desert base anyway, so why not have him based in Nevada. He's not the defender of a particular city, after all, but of an entire Sector. Eliminating his contextualizing city would have promoted his actual role (and not been too far off the way Green Lantern's world has been portrayed of late). Sometimes I think the trouble with the New DC isn't that too much has changed, but rather that NOT ENOUGH has.

9 comments:

Trey said...

Maybe Los Angeles has it's on timezone in the NDCU? ;)

Until the late eighties Star City was often placed on the Great Lakes or on the East Coast, so a change back to that isn't so bad, I guess. I'm inclined to call the Coast City thing a mistake.

Anonymous said...

Typical stupid mistake from DC's editors, who are either overworked, incompetent or both.

Anonymous said...

It was Hal's job to set the Coast City clock back an hour. Hal's good at smacking down bad guys, but he's not known for his attention to detail.

Siskoid said...

Especially now that Sinestro is the GL of Sector 2814.

JHeaton said...

Coast City was originally a railroad town called Coyote Corners. It was renamed after Jedidiah Coast, a wealthy landowner who became even richer when he discovered gold on his property, made the town the base of his growing business empire.

Jeff R. said...

Coast City is, like some parts of Indiana, contrarian enough to not observe Daylight Savings Time.

(This means that it has to be located on the Florida Panhandle to get that time and an actual Coast.)

Siskoid said...

So close neighbors to Atlanta or New Orleans? Hal must have one hell of a commute to get to that desert air base!

Wayne Allen Sallee said...

@Trey, in fact, in that DC Atlas for the RPG, the map of Star City used a backwards map of sections of Chicago and Indiana right on the state line. I don't read I, Vampire, but I could see Coast City near, say, well, OK, I can't see it in MST. Star City could easily have a different time zone if placed in a certain part of the US. Of course, Arizona doesn't use Daylight Savings Time, which is neither here nor there. The editors cannot or do not bother to edit anymore.

@Siskoid, remember a time when mistakes were often corrected the next time around?

Siskoid said...

Next time is going to be next month, so we'll see.