HyNor

The HyNor-project was a nationally supported project[1] which purpose was to facilitate and coordinate the introduction of hydrogen as a fuel in Norway, running from 2003 to 2012. Toward the commercial introduction of hydrogen vehicles in 2015, the HyNor-project focused on acquiring an early pre-commercial fleet of hydrogen vehicles, and keeping a close dialogue with the leading car manufacturers and other similar initiatives in the Nordic countries and around the world.

History

The HyNor-project started out as a hydrogen highway-project in Norway. It was initiated by large industrial actors such as Statoil and Norsk Hydro in 2003 with the goal of a market-realistic demonstration of hydrogen refuelling stations, as well as hydrogen vehicles. Several hydrogen refuelling stations were built along the 580-kilometer (360 mi) route from Oslo to Stavanger. Norway's first hydrogen fueling station was opened in 2006 near Stavanger, the second in Porsgrunn in 2007, and two stations were opened in Oslo and Lier in 2009. There were also hydrogen stations planned for Bergen and Lyngdal, but these projects were never carried out.

The official opening of the HyNor hydrogen highway -project took place on 11 May 2009 in Oslo, and most of the stations, except for the one in Stavanger are still in operation today. The infrastructure is part of the Scandinavian hydrogen highway partnership.

In October 2011, Statoil announced they wanted to close the hydrogen refuelling stations in Stavanger, Porsgrunn, Drammen and Oslo after 2012.[2] A new company, HyOP,[3] was established to take over the ownership and operation of the stations, and has done so since May 2012.

In June 2012 a new refueling station was opened at Akershus EnergiPark in Skedsmo.[4]

Vehicles

The HyNor-project has tested several different hydrogen vehicles:

Current station network

  • Stavanger - H2 from natural gas reforming (steam reforming), HCNG 8%, at 350 and 700 Bar (shut down in November 2011)
  • Porsgrunn - H2 byproduct from chlorine production, 700 bar refueling
  • Drammen - Trucked-in hydrogen, 700 bar refueling (shutdown in 2015 and moved to Oslo airport Gardermoen)[5]
  • Oslo - Trucked-in hydrogen, 700 bar refueling
  • Oslo - Gaustad - On-site electrolysis (10 Nm3/h), 700 bar refueling
  • Oslo - Rosenholm - On-site electrolysis (2x60 Nm3/h), 350 bar refueling (bus-only station)
  • Lillestrøm - H2 from biogas via Sorption Enhanced Steam Methane Reforming(SE-SMR) and solar electrolysis, 700 bar refueling.[6][7]
gollark: What? Why does it say it's doing a sequential scan now? Æ all is bee.
gollark: Slower, even.
gollark: Oops, it turns out I'm accidentally sorting by it instead of the rank, but it's equally slow after fixing that.
gollark: ```nonlocality=# EXPLAIN ANALYZE SELECT url, ts_rank(fts, query), ts_headline(fts::text, query, 'MaxWords=60') AS rank FROM pages, websearch_to_tsquery('bee') query WHERE fts @@ query ORDER BY rank LIMIT 1; QUERY PLAN ------------------------------------------------------------------------------------------------------------------------------------------------- Limit (cost=860.92..860.92 rows=1 width=96) (actual time=8506.425..8506.427 rows=1 loops=1) -> Sort (cost=860.92..861.05 rows=52 width=96) (actual time=8506.423..8506.425 rows=1 loops=1) Sort Key: (ts_headline((pages.fts)::text, query.query, 'MaxWords=60'::text)) Sort Method: top-N heapsort Memory: 25kB -> Nested Loop (cost=688.65..860.66 rows=52 width=96) (actual time=1.362..8505.403 rows=348 loops=1) -> Function Scan on websearch_to_tsquery query (cost=0.25..0.26 rows=1 width=32) (actual time=0.023..0.025 rows=1 loops=1) -> Bitmap Heap Scan on pages (cost=688.40..846.49 rows=52 width=142) (actual time=0.353..1.502 rows=348 loops=1) Recheck Cond: (fts @@ query.query) Heap Blocks: exact=231 -> Bitmap Index Scan on page_search_index (cost=0.00..688.39 rows=52 width=0) (actual time=0.320..0.320 rows=387 loops=1) Index Cond: (fts @@ query.query) Planning Time: 0.190 ms Execution Time: 8506.463 ms(13 rows)```
gollark: It's not a condition, it's an extra row on the output, and I can see exactly what it does via `EXPLAIN ANALYZE`.

See also

References

Notes

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