[Gvsig_english] View Frame Properties of Map Buggy

Tue Jan 5 08:15:56 CET 2010

Hi,

Still going, not sure why...

I opened an old project that had one VIEW and one MAP. Removed grid and 
clicked on th pan tool. I then placed each window side by side.

If you pan in the MAP the VIEW adjusts. If you pan in the VIEW the MAP 
adjusts. If you return to the MAP and try to pan the image jumps to the 
previous position prior to the previous move and consequently so does 
the MAP. It appears that the register of moves in the MAP is not 
adjusted when the VIEW is moved.

This lack of changing values when moving various elements might account 
for the boomerang effect I have noted. It might also relate back to the 
grid disassociating itself from the image when zooming in the MAP View 
(as described in previous posts) - I am not sure if the grid is based on 
the VIEW or MAP data (which should be the same, but obviously at the 
moment is not).

Cheers Simon

Simon Cropper
Botanicus Australia Pty Ltd
PO Box 160, Sunshine, Victoria 3020.
P: 9311 5822. M: 041 830 3437.
mailto: scropper at botanicusaustralia.com.au 
<mailto:scropper at botanicusaustralia.com.au>
web: www.botanicusaustralia.com.au <http://www.botanicusaustralia.com.au>

On 5/01/2010 4:54 PM, Simon Cropper (Botanicus Australia Pty Ltd) wrote:
> Hi,
>
> Follow up on creating one VIEW for each MAP.
>
>    
>> :o Ahhhh...
>>      
> First issue: when double clicking a map view to change an option you
> need to respecify everything. So if you specify the VIEW to use and the
> scale option, then get in it to change a value the referenced view is
> set to the last in the list of views in the view scroll box. That is, if
> you have 15 views (like I now have) and you select View #1 to appear in
> the frame on the map, if you want to change the scale from "adjust
> automatically" to "maintain scale view" the referenced view is set to
> View #15 (last in list) rather than #1.
>
> Second Issue: Regardless of the scale option it is impossible to
> consistently pan the underlying view to the right location. It just
> boomerangs back to where it wants to go. Sooooo frustrating.
>
> Third Issue: The unnecessary duplication of one view and one map to 15
> views and 15 maps has resulted in a project file increasing from 339 KB
> to 2716 KB has resulted in unnecessary project bloat.
>
> Apart from patting my head, rubbing my stomach and hopping on one foot
> while adjusting the XML in the project file - I am at a loss. To date I
> have spent 3 whole days trying to get this program to work.
>
> Any help would be greatly appreciated.
>
> Cheers Simon
>
> Simon Cropper
> Botanicus Australia Pty Ltd
> PO Box 160, Sunshine, Victoria 3020.
> P: 9311 5822. M: 041 830 3437.
> mailto: scropper at botanicusaustralia.com.au
> <mailto:scropper at botanicusaustralia.com.au>
> web: www.botanicusaustralia.com.au<http://www.botanicusaustralia.com.au>
>
>
> On 5/01/2010 2:40 PM, Simon Cropper (Botanicus Australia Pty Ltd) wrote:
>    
>> Hi,
>>
>> Sorry for replying to myself but I appear to be the only one awake.
>>
>> Working through the process of establishing multiple maps (one for each
>> reserve) from a single VIEW, I have come to realize that with gvSIG
>> *there is actually a 1:1 relationship between between each VIEW and
>> MAP*. That is you can not have multiple MAPS to each VIEW _unless you
>> are happy to have all changes to the VIEW scale reflect in all the other
>> maps using that view_.
>>
>> I just finish setting up seven MAPS using the same VIEW (created by
>> importing a template) and adjusted each to show the particular section
>> of the VIEW where my reserves occurred. It looked OK but on saving and
>> entering the project any adjustments to any MAP VIEW in any map will
>> result in all MAP VIEW resetting to the current scale of the referenced
>> VIEW :-( .
>>
>> This leaves only one other option to my current scenario -- create a new
>> VIEW for each MAP. Not very satisfactory as if I change anything I need
>> to reiterate this change manually through multiple VIEWS and MAPS :'( .
>>
>> OK, just for clarity, so people know what I am doing and can possible
>> suggest workarounds before I throw gvSIG through the window...
>>
>> 1. I have shapefiles that show site boundaries (with labels), vegetation
>> (historic), vegetation (current) for 12 reserves. All data is present in
>> one shapefile (opened multiple times with different symbology). The
>> backdrop are ECW Images of the area.
>> 2. This VIEW is inserted into a map and a grid (100x100m) overlayed.
>> 3. A box is placed around the grid to make its presentation cleaner.
>> 4. Extent of MAP VIEW adjusted to show reserve #1.
>> 5. Need to print site boundaries (with labels), vegetation (historic)
>> and vegetation (current) -- by turning layers on and off in referenced VIEW.
>> 6. Need to show next reserve and repeat.
>> 7. If needed, I need to return to the same spot again for each reserve
>> in the future to reprint a map if an error is detected.
>>
>> The problem has been if I use just one MAP and pan then the problems
>> mentioned in the previous post occurs, if I make multiple MAPS for one
>> VIEW, the above problems occur. Now the only option is the cumbersome
>> situation of creating a separate VIEW for every MAP.
>>
>> Cheers Simon
>>
>> Simon Cropper
>> Botanicus Australia Pty Ltd
>> PO Box 160, Sunshine, Victoria 3020.
>> P: 9311 5822. M: 041 830 3437.
>> mailto: scropper at botanicusaustralia.com.au
>> <mailto:scropper at botanicusaustralia.com.au>
>> web: www.botanicusaustralia.com.au<http://www.botanicusaustralia.com.au>
>>
>>
>> On 5/01/2010 11:58 AM, Simon Cropper (Botanicus Australia Pty Ltd) wrote:
>>
>>      
>>> Hi,
>>>
>>> Sorry for the constant stream of issues but I am finding the more I use
>>> the map facility the more buggy it seems.
>>>
>>> After creation of a map template I find navigating within the map to
>>> orient the underlying view quite frustrating.
>>>
>>> BUGS
>>>
>>> Compared to other projects where a single view is established and just
>>> layers turned on and off in the reference view, this project requires to
>>> move to multiple areas at different scales and positions. I presumed I
>>> could set up a template and pan to a particular location and print the map.
>>>
>>> If I zoom to the open layers it does this as expected but once I am in
>>> around the 1:2000 to 1:10000 range all sorts of odd behaviour appears.
>>> One quite irritating behaviour is when a view gets stuck -- not quite at
>>> the right scale or location you use the zoom in, zoom out and map tools
>>> to try and change the location and the underlying layer just returns to
>>> the same location everytime. For example, to pan you drag the image away
>>> from the current location, release the mouse and the image immediately
>>> returns to the previous location. Using zoom out to see an entire site I
>>> select the reserve with the zoom in tool and you get a particular
>>> position, if you pan to make minor adjustments you have the above
>>> problem occur. If you zoom out then try again you get the same view
>>> configuration.
>>>
>>> I have experimented with various scale options "keep constant",
>>> "maintain view scale" and "adjust automatically" and the behaviour
>>> occurs in all options. I usually find that I get the best position quite
>>> by accident after 5-10 minutes of adjusting.
>>>
>>> Can people indicate how they would set up a project which have multiple
>>> reserves in one dataset and the need to produce multiple maps (various
>>> layers on/off) for each reserve? Create a single map for each reserve or
>>> section of reserve (my current thinking)?
>>>
>>> SUGGESTIONS
>>>
>>> I also had the thought that it would be good to have in the "Scale"
>>> section of the map options dialog the ability to zoom to a region of
>>> interest.
>>>
>>> The other valuable option, which seems plausible considering you have a
>>> dynamic view in a map, is to have various layers turned on and off. This
>>> would allow you to set up one map for historic vegetation or current
>>> vegetation or whatever (point map to one view and within the map options
>>> select various layers) and use the scale option to move the underlying
>>> view to particular areas -- this saves on creating multiple maps of what
>>> are essentially the same thing.
>>>
>>>
>>>
>>>        
>> _______________________________________________
>> Gvsig_internacional mailing list
>> Gvsig_internacional at listserv.gva.es
>> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>>
>>
>>
>>      
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>
>
>    