Has anybody else encountered the following error when trying to open
files in the new version of MapInfo Pro?
ncsecwmie.dll
it appears as you try to load up layers or workspaces. Does anyone know
of a patch which has been created for this?
I have checked the program files and the file is there, just the
software is not reading it. Ay help would be appreciated.
Yours,
Mark.
markbutcher a écrit :
The problem is with MapImagery. It happens when you uninstall and then
reinstall MapInfo without uninstalling MapImagery such as when you
upgrade to v8.5. There is a new version of MapImagery on their web
site. Download it and install it. That solves the problem.
Abu Geo
I know that you can edit the linestyles using the linestyle editor, but
what
is the maximum number that can be added without touching the existing
linestyles included by default?
Regards,
Nick Lawrence
************************************************************
Opinions contained in this e-mail do not necessarily reflect
the opinions of the Queensland Department of Main Roads,
Queensland Transport or Maritime Safety Queensland, or
endorsed organisations utilising the same infrastructure.
If you have received this electronic mail message in error,
please immediately notify the sender and delete the message
from your computer.
************************************************************
You can have 255 line styles. This is because a single byte is used as a
pointer into a lookup table in the MAP file, and a single byte can only have
256 combinations. Take out the null option and you are left with 255.
Regards
Bob
From: | "Bob Young" <b...@mapsbydesign.co.uk> on 11/29/2006 09:40 AM GMT |
To: | <mapi...@googlegroups.com> |
cc: | |
Subject: | [MI-L] Re: Maximum number of linestyles in MapInfo 8.5? |
mapi...@googlegroups.com wrote on 30/11/2006 03:06:01 AM:
> You can effectively have 127 line styles. As Bob notes below, the size
of
> the field used to store the line style is a byte. But the uppermost bit
> of that byte is reserved to indicate interleaved line style display. So
> technically styles 1 and 128 are the same style, except one will be
> displayed interleaved (128) and the other will not (1). This scheme
does
> waste some space, as not all line styles are interleaveable. But this is
> the scheme currently in use.
> So the correct answer is 127 line styles can be defined.
> Derek Snyder
> MapInfo Corporation
In my work area, there are a lot of CAD designers, as well as
GIS operators.
One of the common tasks is to take a CAD drawing, and import it
into MapInfo.
The problem is, CAD has many different linestyles, all with particular
meanings. The only way to bring all those linestyles into MapInfo is
to delete most of the existing MapInfo linestyles. This means that
if we open an ordinary MapInfo table from a different MapInfo user,
the linestyles are all wrong.
If the maximum limit of linestyles was increased significantly, we
could fit all the extra linestyles from the CAD programs, without
deleting any of the default MapInfo linestyles.
There are literally thousands of available point symbols (256
per font). Can't we have the same number of possible linestyles?
As well as the difference in the number of linestyles there is a fundamental
difference in the way the lines are drawn ( or rendered). When MapInfo
"renders" its lines, it uses a "raster" pattern to render the line. Whatever
zoom level you are at the "raster" pattern is the same. You can apply a line
scale of sorts but relative to CAD this is less subtle. You are applying a
"chunk factor" of 1 to 7 and the whole bit pattern is increased by the
applied factor.
In packages like AutoCAD line styles are defined as, and then rendered as
vector (rather than raster) styles. This ulimately gives you much more
control. You also have an option to make the line appear the same
independant of scale, but more usefully you can make the lines dashes and
gaps zoom as you zoom in on the drawing.
Interestingly for MapInfo to adopt these changes they would not need to
change the format. They would need to change how the lines are defined and
how they are rendered.
If you are needing read only access in your MapInfo view of the CAD drawings
you could convert the objects at "translation" time. So a single line, or
polyline gets converted to multiple lines. I have done this in the past and
achieved a MapInfo Map that looks identical to a CAD drawing. I have also
done this with text. AutoCADs original text ( before support of true type )
is defined again by vector x,y displacements, and so to get the text to
scale and appear identical you can translate each character to multiple
lines in MapInfo. Although the individual MAP files get much bigger the
performance is fine - the only limitation being you cannot exceed the 2 GB
filesize limit. Of course the translator then needs to hold line definitions
and character definitions.
So if there was enough demand from users, this perhaps results in two wishes
for the user wish list.
1. More than 127 line styles - this requires new object definitions in the
MAP file.
2. Ability to render a line style by vector rather than raster definition.
Regards
Bob
----- Original Message -----
From: <nicholas....@mainroads.qld.gov.au>
To: <mapi...@googlegroups.com>
Sent: Thursday, November 30, 2006 12:42 AM
Subject: [MI-L] Re: Maximum number of linestyles in MapInfo 8.5?
>
>
>
> Hi Nick
What we have done in my workplace is use the LineStyle editor to build
MapInfo linestyles equivalent to the CAD linestyles.
We also have an .mbx that interrogates a CAD file, and builds a MapInfo
table
using the appropriate linestyles.
> So if there was enough demand from users, this perhaps results in two
wishes
> for the user wish list.
> 1. More than 127 line styles - this requires new object definitions in
the
> MAP file.
I see this could be done in two ways.
a) have more than 127 linestyles in Mapinfow.pen
b) have more than one .pen file (each with 127 linestyles) and incorporate
the ability to specify which .pen file inside the line object definition.
This would make linestyles work in a similar fashion to point objects,
where
you first choose a font, and then choose a symbol.
Personally, I much prefer option b) because;
- it would give me an unlimited number of linestyles
- the linestyles could be grouped into convenient categories, eg
mapinfow.pen,
transport.pen, boundary.pen, etc
- each category would have a manageable number of linestyles, ie no more
than 127
Nick