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 downloader error #894
Comments
I have swapped over to the master and did not sync so am working on 269abc9- 27Feb (very shameful I know) but its working, so I think the changes that have been made recently to the downloader has created this error |
Kristy, that is related to Linfiniti server, I also got that error cc: @timlinux On Wed, Mar 19, 2014 at 8:34 AM, Kristy Van Putten <notifications@github.com
------------------- Akbar Gumbira Software Engineer - Risk and Vulnerability Team Australia-Indonesia Facility for Disaster Reduction (AIFDR) ----------------------------------------------------------------------------------------- Menara Thamrin, Jakarta E | akbargumbira@gmail.com M | +62 856 24545876 |
Hi I am looking... Regards Tim On Wed, Mar 19, 2014 at 4:54 AM, Akbar Gumbira notifications@github.comwrote:
Tim SuttonVisit http://linfiniti.com to find out about:
|
@akbargumbira it is the server giving an error, but its because we are passing in an invalid extents (it should be in geographics coordinates). @vanpuk what CRS are you using and is on the fly projection working? |
@timlinux: I never looked at osm.linfiniti.com to see how it handles the request. Should there be some validations regarding bbox parameter? And then we can inform the user from OSM downloader tools if that is the case |
@timlinux: I think it hits this one https://github.com/timlinux/osm-reporter/blob/master/reporter/views.py#L136 .. or this one https://github.com/timlinux/osm-reporter/blob/master/reporter/views.py#L142 |
@akbargumbira That code is all behaving correctly - the problem is that the bbox is being passed in EPSG:3857 instead of geo coordinates. |
@timlinux: yeah I see. I can replicate it (change the CRS to EPSG:3857) so, shall we handle it on OSM downloader tools itself? Just give user the warning that it should be in geo coordinates? or convert all kind of the projection to geo coordinates? or handle it in osm reporter? |
There is already logic for doing the conversion in place - its just not being called or it is returning the incorrect result. Leave this one to me, I will look at it, thanks! |
@vanpuk can you confirm which CRS you were using? |
…valid expected results and test_utilities has a green dot.
I've written some tests to replicate. So it seems this error is specific to QGIS 2.0. Can you confirm that you are using QGIS 2.0 vanpuk? A temporary work around would be to ensure your project is in EPSG:4326. When I find the pronlem I will hotfix and make a bugfix release. |
…n env to use qgis 2.0
@vanpuk from my testing here it seems to replicate if I use EPSG:900913 in the unit tests, but if I switch to EPSG:3857 (the more 'official' google projection now) the problem does not occur. So could you provide a little more detail:
Thanks |
…n env to use qgis 2.0
@vanpuk can you provide the details that Tim asked here? Thanks |
I'll look at this for 2.2 |
@Gustry Can you look into this and close if you can't replicate. Please test when your project is using projected CRS. |
I can't replicate it. |
Problem
Error Received on Mac - InaSAFE 2.0.4
Solution
Fix error???
The text was updated successfully, but these errors were encountered: