Please don't hijack other threads, create a new thread if you need to ask a
question that is not related to this thread.
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/FDO-OGR-provider-stops-working-with-many-layers-tp4358864p4670732.html
Sent from the MapGuide Users
Hi jackie
Adding to the exclude list, does solve the problem, but the benefits (I
assume there must be) of having the connection pools are lost.
What I did instead was to add to the: DataConnectionPoolSizeCustom =
OSGeo.OGR:50
It seems that the somewhere in the system is an upper limit of open
Have you tried manually modifying the measurement Tool task pane code behind
template file to hard code it to always use feet or convert your measurements
so the output becomes feet.
Then you can keep your projection in whatever you want for DD coordinates to
appear in the taskbar.
I think
I am now facing the same issue when trying to migrate to 2.2
If the feature source has already been configued in say 2.1 or MGE2010 it
all works fine.
On a new feature source, the tables preview properly if you don't have the
geometry specified. However, as soon as you define the geometry
