-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSM Import Cannot find SRID (4326) in spatial_ref_sys #5
Comments
It looks like this has probably been broken since osm2pgsql-dev/osm2pgsql@b2a9f72 which added 4326 as a requirement. There are two options at the moment:
This inserts all the SRS's. The truncate is required as 900913 has been in spatial_ref_sys.sql since PostGIS r12623 which means you will get duplicate key errors due to the insert called by createdb. Alternatively, you can copy the required 4326 entry from spatial_ref_sys.sql and insert that by itself. Happy to put in a pull request for either fix. Possibly sourcing all of spatial_ref_sys.sql (and remove the 900913 entry from run.sh) is the easiest and most fool/future proof rather than adding an individual SRS. |
I ended up using a different container: |
the result of your fixes
|
i use this files : https://raw.githubusercontent.com/postgis/postgis/svn-origin/svn-2.1/spatial_ref_sys.sql otherwise the 900913.sql you have all ref (900913 and 4326) and its works for me osm2pgsql SVN version 0.89.0-dev (64bit id space) Using built-in tag processing pipeline
|
@kwauchope shouldn't this:
be:
|
Solution implemented in PR #10 works! Why not yet merged? |
When importing an OSM file (Minnesota) I am receiving the following error after the "Relation" step and most other steps complete:
Is there a way to populate that spatial_ref_sys table? Thanks.
The text was updated successfully, but these errors were encountered: