Opened 15 years ago
Closed 14 years ago
#2055 closed bug (invalid)
OSM plugin: incorrect BBOX values used on data download
| Reported by: | dankarran | Owned by: | wonder |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | |
| Component: | Python plugins and bindings | Version: | 1.3.0 |
| Keywords: | osm, crs | Cc: | |
| Must Fix for Release: | No | Platform: | OS X |
| Platform Version: | Awaiting user input: | no |
Description
If you open layers in QGIS that aren't in WGS84 (e.g. I tried with some GeoTIFFs in OSGB36) and then try to download data from OSM to overlay, the BBOX uses the coordinates from the original CRS not WGS84 as is needed. Can that be forced to use WGS84 to make sure it'll work with OSM?
Change History (3)
comment:1 by , 15 years ago
| Keywords: | osm crs added |
|---|
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|
comment:3 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
OSM plugin transforms the extent, but you have to enable projections to have it working. Because otherwise the plugin can't tell what's the reference system of the project and thus can't do the transformation.