Symbolization in Map Manager distorts point data

Hello!

Thank you to report that unexpected beahvior on this Forum.

Lot of factors can explain this behavior. We need to ask you more precisions, beginning with:

• Do you have any rotation in the view (both models)?
• Do you assign any Coordinate Systems?
• Do you change any setting in Reference dialog (as rotation)?
• Do both files have the same global origin?
• Does orientation change right after opening of Map Manager or after the application of symbolization?

 Please, be specific on settings of both models (files) involved and on steps by steps workflows used.

Thank you and Regards,

Sebastien

Thanks for your answer.

There are no assigned rotations. The map model is derived from the default model through the simple expediant of opening the map manager and applying symbology.

No rotation settings were made in the reference dialog box.

I don't know how Map Manager generates the map model... I assume they have the same global origin.

The orientation occurs at the application of symbolization.

Specifically: The seedfile is set with a standard NY State Plane projection.  The data points are queried into a newfile created from the seedfile. The data points are stored in an Oracle Database with a NY State Plane projection.

Map Manager was opened and symbolization created. The symbolization modifies the color and scale of the cell used to represent the point data based on the where clause. Rotation is not changed.

One where condition changes the scale of the feature by 1/2 (from 16 (nominal) to 8).

THe status window reads as follows.

Display complete

No Reference file index: Seamless mapping will not be active

GEOMAPMAN is already loaded.

No elements found

Query Complete (490 features in 2.792 seconds)

GDIEXPLORER is already loaded.

culvert_points - Line : Native Feature : culvert_points, Level: culvert_points, Ref: 1 (culvert_points.shp)

Feature classes that include RDBMS properties will not be available for edit since database connection was cancelled.

Feature classes that include RDBMS properties will not be available for edit since database connection was cancelled.

Replaced missing TrueType font [SAPDings] with [Arial].

Replaced missing TrueType font [Teen] with [Arial].

Replaced missing SHX font [STANDARD] with [msdefault.kanjibig].

GCSDIALOG loaded.

Raster Snap = OFF

Initializing...

Compiled Apr  9 2011 : 01:11:17

MAPENTERPRISE loaded.

FMEDATAEXCHANGE loaded.

DATAEXCHANGE loaded.

Hope this tells you something

THanks

Doug Osborne

Hello,

That sounds very strange to me that the orientation/scale changing by only applies symbology. Let me summarize your workflow. Please correct me if I’m wrong:

Steps to reproduce:

1. Create a new file you seed file (with NY State Plane CS)
2. Querying data from Oracle Spatial to default model
3. Launch Map Manager
4. Create a Map Model
5. Attach actual model
6. Create a Thematic Symbology on queried feature
7. Data are upside-down
8. Correct? Please correct where I’m wrong.

Do you use a specific schema where you defined user workspaces?

Which user workspace do you use?

How do you connect to Oracle Spatial?

Connection defined in Schema as registered connection?

Or Ad hoc connection?

In your copy of Message Center, it has two messages I do not understand where they from:

culvert_points - Line: Native Feature: culvert_points, Level: culvert_points, Ref: 1 (culvert_points.shp)

Where from that shapefile?

Feature classes that include RDBMS properties will not be available for edit since database connection was cancelled.

Did you have RDBMS feature in your seed file?

We will need you data to be able to reproduce on our side. It should be good if you could provide a video screen capture of workflow, but also your seed file and the workspace used (custom schema as .xml file).

You can use my email (click on my name) or by ftp if files are too big. We will give your case to investigation team to try to explain that weird behavior.

Thank you.

The workflow you listed is generally correct except I do not attach any files to the Map Manager. That is done automatically.

The Oracle connection is defined in the xml file since this is the only way into the spatial data (geometry and tabular information).

I'm going to go through the data and reverify the steps just in case I misrepresented something, I'll provide the documentation etcetera as requested, as soon as I can.

Thanks.

I finally receive your email. Soon as possible, I will refer to the right

person (or I will check it) and let you know about it.

Best regards,