This seems to become general "ideas about QMS" thread. So let me add some of my ideas after using QMS under "production" conditions for some time. The overall impression is excellent. You no longer need to go forth and back through overlays when you want to add some points to a track. Managing map views with multiple layers is really powerful and easy to control. Great!
What is still confusing me, although I well understand the principle, is the way databases and the workspace are managed, I mean the need to put a copy of a database item to the workspace in order to access it. To save a track from a db to a gpx file, one has to add the track to the workspace and then copy it to a GIS project. The same procedure the other way round to import a gpx track to the db. What is most confusing for me is that the database folder hierarchy is not visible in the workspace. Group folders, which mainly serve to structure data, can not even been shown in the workspace and other folders are all shown on the same level. I would have preferred to have no database window but databases be treated in the same way as GIS files: add a db to the workspace, show/hide db items on the map by checking/unchecking the checkbox, update the whole database or selected items. However, I understand that the workspace / database solution has been chosen for good reasons and I do not propose to change it. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
