Custom EPSG should use traditional coord order

[ingalls]

Context

It appears as though features retrieved from a gdal source use traditional coordinate order. This results in our reading of OGR sources working perfectly if the Proj string is built directly from the source - but failing if specified manually.

Actions

• Use traditional coord order for custom SRS
• Short Circuit if EPSG is already 4326
• Generate list of OGR sources with manual srs tags and make sure I don't create another regression mess
  • au/christmas_island.json (Good As Is)
  • ch/basel-stadt.json
  • ch/geneva.json
  • ch/bern.json
  • ch/schaffhausen.json
  • de/hh/statewide.json
  • de/nw/city_of_wuppertal.json
  • it/45/ferrara.json
  • it/45/bologna.json
  • it/04/acerra.json
  • it/52/firenze.json
  • it/42/statewide.json
  • it/21/city_of_biella.json
  • it/21/torino.json
  • it/34/city_of_verona.json
  • li/countrywide.json
  • nz/countrywide.json (Buildings)
  • se/municipality_of_nacka.json
  • ua/63/city_of_kharkiv.json
  • ua/12/city_of_dnipropetrovsk.json
  • us/pa/forest.json
  • us/ut/statewide.json
  • us/wy/fremont.json
  • us/wy/hot_springs.json
  • us/wy/statewide.json
  • us/nc/anson.json

Fixes: #26

cc @stefanb