Some more feedback:
The MaestroAPI.chm does list a MinScaleSpecified property for the
DrawingLayerDefintionType.
However when running the script in the console reports a non existing
attribute :
AttributeError: ‘DrawingLayerDefintionType’ object has no attributes
MinScaleSpecified
Also when
You are correct that a Drawing Layer has no vector scale range.
This is because min/max scale is a root property of a
DrawingLayerDefinition, so you python code is correct. But what you're
failing to do is to check is the property layer type of the ldf.SubLayer
property (as this could be a vector
Anyone?
Why is my MBtiles extract working perfectly in QGis (via GDAL),
but not in Mapguide OS?
Noone ever tried consuming MBtiles Data in Mapguide?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/MBtiles-via-GDAL-tp5178965p5183753.html
Sent from the MapGuide Users mailing
Well, after having used the python script console in Maestro, we were able to
update the Maxscale for those 300 dwf layers in bulk as opposed to a manual
way.While searching and testing we came with some questions or at least some
hints to our open question.I thought I would be interesting to at
These XSD files are set in stone. MapGuide and client applications are
working against these XSD files as they were originally written.
Nothing stops you from editing those files, but that doesn't mean that
MapGuide will respect the changes.
- Jackie
--
View this message in context:
James,
I think you have correctly found the culprit. I've read about individuals
editing the dbf portion of the shapefile (deleting records) without deleting
the feature and corrupting the idx file. The same is probably true in your
case where you have a record without the feature.
-Steve
If MapGuide tried to use the GEOS.dll from GISInterals, it cannot start. If
we use MapGuide's geos.dll the gdalplugins fail...
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/mapguide-2-6-MSVC-2012-Compiler-for-GDAL-tp5168554p5183806.html
Sent from the MapGuide Users
Gordon,
Yes It works using the interface to change the map unit to degrees. The
problem is when I set the ApplicationDefinition.xml to use degrres as
default. It does not work. Did it work in your environment, setting the
ApplicationDefinition.xml to degrees ?
Extension
I think I may have found the cause of the issue:
First, I was able to reproduce the .idx file corruption by selecting one of the
features in the layer created from the affected shp file. Then I toggled the
layer on and off until the .idx file was corrupted. Doing this without he
selection
Hi
I have tried to use the ScaleRangeUpdate example python script with Maestro.
Unfortunately this does not work for a DrawingLayer as it does not have a
vectorscalerange.
After a lot of trying I managed to find out that it is possible to call:
ldf.SubLayer.MinScale = min
So we added a new
Did you change anything on the wms user credentials?
I had a problem with AIMS2014, where i changed the standard
wms-user/password...
after that i couldn't connect anymore,and got the authentication box when
trying to connect...
--
View this message in context:
Hi GordonL,
Yes, it seems to require it to be registered even if you define the
Coordinate System with WKT code.
I use the WKT definition below, that if correctly implemented would define
EPSG:3763.
But MG OS simply ignores the EPSG code, when I try to reference it, for
instance on WMS, etc
Hi
We have tried to edit the XSD on the Maestro insttalation folder Schema, but
it seems to have no effect on the Maestro XML generation of a resource. At
least not for the LayerDefinition-1.0.0.xsd file.
We want to try to force the MinScale and MaxScale into the xml for a
drawingLayer.
Could
13 matches
Mail list logo
