Opened 13 years ago
Closed 13 years ago
#1805 closed defect (fixed)
Put back 900913 srid
| Reported by: | robe | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.1 |
| Component: | postgis | Version: | 2.0.x |
| Keywords: | Cc: |
Description
I'm not sure when we did this, but I assume its intentional that we removed 900913 from spatial_ref_sys. Or was it something we added in 1.5 but didn't up port to 2.0?
Anyrate I see no mention of it in the docs (unless I am blind, which I might be) and of course it breaks a lot of OSM applications. Mine included which is the only reason I noticed it.
Change History (3)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Component: | build/upgrade/install → postgis |
|---|---|
| Owner: | changed from to |
| Summary: | document removal of 900913 from spatial_ref_sys and add to legacy → Put back 900913 srid |
I think Fricking terrible is a bit of an over dramatization 
. So I guess this means you want to put 900913 back.
Note:
See TracTickets
for help on using tickets.
Absolutely not intentional, it must have gotten wiped when the new spatial_ref_sys was generated from GDAL. Fricking terrible, I guess nobody really does test these things… maybe not until the 0.1 releases now.