#554: wxGUI location wizard: Search in description with 0 hits
-----------------------------+----------------------------------------------
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Keywords: location wizard | Platform: MSWindows XP
Cpu: x86-32 |
-----------------------------+----------------------------------------------
Hi,
in the latest 6.4.0svn wingrass build from osgeo4w--
- startup with wxgui.
- Define new location via location wizard.
- by epsg code (list comes up now, great to see that fixed!)
- Search in description: ___ something with no hits, eg 4326 or typo
At this point the list of codes is empty and the following error message
appears on the DOS console window:
{{{
Traceback (most recent call last):
File
"C:\OSGeo4W\apps\grass\grass-6.4.0svn\etc\wxpython\gui_modules\location_wizard.py",
line 1365, in OnSearch
self.epsgcode = self.epsglist.Search(index=1, str=value)[0]
TypeError: 'NoneType' object is unsubscriptable
}}}
so I guess two things are needed:
- only try to grab epsg code to fill in "EPSG code: ____" box if >=1
result was found, and
- automatically reload EPSG codes before each new search (if 0 hits then
the 'search in desc' box is unusable until you press the Reload EPSG Codes
button.
#554: wxGUI location wizard: Search in description with 0 hits
---------------------------+------------------------------------------------
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Resolution: | Keywords: location wizard
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):
also in the location wizard, it would be really nice for lat/lon locations
if the "Set default region extent and resolution" would accept the
"DDD:MM:SS.SSSh" format. (swig G_scan_northing()?)
currently if you try that it gives an error: (e.g. for 48deg South lat)
"Invalid value: invalid literal for float(): 48S"
Replying to [ticket:554 hamish]:
> - Search in description: ___ something with no hits, eg 4326 or typo
you search in the description, not in the codes - so you get empty list.
Use "Reload EPGS codes" to reload the list.
> At this point the list of codes is empty and the following error message
appears on the DOS console window:
>
> {{{
> Traceback (most recent call last):
> File
"C:\OSGeo4W\apps\grass\grass-6.4.0svn\etc\wxpython\gui_modules\location_wizard.py",
line 1365, in OnSearch
> self.epsgcode = self.epsglist.Search(index=1, str=value)[0]
> TypeError: 'NoneType' object is unsubscriptable
> }}}
Fixed in r36775.
> so I guess two things are needed:
> - only try to grab epsg code to fill in "EPSG code: ____" box if >=1
result was found, and
> - automatically reload EPSG codes before each new search (if 0 hits then
the 'search in desc' box is unusable until you press the Reload EPSG Codes
button.
Replying to [comment:4 martinl]:
> Replying to [ticket:554 hamish]:
> > - Search in description: ___ something with no hits, eg 4326 or typo
>
> you search in the description, not in the codes - so you get empty list.
Use "Reload EPGS codes" to reload the list.
Could the search code be changed to also search in the EPSG codes? I get
regularly trapped that it isn't possible (often I want to search for a
code to see if I recalled the number correctly)
That would be great. FBK Trento promised to me to set up something like
this but I don't know if it will happen. Maybe we should install a
buildbot instance at OSGeo?
Replying to [comment:6 neteler]:
> Could the search code be changed to also search in the EPSG codes? I get
regularly trapped that it isn't possible (often I want to search for a
code to see if I recalled the number correctly)
>
> could we release also weekly updated native installer? - to enable users
to test recently fixed bugs?
>
I'm having some hardware issues right now (my laptop screen died). I'll
release another wingrass installer when I get this resolved. Sorry for the
inconvenience. However, the files and steps required (recently updated) to
make an installer are in the source code if someone else wants to give it
a try in the meantime.
-Colin