postgis spatial reference ID (srid) = 4326, linestring endpoints do not look like latlong

[rbracket]

I would expect to see lat long from this query, instead saw feet?

SELECT
st_asewkt(osm_ways.geometry)
FROM
public.osm_ways limit 1;

"SRID=4326;LINESTRING(565378.109016 4187349.703712,565377.378041 4187339.811519)"

details: script was spiderosm_berkeley.py..
with this config file:
{
"gis_data_dir" : "/home/GISData/",
"out_dir" : "/home/katie/Berkeley/",
"postgis_enabled" : true,
"postgis_dbname" : "berkeley",
"postgis_user" : "postgres",
"postgis_password" : "******",
"postgis_port" : 5432,
"spatialite_enabled" : false
}

..logging notes.....
Reading /home/katie/.spiderosm.json
Reading ./config.spiderosm.json
=== 2014-12-09 11:36:25, spiderosm 0.3.6, init, INFO:
config.info: {u'version': u'0.3.6', 'sys.version': '2.7.3 (default, Feb 27 2014, 20:00:17) \n[GCC 4.6.3]', u'license': u'MIT', u'author': u'Michael Arnold', u'author_email': u'mha@spiderosm.org', 'sys.platform': 'linux2', u'homepage': u'http://spiderosm.org', 'os.name': 'posix', 'package_dir': '/usr/local/lib/python2.7/dist-packages/spiderosm'}
=== 2014-12-09 11:36:25, spiderosm 0.3.6, init, INFO:
config.settings: {u'postgis_dbname': u'berkeley', u'out_dir': u'/home/katie/Berkeley/', 'spatialite_enabled': False, u'gis_data_dir': u'/home/GISData/', 'spiderosm_test_data_dir': '/usr/local/lib/python2.7/dist-packages/spiderosm/test_data', 'postgis_enabled': True, u'postgis_port': 5432, u'postgis_user': u'postgres', u'postgis_password': u'tualatin', 'spiderosm_dir': '/usr/local/lib/python2.7/dist-packages/spiderosm'}

[mharnold]

Good point! OSM data is generally in lat-long, which only makes sense due to it's seamless world wide extent. So it makes sense to expect osm_ways, and osm_nodes to be in lat-long.

Path networks, including osm_pnwk are in planar coordinates since distances (in either feet or meters) are fundamental to the processing. The projection of OSM data from lon/lat to planar is currently done 'up front', but probably would make more sense to do this at the osm.geojson -> osm_pnwk.geojson step.

Thanks for pointing this out. I am currently expanding the documentation (and handling) of spatial reference systems in spiderosm. I'll be sure and at least document that osm.geojson and related database tables are in planar coordinates.