MapGuide Enterprise Wishes (Read Only)
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Studio should be smarter with creating layers from SDF sources

4 REPLIES 4
Reply
Message 1 of 5
jumpinjackie
588 Views, 4 Replies

Studio should be smarter with creating layers from SDF sources

Because SDF can store multiple geometry types, when I create a new layer from a SDF feature source, the new layer will have all 3 geometry styles, even if the SDF only has one type of geometry.

The only time a layer from a SDF feature source has a single geometry type style is if it was converted from a different format (eg. SHP)

Studio should be smarter about this, it should figure out that there's only polygons in it and so if I create a new layer from it. It will only have polygon styles. Not all 3 together!

Currently, the only way to change this is to manually edit out the useless styles in the layer document. And that is a time consuming process.

- Jackie
http://themapguyde.blogspot.com
http://au.linkedin.com/in/jackieng
4 REPLIES 4
Message 2 of 5
Anonymous
in reply to: jumpinjackie

jackie.ng wrote:
> Because SDF can store multiple geometry types, when I create a new layer from a SDF feature source, the new layer will have all 3 geometry styles, even if the SDF only has one type of geometry.

That's not necessarily true. SDF files contain a schema which, among
other things, defines what kinds of geometry types are allowed in each
geometry column. If you create an SDF class that limits the geometry
column to a specific geometry type, then only that type will be
displayed in Studio.

How are you creating the SDF files?

I found this to be a problem with FME2006, because it did not allow you
to set the geometry type, but FME2007 does (you need to replace your
destination data sets).

Also, fdo2fdo allows you to do schema re-mapping, which I'm pretty sure
includes changing the allowed geometry types.

Jason
Message 3 of 5
dhequet
in reply to: jumpinjackie

Even if it can be defined in SDF, this problem remains when you use other kind of datas:
IE: the new "Oracle foreign datastore" feature in AMGE 2008 doesnt know what kind of geometry you have in the tables. the layer will have all 3 geometry style. The only method to prevent this is to export your layer as xml, the import it whit mapagent. That is not user friendly.
Can't you add a checkbox or somewhat that can limit geometry style used on a layer on the creation?
Message 4 of 5
jumpinjackie
in reply to: jumpinjackie

The SDFs were created from Map3D 2008.

Hmmm, on second thought this could be more of a Map3D problem, as it always produces an SDF with all 3 geometry types.

And Studio is just simply interpeting that.

This wish was probably for the wrong product XD

- Jackie
http://themapguyde.blogspot.com
http://au.linkedin.com/in/jackieng
Message 5 of 5
Anonymous
in reply to: jumpinjackie

dhequet wrote:
> Even if it can be defined in SDF, this problem remains when you use other kind of datas:
> IE: the new "Oracle foreign datastore" feature in AMGE 2008 doesnt know what kind of geometry you have in the tables. the layer will have all 3 geometry style. The only method to prevent this is to export your layer as xml, the import it whit mapagent. That is not user friendly.
> Can't you add a checkbox or somewhat that can limit geometry style used on a layer on the creation?

I agree that it would be useful to allow the users to select which
geometry types to use for data sources that contain more than one
geometry type (or which only contain one but aren't smart about exposing
it). I'd like to see all stylization options presented with, as you
say, checkboxes next to each to enable/disable them.

Jason

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report