Nishiyama Station (Niigata)

Nishiyama Station (西山駅, Nishiyama-eki) is a railway station in the city of Kashiwazaki, Niigata, Japan, operated by East Japan Railway Company (JR East).

Nishiyama Station

西山駅
Nishiyama Station, October 2009
LocationNishiyama-cho, Kashiwazaki-shi, Niigata-ken 949-4141
Japan
Coordinates37°26′54″N 138°38′30″E
Operated by JR East
Line(s)■ Echigo Line
Distance12.8 km from Kashiwazaki
Platforms2 side platforms
Other information
Statusunstaffed
Websitewww.jreast.co.jp/estation/station/info.aspx?StationCd=1175
History
Opened11 November 1912
Traffic
Passengers (FY2010)42 daily[1]
Services
Preceding station JR East Following station
Kariwa
toward Kashiwazaki
 Echigo Line Raihai
toward Niigata
Location
Nishiyama Station
Location within JR Echigo Line
Nishiyama Station
Nishiyama Station (Japan)

Lines

Nishiyama Station is served by the Echigo Line and is 12.8 kilometers from the terminus of the line at Kashiwazaki Station.

Station layout

The station consists of a two opposed ground-level side platforms connected to the station building by a footbridge.

The station is unattended. Suica farecard cannot be used at this station.[2]

Platforms
1 ■ Echigo Line for Yoshida, Niigata,
for Kashiwazaki
2 ■ Echigo Line for Kashiwazaki (peak time only)

History

Nishiyama Station opened on 11 November 1912. With the privatization of Japanese National Railways (JNR) on 1 April 1987, the station came under the control of JR East. A new station building was completed in 1992.

Surrounding area
gollark: Keep cc.znepb.me.
gollark: If you configured it wrong during setup of whatever this is somehow, then it won't match. PotatOS has the law enforcement access mechanism (PS#7D7499AB) which also currently doubles as "forgot password" handling, but not every OS does that.
gollark: How do you know your password is the right one?
gollark: I should assign unique IDs to the other sandbox escape bugs.
gollark: My "fix" is this:```lua--[["Fix" for bug PS#E9DCC81BSummary: `pcall(getfenv, -1)` seemingly returned the environment outside the sandbox.Based on some testing, this seems like some bizarre optimization-type feature gone wrong.It seems that something is simplifying `pcall(getfenv)` to just directly calling `getfenv` and ignoring the environment... as well as, *somehow*, `function() return getfenv() end` and such.The initial attempt at making this work did `return (fn(...))` instead of `return fn(...)` in an attempt to make it not do this, but of course that somehow broke horribly. I don't know what's going on at this point.This is probably a bit of a performance hit, and more problematically liable to go away if this is actually some bizarre interpreter feature and the fix gets optimized away.Unfortunately I don't have any better ideas. Also, I haven't tried this with xpcall, but it's probably possible, so I'm attempting to fix that too.]]local real_pcall = pcallfunction _G.pcall(fn, ...) return real_pcall(function(...) local ret = {fn(...)} return unpack(ret) end, ...)end local real_xpcall = xpcallfunction _G.xpcall(fn, handler) return real_xpcall(function() local ret = {fn()} return unpack(ret) end, handler)end```which appears to work at least?

See also

References
  1. 柏崎市統計年鑑(平成24年版) [Kashiwazaki City Statistical Yearbook (Fiscal 2012)] (PDF) (in Japanese). Japan: Kashiwazaki City. Retrieved 17 November 2017.
  2. Suica＞利用可能エリア＞新潟エリア＞拡大図 [Suica Area in Niigata] (in Japanese). Japan: JR East. Retrieved 17 November 2017.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.