Title: RE: [MI-L] RE: Labels

Arlene,

I'm not sure, what is causing your problem and if it is the same problem.

The problem I have encountered was that the labels were moved approx. 300 meters. This matched exactly the difference between coordinates in two often used coordinatesystems in Denmark.

The problem was that when the workspace was written the coordinates were written using the first coordinatesystem. But when the workspace was reloaded, the coordinates were interpretered using the second coordinatesystem.

If you look at a workspace in a text editor, you'll see that when MapInfo creates a map, it involved a number of statements:

1. Create the Map with the layers.
Map From <list_of_layers> ...

2. Set coordinatesystem, center and zoom
Set Map
        CoordSys ...

3. Setup the layers
Set Map
        Layer 1 ...
        Layer 2
        Layer ...

If you add a print statement, that prints the current coordinatesystem of the map after the first Set Map and after the second Set Map, you can see if MapInfo is using different coordinateystems. The print statement is this: Print MapperInfo(FrontWindow(), 18)

Here is a short sample:

******************************************************************************************
...
Set Map
  CoordSys Earth Projection 8, 28, "m", 9, 0, 0.9996, 500000, 0
  Center (537837.6939,6152324.979)
  Zoom 27.81736419 Units "km"
  Preserve Zoom Display Zoom
  Distance Units "km" Area Units "sq km" XY Units "m"
  Distance Type Cartesian
Print MapperInfo(FrontWindow(), 18)
Set Map
  Layer 1
    Display Global
    Global   Symbol (34,16711680,12)  Line (2,2,16711680)  Font ("Tahoma",257,9,0,16777215)
    Label Line Arrow Position Above Font ("Arial",0,9,0) Pen (1,2,0)
      With VEJNAVN
      Parallel On Auto Off Overlap Off Duplicates Off Offset 2
      Visibility On
  Layer 2
    Display Graphic
    Global   Symbol (34,16711680,12)  Line (2,2,255)  Font ("Tahoma",257,9,0,16777215)
    Label Line Arrow Position Above Font ("Arial",0,9,0) Pen (1,2,0)
      With VEJNAVN
      Parallel On Auto Off Overlap Off Duplicates Off Offset 2
      Visibility On
Print MapperInfo(FrontWindow(), 18)
Set Window FrontWindow() Printer
 Name "\\BDCODKX\ODKX13" Orientation Portrait Copies 1
 Papersize 9
...
******************************************************************************************

Peter Horsbøll Møller
GIS Developer, MTM
Geographical Information & IT
 
COWI A/S
Odensevej 95
DK-5260 Odense S.
Denmark
 
Tel     +45 6311 4900
Direct  +45 6311 4908
Mob     +45 5156 1045
Fax     +45 6311 4949
E-mail  [EMAIL PROTECTED]
http://www.cowi.dk/gis

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Arlene Baker

Sent: Monday, June 19, 2006 7:44 PM
To: [email protected]
Subject: [MI-L] RE: Labels

Hi,

I've also had this problem and it wasn't caused by packing -- the arrows from the labels point to the correct points (correct label with correct point) and I haven't packed the table.  Not sure if it is caused by coordsys difference.  The labels aren't really in the wrong place -- the lines/arrows pointing from the label to the point are hundreds of miles long (I've had one go almost to South America when the point was in Central Florida).  For example, I have a map layer with an extent of 20 miles and have a few labels pulled off some points, maybe 1/2 a mile from the point -- just enough so it is readable in my layout window.  I re-open the saved workspace and those labels are now hundreds of miles away from their points.  If it was a coordsys problem, should I expect the difference to be the distance between a point in one coordsys and the same point in another system?  Or is the coordsys difference just causing the labels & lines to "fly" all over the place?

Arlene

Arlene Baker
The Shopping Center Group
2170 W. State Road 434
Suite 180
Longwood, FL  32779
Phone:  407-788-8818
Fax:  407-788-0971
www.theshoppingcentergroup.com
 
Confidentiality Note: The information contained in this email and document(s) attached are for the exclusive use of the addressee and may contain confidential, privileged and non-disclosable information. If the recipient of this email is not the addressee, such recipient is strictly prohibited from reading, photocopying, distributing or other wise using this email or its contents in any way and must immediately delete this email.


----------------------------------------------------------------------

Message: 1
Date: Sat, 17 Jun 2006 22:50:05 +0200
From: Peter Horsb?ll M?ller <[EMAIL PROTECTED]>
Subject: RE: [MI-L] Labels
To: "David Hilpipre" <[EMAIL PROTECTED]>,     "Anthony Hicke"
        <[EMAIL PROTECTED]>,    "Mapinfo-L"
        <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

Hi,
 
Just wanted to share some insight on this issue.
 
This problem is not only related to packed tables. I can slo be related to raster layers ...
 
Imagine this:
1. You have a map with a bunch of layers and a raster layer. Thie raster layer is not visible, but in a different coordsys 2. You save a workspace with the current view of the map, the coordsys is not the same as the raster layer

 
3. You reopen the workspace. Now it gets technical:
3a. When a map is created thru a workspace MapInfo starts by adding all the layers 3b When it has added the layers, the map window has the coordsys of the raster layer 3c. Now the settings for the layers are applied, and also the costum labels - coordinates are not using the coordsys of the raster layer 3d. Finally the settings for the raster layer, se the zoom level and turns off the raster layers visibility

 
4d. Now the labels turn up in incorrect positions.
 
Did you notice the problem ?
 
The problem is that when saving the workspace, the coordsys is not the same as when reloading the workspace again. This might interfer with the position of the labels - and I guess also with cosmetic objects !?

 
So, be aware when using raster layers in a different coordys then the rest of you layers. BTW, this might be solved with MapInfo 8.5 as you here can reproject raster layers.

Peter Horsbøll Møller
GIS Developer, MTM
Geographical Information & IT
 
COWI A/S
Odensevej 95
DK-5260 Odense S.
Denmark
 
Tel     +45 6311 4900
Direct  +45 6311 4908
Mob     +45 5156 1045
Fax     +45 6311 4949
E-mail  [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> http://www.cowi.dk/gis

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of David Hilpipre

Sent: Friday, June 16, 2006 6:11 PM
To: Anthony Hicke; Mapinfo-L
Subject: RE: [MI-L] Labels

Hi
 
Usually, it happens only on labels that have been moved to some other locations by the user (so there is a line in the wor for this specific label where you find the new location of that label and the row id of the table to which it corresponds) AND only if the table has been packed AFTER labelling (cause when you pack a table, rowid changes, at least the ones that are located after the greyed records).

In this case, the wor you're using is not up to date with the table : some labels in the wor are still pointing to a let's say 3rd row in the table, but that 3rd is not the same object as it used to be...cause the table has been packed inbetween

 
Don't know if it make sense to you. It's even a pain to explain in french, so imagine in english !!!
 
David
________________________________

De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Anthony Hicke

Envoyé : vendredi 16 juin 2006 17:26
À : [email protected]
Objet : [MI-L] Labels

Hello,

I am using Mapinfo Professional 7.0.  Occasionally, when opening a workspace created ion the past, the labels "streak across the page;"  that is, labels no longer are located where they should be , but have moved far to the southwest, with their connecting lines stretched from the point map location to the newly moved label.  To fix this, I can click "remove custom labels" andf auto label, but then I lose my custom labeling of course.  Normally, I click on each labeled data point with the auto-label tool to fix this, but my most recent map is very large, and clicking each data point iss very time consuming.  I've searched the Mapinfo knowledge base for a bug fix, but had no success.  FYI, this also happened when using Mapinfo 6.0.   Also, this problem does not happen consistently.  Any Ideas?

_______________________________

Anthony Hicke, PG, CHG
Project Groundwater Geologist
Richard C. Slade & Associates LLC
818.506.0418  North Hollywood
707.963.3914  St. Helena
818.506.1343  Fax

PLEASE NOTE:  The information in this email is privileged, confidential and protected from disclosure.  If you have received this email in error or are not the intended recipient, you may not use, copy or disclose this message or any information contained in it to anyone.  Please notify the sender by reply email and destroy the message.  Thank you.

 

_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l



_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l

Reply via email to