EDIT: The registered copyright they're referring to is here: http://cocatalog.loc.gov/cgi-bin/Pwebrecon.cgi?Search_Arg=tx...
EDIT: The registered copyright they're referring to is here: http://cocatalog.loc.gov/cgi-bin/Pwebrecon.cgi?Search_Arg=tx...
northamerica:
# From Paul Eggert (2006-03-22):
# A good source for time zone historical data in the US is
# Thomas G. Shanks, The American Atlas (5th edition),
# San Diego: ACS Publications, Inc. (1991).
# Make sure you have the errata sheet; the book is somewhat useless without it.
# It is the source for most of the pre-1991 US entries below.
europe: # From Paul Eggert (2006-03-22):
# A good source for time zone historical data outside the U.S. is
# Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition),
# San Diego: ACS Publications, Inc. (2003).
As far as I know, even if the book is copyrighted, the raw information contained in it shouldn't be? These atlases set forth interpretations of historical
time zone information pertaining to innumerable locations
throughout the world, based upon the compilation of
historical research and documentation regarding
applicable time zones officially and/or in actuality in
effect, given the actual latitude and longitudes of
specific locations throughout the world. # Austria
# From Paul Eggert (2006-03-22): Shanks & Pottenger give 1918-06-16 and
# 1945-11-18, but the Austrian Federal Office of Metrology and
# Surveying (BEV) gives 1918-09-16 and for Vienna gives the "alleged"
# date of 1945-04-12 with no time. For the 1980-04-06 transition
# Shanks & Pottenger give 02:00, the BEV 00:00. Go with the BEV,
# and guess 02:00 for 1945-04-12.That's correct. Supreme Court decision. Said decision is the reason why you occasionally read news articles about the U.S. considering some form of database protection laws - to make those databases protectable under law (and therefore to make this lawsuit legitimate).
Then there's the openOV project, a new project bringing together data from lots of sources and talking to lots of transport companies and agencies. Most transport tenders include a clause requiring data to be supplied to "national journey planners", so there's hope. Just today they're working on GTFS feeds for most of the Netherlands.
The Dutch Railways (NS) now has an API but it's mainly consumer facing data, and nothing truely helpful.
tl;dr: Our transit APIs are stuck in 2005 but making headway.
Legal attacks don't have to have merit to be successful.