Hi Martin, Oliver, et al,
sorry I didn't find any time yet to write about it. But just a short
comment for the more advanced users:
assuming you have your TMS locally on your disk, you can just add a new
TMS with the url
file://home/me/Maps/mytms/%1/%2/%3.png
if you have many tiles, they will use lots of space on your disk
although the tiles are small.
you can zip all png in the deepest directory %2 creating a zip of that
name %2.zip in %1, where the filenames inside the zip look like %2/%3.png
I attach a shell script that should do the job.
if [ $# -ne 1 ]; then
echo "Argument repository name missing"
exit
fi
REPOSITORY=$HOME/Maps/$1
for i in `ls -1 $REPOSITORY`; do
# if [ "$i" -ne "14" ]; then
for j in `ls -1 $REPOSITORY/$i|grep -v zip`; do
echo "$REPOSITORY/$i/$j"
cd $REPOSITORY/$i
echo "zip -ur ${j}.zip ${j}/*"
zip -ur ${j}.zip ${j}/*
# echo "rc $?"
if [ "$?" -eq "0" ] || [ "$?" -eq "12" ] || [ "$?" -eq "13" ]; then
echo "rm -r $REPOSITORY/$i/$j"
rm -r $REPOSITORY/$i/$j
fi
cd ../..
done
# fi
done
Henrik
On 02/16/2012 09:47 PM, Oliver Eichler wrote:
> Hi Martin,
>
>
> what a list! :)
>
>>
>> Geo-referencing:
>> * Crosshairs instead of those pins when georeferencing.
>
> Ok, I think about it.
>
>> * Have the georeferencing points snap to pixels as used by gdal so
>> that one knows exactly where they'll end up.
>
> They do. They are placed exactly where your mouse points to. And this is
> the pixel. Of course if you overzoom one pixel is represented by several
> pixel.
>
>> * Allow the georeferencing points to be moved with the keyboard (e.g.
>> the arrow keys) rather than only dragged into place with the mouse.
>
> The intended work flow is a bit different. Usually I choose an overzoom
> of around 2. The point turns active (blue) if the mouse is near. As the
> point usually is very close to the final position it's sufficient to
> simply click on the grid crossing and the point jumps to that pixel.
> Then I use the 'n' key to move to the next point in the list. By that I
> can fine tune quite a large amount of points pretty fast.
>
>> * It would be a great feature if one could take a map from a set and
>> fine tune the georeferencing points if the maps don't fit together
>> properly.
>
> That's not as easy as it sounds. I tried to do similar with the fine
> tune tool. But it's not a real good approach.
>
>
> Besides, usually the maps match pretty well. If they don't I could boil
> it down to two reasons so far:
>
> 1. I was too sloppy placing the reference points. As I always save the
> points I can fix that.
>
> 2. The map has non linear distortions. Usually these are introduced by
> the scan process. Many reference points can heal these distortions a
> bit. But never completely.
>
>
>>
>> Interface aesthetics:
>> * Move Setup> General to Edit> Preferences?
>
> We had that one. Imho Edit->Preference is a design flaw. It's beyond any
> logic for me.
>
>
>> * Tool tips for the “M” and “T” headers in the maps list on the maps
>> tab. Not quite self-explanatory (Marked and Type?)
>
> Mode and type :) But you have a valid point here.
>
>> * Narrower tabs graphics.
>
> ???
>
>> * List the F-key shortcuts in the status bar when it's hidden in the
>> side-bar.
>
> The problem is that the statusbar is already too crowded for system with
> small screens. If you do not want the left hand menu, you either recall
> the F keys or use the menus.
>
>> * Scrap the Project Summary from the side-bar but add the option to
>> clear the project to the project window.
>
> No, I love that summary :) But you can close the splitter if you do not
> want to see it.
>
>> * Put up a graphic that shows when QLGT/GDAL is working/waiting.
>> Sometimes one isn't sure if it's doing something, has finished, is
>> hung or just ignoring some type of input.
>
> I guess that request is because of the hanging GUI when accessing WMS
> servers via GDAL API. I can not fix that because the call in the API
> blocks everything. However the next release will provide native WMS
> handling. Thus the GUI will stay responsive.
>
>>
>> Interface functionality:
>> * C-q to quit
>
> ok
>
>> * Optionally have the mouse scroll wheel pan, rather than zoom. With a
>> two axis touchpad that seems like a more useful behaviour.
>
> I hated that in MapSource. Imho Google conditioned everyone to use the
> wheel for zoom. If you have trouble to click and move on your touchpad
> you can keep the alt key pressed and move the map with the touchpad.
> This feature is a compile option. Thus you might need change it with
> ccmake and recompile.
>
>> * Make it possible to somehow center a point on the map (e.g. by
>> double-clicking) so that one can zoom in on that point ... and/or zoom
>> in on the point where the pointer is hovering.
>
> If you use the mouse wheel or the corresponding area on your touchpad,
> QLGT will zoom on the location the mouse pointer is pointing to. + and -
> will use the screen center. I will think about that double click.
>
>> * Add the option of keeping the same viewport when switching between
>> maps, as opposed to saving the view of each map. Helps when comparing
>> information between two raster maps.
>
> This is a bit complicated, as you never know if the next map covers the
> same area. And if not, what to do? And if the map after that covers the
> point again, how to behave?
>
> I solve that problem with a waypoint. With a double click on a waypoint
> the map centers the waypoint. By that I can make all maps to cover the
> same area.
>
>> * List both raster and vector maps in one window. Perhaps offer a few
>> ordering methods, such as map type, name and order of last use?
>
> That was the early behavior. Once you have a lot of maps you appreciate
> the separation.
>
>>
>> Track editor
>> * Handle NANs in GPS elevation data more gracefully. Currently the
>> altitudes seem to shoot off into the stratosphere on the profile
>> graph.
>
> If these are single points, the median filter will take care. If there
> are several nan in a row I mark these points in the track point list and
> hit the del key. By that the points are hidden, not delete. The del key
> is a toggle function. A right click will summon a context menu that
> offers the same functionality.
>
>>
>> Grid:
>> * Narrower gridlines (or with variable width) and adjustble distance
>> between lines.
>
> The problem is how to deal with that when the map is zoomed. Let's say
> you chose 500m. On zoom level 1 this is perfect. On zoom level 64 QLGT
> dies drawing lines.
>
>>
>> Streaming maps:
>> * Implement a map cache for easy downloading for offline use. Even
>> integrate that into the select sub-map feature so that TMS/WMS maps
>> get loaded into a cache or special map.
>
> Henrik added a similar feature last week. However he did not tell us
> sofar, how to use it.
>
>>
>> Live Log:
>> * Place the tip of the arrow at the position, rather than its middle.
>
> Hm, not sure if that is better in the sense of "everyone understands"
>
>> * Add the option to display a circle indicating the radius of the error.
>
> :) You are Garmin spoiled. The problem is that I do not have the
> information. The DOP is not the same as the stuff Garmin displays as
> error circle. In fact they dropped it for the newer units.
>
>>
>> Bugs:
>> * BUG: Crashes on starting LiveLog if gpsd is not running.
>
> ok, I'll have a look
>
>> * BUG: Sometimes zooming gets stuck at ca. 32x Zoom level. (seems to
>> be non-reproducable)
>
> Never had this one. What kind of map?
>
>
>> * BUG: When I press the "-" key on my keyboard, it behaves like a "+"
>> key. This seems to come from the fact that my keyboard layout has
>> redefined that key as "-" but QLGT seems to ignore the keysym, and
>> rather listen to the original keycode. Interestingly, the zoom keys
>> work properly in the 3D map.
>
> They do? This is the very same code for 3D and normal view. But your
> guess is right. Qt sees the key codes. It does not know about a
> different character binding.
>
>> * BUG: The georeferencing pins sometimes become ungrabbable (seems to
>> be when you do something else and they somehow aren't part of the
>> context any more)
>
> Yes that is a design flaw. You must not do anything else while
> referencing. There is no easy solution, else I would have fixed it since
> long.
>
>> * BUG: The diary icon still shows after deleting a diary from a
>> project. (QLGT crashed when I was playing around with adding and
>> deleting diaries).
>
> ok, I'll have a look
>
>> * BUG: In the database, when one adds an “other data” directory to a
>> project directory, the tick mark gets set and one can no longer toggle
>> it.
>
> I do that frequently with every new project. Never had a problem. Can
> you give more details?
>
>
> Hey here is the end! I made it :)
>
> Oliver
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Qlandkartegt-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
>
--
Henrik Schulz
E-08018 Barcelona, c/Almogavers 56 5o 3a
Phone +34 935 323 986
Mobile +34 693 463 361
mailto: [email protected]
http://asterix.000space.com
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
