RE : [MI-L] Selecting object types

Robin Prest Tue, 27 Jun 2006 12:14:46 -0700

Title: Message

Hi,

See below, it goes much further than what you're asking for (it selects all sorts of things, including points for exemple)

Rob.

From IAA Website : http://members.iinet.net.au/~haycraft/iaa/ (an Information Technology consultancy business located in Canberra, Australia)

Select By Drawing Style (SDS)

If you're a Mapinfo Pro user and you want to Select some rows of a table, not by values in the text fields, but by the Drawing Style of the objects in the Obj field, then it's a real chore.

For example if you need to select, from a table of Text objects, the rows containing Text features drawn with

Box background
Bold and Shadow effects

then you'll have to type

select * from TextTable into Selection
where (((StyleAttr(ObjectInfo(Obj,2),2)\256) mod 2)=0)
and (StyleAttr(ObjectInfo(Obj,2),5)<>-1)
and (((StyleAttr(ObjectInfo(Obj,2),2)\1) mod 2)=1)
and (((StyleAttr(ObjectInfo(Obj,2),2)\32) mod 2)=1)

SDS is query builder tool that lets you build and execute such queries through familiar style-picker dialogs.

For a screenshot of the SDS dialog settings for the above query see SDS.

To get a copy see Downloads.

http://members.iinet.net.au/~haycraft/iaa/iaa11g.htm

-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Peter Horsbøll Møller
Envoyé : mardi 27 juin 2006 19:57
À : Ronning, Christine
Cc : [email protected]
Objet : RE: [MI-L] Selecting object types

Christine,

There is a few ways of doing this:

Select     *

From    MYTABLE

Where

1.     Str$(OBJ) = "Point"

2.    Str$(ObjectInfo(OBJ, 1) = "5"

3.    Area(OBJ, "sq m") = 0 And ObjectLen(OBJ, "m") = 0

I would recommend using the second. If you need to find other object type, the values to be used are these (copied from the MapBasic.def):

Define OBJ_TYPE_ARC                             1
Define OBJ_TYPE_ELLIPSE                         2
Define OBJ_TYPE_LINE                            3
Define OBJ_TYPE_PLINE                           4
Define OBJ_TYPE_POINT                           5
Define OBJ_TYPE_FRAME                           6
Define OBJ_TYPE_REGION                          7
Define OBJ_TYPE_RECT                            8
Define OBJ_TYPE_ROUNDRECT                       9
Define OBJ_TYPE_TEXT                            10
Define OBJ_TYPE_MPOINT                          11
Define OBJ_TYPE_COLLECTION                      12

By the way, a different approach would be to export the table to Shape using Universal Translator. This would result in a number of tables named by the object types. Remember that Shape can not contain different objecttypes in the same file. Then you just need to reimport - or open - the generated Shape files.

HTH,

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

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronning, Christine
Sent: Tuesday, June 27, 2006 7:32 PM
To: David Reid; Bill Thoen
Cc: [email protected]
Subject: [MI-L] Selecting object types

Hi all,

Can anyone tell me how to select object types within a table? For example I have a table with points and regions but would like to seperate them out. How would I select just the points? Thanks

Christine

-----Original Message-----
From: [EMAIL PROTECTED] on behalf of David Reid
Sent: Tue 6/27/2006 7:50 AM
To: 'Bill Thoen'
Cc: [email protected]
Subject: RE: [MI-L] Strange "Find" results geocoding in MI ProViewer

I should have added that within the Workspace being used, I have "Inset
address" from end of street set to zero as these are mainly rural streets
set to 0.001 mile addressing format.

Find Using Streets(COL1) Refine Using Communities(COL1) Options Abbrs Off
ClosestAddr Off OtherBdy Off Symbol
Inset "0" Distance Units "ft" Offset "15" Distance Units "ft"

When I plot the two addresses (that have come to our attention) in Mapinfo,
they geocode right where their supposed to. Thus far, all other addresses
that have been searched appear where their supposed to.

Additionally, the tables being used are maintained in MI 6.5, but the
Proviewer we're using is 6.0. I would think that would be an issue though.

Strange indeed
Dave

-----Original Message-----
From: Bill Thoen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 27, 2006 9:08 AM
To: David Reid
Cc: [email protected]
Subject: Re: [MI-L] Strange "Find" results geocoding in MI ProViewer

On Tue, Jun 27, 2006 at 08:42:57AM -0500, David Reid wrote:
> Yesterday, on various addresses entered to the "Find" dialog, it started
> geocoding some of these addresses as much as 1/2 mile from where the
address
> is known to accurately geocode otherwise.
>
> Has anyone seen this before and found what causes this problem?

Are these addreses supposed to be near the start or end of a long rural
road? MapInfo's algorithm moves addresses near a road intersection back up
the road about 10% of the length of the segment. This keeps the locations
from "bunching up" on intersections in the cities, but it's not helpful in
the country. I think there's a preference setting for this somewhere.

--
Outgoing mail is certified Virus Free
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.5/376 - Release Date: 06/26/2006

_______________________________________________
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

RE : [MI-L] Selecting object types

Reply via email to