[mapguide-users] Re: FeatureSource has a different coordinate
system than the map
Lotte Doyle
doylelotte at gmail.com
Fri Mar 2 14:10:53 EST 2012
When you said to generalize data, did you mean to build a sort of
pyramid like one does for raster? Could it be done through Maestro, or
elsewhere before I import the data into MG?
The feedback is definitely faster at a larger scale, but I'm still
worried about the background processing... If you could refer to this
screenshot: http://i.imgur.com/AEE90.png
1. when the map app was first loaded and rendered. Blank map during wait.
2. when I entered the 1:5000 scale to zoom towards. Blank map during wait.
3. when I zoomed out a bit to find my river. Blank map during wait.
4. when I was back at 1:5000 scale and panned along the feature. It
was only at this stage that the app was able to render the features
immediately, allowing me to make a series of quick pans. However,
after I finished, it took up CPU resources for quite awhile longer
before settling down.
I have a feeling those wait times will be a deterrent for some people.
I'm testing out the software on a Windows desktop PC. Would I expect
better performance on a Linux server? My grand scheme is to have the
map+web servers running on a Linux server, while Maestro usage and
creating Fusion layouts are done on Windows desktops.
Much thanks.
On Fri, Feb 24, 2012 at 23:31, Zac Spitzer <zac.spitzer at gmail.com> wrote:
> it all depends on your data
>
> rivers are often supplied with low level accuracy, if you are viewing
> them at a high scale mapguide needs to read all the data and then
> scale it to make it visible. i.e. lots of processing
>
> you may need to generalize your data for different view scales
>
> how does it go at lower scales like 1:5000 ?
>
> On Sat, Feb 25, 2012 at 9:38 AM, Lotte Doyle <doylelotte at gmail.com> wrote:
>> Ahh, this did the trick! I usually go for stable builds and thought 2.1 was the latest from what was listed on the Downloads page.
>>
>> I'm still monitoring the cpu load and see that it still takes quite a lot of processing power for every map UI action, though the maps no longer freeze. Is this normal?
>>
>>
>> On 2012-02-17 14:56, Zac Spitzer wrote:
>>
>>> 2.1 is an old release, 2.2 is much more stable
>>>
>>> http://trac.osgeo.org/mapguide/wiki/Release/2.2/Notes#Installation
>>>
>>
>> _______________________________________________
>> mapguide-users mailing list
>> mapguide-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
>
>
> --
> Zac Spitzer
> Solution Architect / Director
> Ennoble Consultancy Australia
> http://www.ennoble.com.au
> http://zacster.blogspot.com
> +61 405 847 168
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
More information about the mapguide-users
mailing list