Opened 11 years ago
Closed 10 years ago
#1872 closed defect (fixed)
r.in.wms doesn't work on Windows
| Reported by: | martinl | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 7.0.0 |
| Component: | Raster | Version: | svn-trunk |
| Keywords: | r.in.wms | Cc: | |
| CPU: | Unspecified | Platform: | MSWindows 2K |
Description
Using latest WinGRASS 7 (OSGeo4w) r.in.wms refuse to work.
r.in.wms url=http://irs.gis-lab.info layers=osm output=osm format=png ERROR: Unable to determine region, m.proj failed
Change History (9)
comment:1 by , 11 years ago
| Version: | unspecified → svn-trunk |
|---|
follow-up: 4 comment:2 by , 11 years ago
comment:3 by , 11 years ago
it is worth re-testing since the script called from within another script winggrass bug was recently fixed. that was for .bat wrappers in grass6 though, so may not apply to trunk.
also for locations using a grid file for the datum transform note the bug that there is no way to pass the path to a NTv2 grid filename to cs2cs if the path has a space in it, which can cause m.proj to fail. we should probably submit a quoting patch to proj4 to get that eventually fixed.
... and a reminder that r.in.wms2.py does not run from grass6 addons, still needs more porting work done on it.
Hamish
comment:4 by , 11 years ago
| Priority: | critical → major |
|---|
Replying to neteler:
Is this still the case (I also wonder why a single WMS module can have a "critical" level)?
I agree. Downgrading to major.
Moritz
comment:6 by , 11 years ago
I have not tested script-within-a-script in WinGrass7 or r.in.wms.py there to see if m.proj is working with/without a NTv2 grid file, but afaik issues as discussed in comment:3 remain.
regards, Hamish
comment:7 by , 10 years ago
In order to keep this ticket focused:
Note that script-within-a-scrip for standalone WinGRASS trunk is subject of #2150 but a workaround is now applied. If this was the cause, r.in.wms should work now.
Note also that whether m.proj is working with/without a NTv2 grid file can test only somebody who understands what it is (e.g. I cannot not). Is this MS Windows specific as this ticket is? Is this what the message suggests? Perhaps the message should be changed to give more details.
For GRASS 6, there is a separate ticket for r.in.wms2, #2010 and ticket #820 for r.in.wms.
comment:9 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Is this still the case (I also wonder why a single WMS module can have a "critical" level)?