Opened 14 years ago
Closed 14 years ago
#320 closed defect (fixed)
parse and use mapSearch layers setting
Reported by: | landry | Owned by: | josegar74 |
---|---|---|---|
Priority: | major | Milestone: | v2.6.0 |
Component: | Web Map Viewer | Version: | v2.6.0 |
Keywords: | openlayers | Cc: |
Description
So far, config-gui.xml only permits to set projection/extent for the main map viewer/search map, it'd be nice if resolutions array/units could be configured there too instead of being hardcoded to 'degree + autofill scale array'. As of now (i don't work in WGS84, nor on the whole world extent), i have to manually hack units:'m' and the scales/resolution array in the gn.libs.map.js file.
As a side note, it looks to me that gn.libs.map.js is built from some of the scripts/ol*.js files, but how so, and which ones ? it's not listed in scripts/full.cfg, and i'd like to do modifications on the original files when debugging - that supposes the include lines in xsl/main-page.xsl has to be modified too..
Change History (8)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
1) For debug you can add in URL debug=true parameter, using then the non compressed javascript files.
2) About full.cfg file, is not really used since the change to maven. Now is used yuicompressor-maven-plugin (see web/pom.xml)
3) You can specify in config-gui.xml the resolutions for layers and other options/parameters. For example:
<layer server="http://localhost:8080/geoserver/wms" tocName="Borders" params="{layers: 'gn:gboundaries', transparent: 'true', format: 'image/png'}" options="{}" />
you can setup this in "options" as you do in OL.
4) I'll check about the typo. Thanks for reporting
comment:3 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Duh. stupid me. Of course i'll set it up in options hash.. marking the issue as invalid then. Thanks for the info and your work in the ol/mapfish integration!
comment:4 by , 14 years ago
Thanks for reporting.
If you get any issue working with the options/params hash, reopen the issue, please
comment:5 by , 14 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Summary: | allow resolutions/units to be configurable in config-gui.xml → parse and use mapSearch layers setting |
Hmm.. i still have a little related issue (hence changing summary)
in xsl/main-page.xsl, when initializing minimaps in initMapsSearch, the AdvancedSearch.init() call isn't given mapOptions as last parameter. This is needed to apply user-specified params.
secondly, backgroundLayers is used for all three maps, and config/mapSearch/layers/layer config key is unused. i think xsl/geo/utils.xsl should have a second section to parse it, and use the corresponding layer config where appropriate.
Attached diff fixes both small problems.
comment:6 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
comment:7 by , 14 years ago
Status: | new → assigned |
---|
comment:8 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Search maps:
1) Updated to pass map options hash to both map searches. 2) Use by default the layers defined in mapSearch/layers section of config-gui.xml. If not defined uses the layers defined in mapViewer/layers
Oh, and there's a typo in ol_minimap.js line 46 introduced in r6302: constrols vs controls