You cannot convert a Grid file to a shape. If you want the grids to
appear in an ESRI application you need to export the grid (in V-
Mapper) as a ascii grid (may take a while to convert). You can then
import these into ArcMap/ArcView using the toolbox, ascii to raster
(no spatial analyst extension required).
If you really need them as shapefiles, you will need to either contour
them in Vert Mapper or in ArcMap. However by the sounds of it, your
Mapinfo grids are fairly large resulting in long processing times/
large contour files.
Another option you have is to resize the cellsize in VertMapper - if
you click on the relevant grid and then info it will tell you the
current cell size - if you dont mind a coarser grid, use the resizer
tool to resize the grid to a larger size. If you then contour these
grids it will be quicker/smaller sizes.
think thats all the options u got.
Even enclosing the SessionInfo calls in a run command from the mbx doesn't
give the correct values. A disk search doesn't reveal any covert copies of
Mapinfow.prf, which is the file where these preferences are stored. And
LocateFile$() returns the correct file location.
This is happening on both v8.0 and 8.5.1
Cheers,
Martin
Martin Higham
Avantra Geosystems
tel (61 4) 2573 0428
fax (61 3) 9596 7997
www.avantra.com.au
What you are getting are the default settings for the coordsys,
paper/area/distance units within MapBasic. You'll have to set these
within your MapBasic app if you want different settings (set coordsys ,
set distance units etc). Don't forget that you can have different
settings for a MapInfo session, the MapBasic window and MapBasic apps!
HTH
Greg Driver
System Administrator
Applications Support
ICT
NOT PROTECTIVELY MARKED
Well, there's only the one "Window", but there's a "MapBasic Window
Environment" for each running MapBasic application, in addition to the one
for the Window itself. Each application has this environment to perform Run
Command statements (perhaps we should call them "Run Command Environments"
instead). Even more bizarrely, an application's Run Command environment is
different from the environment the application itself runs in!
I got burned with this once, trying to use Run Command to set the current
coordinate system, but I can see why you don't want multiple MapBasic
applications to have their default units and coordinate systems knocking
each other out of the way, even in the world of Run Command.
My guess is that MapInfo doesn't bother copying settings from Mapinfow.prf
into the Run Command environments for MapBasic applications, leaving it up
to the programmer to set these. Whether that should be considered a bug or
not, I couldn't tell you.
You could do something like
Set Distance units "m"
Set Paper units "mm"
Set Area units "hectare"
Set Coordsys Earth Projection 1, 33
Run Command "Set Distance units ""+SessionInfo
(SESSION_INFO_DISTANCE_UNITS)+""""
Run Command "Set Paper units ""+SessionInfo (SESSION_INFO_PAPER_UNITS)+""""
Run Command "Set Area units ""+SessionInfo (SESSION_INFO_AREA_UNITS)+""""
Run Command "Set "+SessionInfo (SESSION_INFO_COORDSYS_CLAUSE)
at the beginning of your app.
Hope this helps
Spencer
-----Original Message-----
From: mapi...@googlegroups.com [mailto:mapi...@googlegroups.com] On
Behalf Of Martin Higham
Sent: Wednesday, March 21, 2007 8:07 AM
To: mapi...@googlegroups.com
Subject: [MI-L] SessionInfo
But can anyone suggest a scenario where the SessionInfo function is actually
useful ? After all, its standard practice in a MapBasic program to
explicitly set the coordsys, distance, area and paper units - and if you
don't do that you're unlikely to be using SessionInfo anyway.
Cheers,
Martin
Martin Higham
Avantra Geosystems
tel (61 4) 2573 0428
fax (61 3) 9596 7997
www.avantra.com.au
> snippet from Greg Driver
>
> What you are getting are the default settings for the
> coordsys, paper/area/distance units within MapBasic. You'll
> have to set these within your MapBasic app if you want
> different settings (set coordsys , set distance units etc).
> Don't forget that you can have different settings for a
> MapInfo session, the MapBasic window and MapBasic apps!
> Snippet from Spencer Simpson
>
> My guess is that MapInfo doesn't bother copying settings from
> Mapinfow.prf into the Run Command environments for MapBasic
> applications, leaving it up to the programmer to set these.
> Whether that should be considered a bug or not, I couldn't tell you.
>
>