MI projecting on the fly
It was my understanding that vector coverages in different projections can be mixed willy-nilly, technically speaking, within a map window, and each would be reprojected on-the-fly to that windows projection as defined by the raster base projection. In a discussion with technical support at a company that supplies several MI add-ons, I was told I was mistaken. Rather, that on-the-fly projection only correctly occurs if the various vectors are all in lat/long. What? That makes on-the-fly projection a very limited feature, indeed. The User's Guide only indicates on-the-fly reprojection to be a problem in processing time, not in mapping. Your clarification of this point will be greatly appreciated. Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI: tfwread.mbx, a warning
I've been vexed for some time by various raster images not aligning correctly along edges or when overlain. You may have read some of my queries to this list made while searching for an answer. Here is the answer: I'd been using tfwread.mbx to import the tiffs. This was apparently a bad move. When the tiffs are imported with georeg.mbx instead, the images align "perfectly". Ironically, I'd started using tfwread because georeg had repeatedly failed to import some files at all. I've no idea _why_ tfwread is in error, but just deleted it from my toolbox. Drew "I'm glad that's over with" Phillips Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI SUM: SQL and aggregate functions
Sorry it took so long to to SUM this. I received several interesting solutions suggesting several different methods. These included a concise SQL query with subselects that would work if MI had a full SQL implementation, and several methods for coding each group of records (formations in a boring) in sequence (using rowid), then querying within the sequence. T. Warman suggested adding an explicit field to the table called "Overlies". S. Cox also offered an awk script that is delightfully brief (ah, I remember those awk days fondly), but I never got around to getting an NT awk-ifier to run it with. Probably because the work would have to be done outside of MI. My solution is relatively painless and evolved mainly from a solution from B. O'Donovan: (1) Select top of bedrock: select boring, formation, min(top) from logdata where formation = "R" into toporock Note that the bottom of the surficial units (where not formcode = "R") cannot be identified by a similar query. Max() selects the record following (lower) deepest surficial formation, whereas min() correctly selects the top of bedrock, as shown. Also note that the select statement is considered dangerous to the SQL cognoscienti because the non-aggregate values don't necessarily relate uniquely to the aggregate value. Indeed, SQL implementations "more sophisticated" than MI's won't allow this sort of statement. To be rigorous, the non-agg columns should be included in the group by statement [P. Strain] (2) Select first unit above bedrock by matching respective "top" and "bottom" of units: Select formtable.boring, formtable.formation, formtable.top, formtable.bottom from formtable, toporock where formtable.boring=toporock.boring and formatable.bottom = toporock.top As Brendan noted, there may be a more elegant solution, but I haven't found it yet. Attempts to use subselects always failed. In addition to those mentioned above, thanks go to C. Vavilala, C. Huyck, and M. Higham. I need not add, but will anyway, that this list has once again proved itself invaluable. Happily initiating the 3D phase, Drew -Original Message- From: Phillips, Andrew [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 10, 2000 2:07 PM To: mi-l (E-mail) Subject: MI SQL and aggregate functions I have a table of borings with formation data. The structure is something like this: Boring Formation Top Bottom AS 0 2 AF 2 22 AD 22 32 AR 32 150 B F 0 25 B .. . . .. . . .. . I would like to select out the record that lies above each "R" formation (i.e., the first formation above bedrock in this case). The most successful SQL statement that I have tried is: Select Boring, Formation, Max(Top) From Formtable where Formation "R" group by Boring order by Boring into firstup Although this does return the correct depth of the "first formation", values in the other fields are from the previous (higher) record. How can I select the correct record? Thanks, Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI SQL and aggregate functions
I have a table of borings with formation data. The structure is something like this: Boring Formation Top Bottom AS 0 2 AF 2 22 AD 22 32 AR 32 150 B F 0 25 B .. . . .. . . .. . I would like to select out the record that lies above each "R" formation (i.e., the first formation above bedrock in this case). The most successful SQL statement that I have tried is: Select Boring, Formation, Max(Top) From Formtable where Formation "R" group by Boring order by Boring into firstup Although this does return the correct depth of the "first formation", values in the other fields are from the previous (higher) record. How can I select the correct record? Thanks, Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI labelr tool
As recently discussed here, I tried using the labelr tool to convert autolabels to a separate text layer. Problem : I set the view in the map window at 1:24 000 and autolabel a point layer w/ font size = 8 pt. Scenario A.If Labelr is then run only labels within the map window are transferred to the Cosmetic Layer. Scenario B.If Labelr is run so that the entire layer can be viewed, the transferred font size is a huge 50 pt. With the labels still in the Cosmetic Layer, one can the zoom back to 1:24K and change the font size to 8 pt, but then the label position is inaccurate. All other attempts to achieve the desired label size, such as changing attributes after the labels have been saved to a new layer, achieve similar undesireable results. How can I create a text layer of labels that are positioned correctly and with specific font attributes? Am I missing something here? Thanks, Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI RE: Georeg.mbx gives ...invalid registration error?....NOT
I have to apologize for wasting bandwidth with this question. Of course Georeg balked, the file was a tif, not a geotif. By using filetableopen*.tif, the expected registration dialogue opened. I know, I'll take the next two days off! Thanks, anyway, Drew -Original Message- From: Phillips, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, January 21, 2000 9:15 AM To: mi-l (E-mail) Subject: MI: Georeg.mbx gives "...invalid registration" error? I'm trying to open a scan of a map as a *.tif and register it. However, Georeg balks and gives an 'invalid registration' error. How can the registration be invalid? There _is_ no registration! What is most perplexing is that I've performed this little procedure several times before. By contrast, Worldreg opens the image, though with no projection of course. Looking for your suggested solutions. Thanks, Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI VM: edit Z of individual pixels?
I've a series of DEMs (USGS origin) that need some editing. How can the Z value of a particular pixel be changed? My goal is to smooth obviously incorrect values with their neighboring values. Here's what I have been able to do (using VM2.1.1/MI5.5, no MB yet): 1. Successfully selected out-of-range values and reassigned them to null by using Grid Query. That's an improvement, but doesn't seem to be a route to assigning a (realistic)value to each particular pixel. 2. Captured values of selected pixels to the VMCapture table. These values can clearly be edited and the table saved, but how can they be incorporated back into the grid? Documentation is sparse. 2a. In one test I selected a small region (~12 pixels) around the target pixels, assigned realistic-if-arbitrary values to the targets, saved the table, created points from the table, and interpolated those in VM. Attempts to union this patch with the original grid have so far been unsuccessful. Seems like there ought to be a better way, anyway. Your suggestions for further experiments greatly appreciated! Drew Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI ellipse object creation behavior
I would like to create ellipses -- circles, actually -- of a specific radius by the click-and-drag method. The open Ruler window indicates a radius, but upon releasing the mouse button the radius of the resulting circle is not that length: it is shorter when the zoom is wider than the circle and visa versa. As well, the offset varies with circle size relative to the zoom width. Does anyone know exactly what is happening or why? I thought I had come up with a handy method for triangulating in the Cosmetic Layer, but this behavior will nix that. Thanks, Drew ** Andrew Phillips, Ph.D. Quaternary Geology Section Illinois State Geological Survey -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
SUM: MI cannot Update Column
Thanks to the many people who pointed out that the table must be packed to perform an Update Column. Exactly my problem. Other solutions were also suggested, however, and may be valuable to others: --J. Chioles recalled if the first column of a table to dump into from another is integer (though it may have been the other way around), the join failed in v.4.5. Solution: If the first (or only) column is integer, try adding a dummy char field in front of it . --Rather than packing (and re-attributing!) the target table, select only the records that correspond to the source table. Then update those. [M. Knudsen] Drew Phillips -Original Message- Okay, I give up. The table for which I would like to update a column has these attributes: -It's an MI table -not read-only -fields of identical structure to source (is that even necessary? don't think so) -viewable and editable (as above?) What else am I missing? Many thanks, -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI SUM: DOQs will not overlay
Mike Lepage astutely suggested inspecting the .tab files. I still haven't figured out why the specified ellipsoids differed between the two files (nor why the particular obscure ellipsoids had been originally selected -- jeepers!), but reregistering with worldreg produced identical tabs. Drew -Original Message- From: Phillips, Andrew Sent: Thursday, September 30, 1999 1:29 PM To: mi-l (E-mail) Subject: DOQs will not overlay I've two DOQs. The first has a 1m resolution, the second was created by resampling the first at a 2 m resolution. Both .tfw files are identical. I registered them using Georeg.mbx. When opened, both appear automatically within the same mapper, suggesting to me that they are, indeed, in the same projection. However, they display with about a 90 m offset. Although I seem to recall some discussion about weird behavior of multiple raster images in MI, I have used a similar set of DOQs in another project with no image shifting (although that was v5.0 rather than the v5.5 in use now). Is this congential, or is there something that I can do? Many thanks, Drew ** Andrew Phillips, Ph.D.615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey (217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI DOQs will not overlay
I've two DOQs. The first has a 1m resolution, the second was created by resampling the first at a 2 m resolution. Both .tfw files are identical. I registered them using Georeg.mbx. When opened, both appear automatically within the same mapper, suggesting to me that they are, indeed, in the same projection. However, they display with about a 90 m offset. Although I seem to recall some discussion about weird behavior of multiple raster images in MI, I have used a similar set of DOQs in another project with no image shifting (although that was v5.0 rather than the v5.5 in use now). Is this congential, or is there something that I can do? Many thanks, Drew ** Andrew Phillips, Ph.D. 615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey(217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI VM: Not all records in point table updated
Esteemed colleagues: I performed a Point Inspection on a hypsographic grid. Rather than finding a new column with elevation data for each record, I found a new column with elevation data for exactly 199 records (out of ~5000). The selection of records seems to have been random. Is there a limitation on records calculated? I admit to not yet having tested the calculation on a smaller data set, but I have performed the operation before with similarly large data sets. Is there another explanation? Thanks, Drew ** Andrew Phillips, Ph.D. 615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey(217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI Open Workspace error
The past bunch of times that I have tried to open a workspace, either through the "Open Previous Session" dialogue or through the File menu, I have received the error message "Variable or fieldID not identified" and a following message that the workspace cannot be fully opened. I've tried editing the *.wor file, but can find no obvious errors, e.g. files not in the expected directories. As well, I've resaved the workspace after creating it again. What variables or field ID's could I be inadvertently creating, and is there a way to identify them? Drew Phillips -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI: Overlay symbols
I'm trying to show two different attributes of point data, one attribute ordinal, the other nominal, by varying color and symbol type. Had this great idea to do so by overlaying thematic maps. Apparently only one thematic map can be visible at a time, however. Is there another method? Drew ** Andrew Phillips, Ph.D. 615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey(217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI BM: Does this have basic functionality
Mappers: I've been using Borehole Mapper (v 1.01) for awhile now, and am perplexed at some seemingly fundamental problems with it. What are your experiences? Are these problems congenital, or is there something that I can do about them? 1. Plot Multiple Logs: After selecting N logs, only N-1 are plotted, and the top of the N-2th log is missing. Actually, the Plot Single Log doesn't work either, except when I used the examples that came with the program. 2. Along a transect, selected logs are not always plotted in their correct spatial order. 3. Certain logs from the same data set will not plot no matter what. The data look like all the other data as well as I can make out. 4. Autolabeling lithological units with their descriptions works OK as long as those descriptions are short. Is there any way to force some formatting, e.g., wrapping the text? Haven't yet come up with much by labeling with an expression. ** Andrew Phillips, Ph.D. 615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey(217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI regions are lines in thematic map?
I'm trying to create a thematic map of a table of polygons, but the only available display style parameters are for lines. The result is solid colored regions. What gives? I wonder if the creation method had some effect: 1. Drew polygons 2. Converted them to polylines for editing 3. Converted polylines to regions. Are these regions not polygons? ** Andrew Phillips, Ph.D. 615 E. Peabody St. Quaternary Geology Section Champaign, IL 61820 Illinois State Geological Survey(217) 333-2513 (ph) [EMAIL PROTECTED] (217) 333-2830 (fax) -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
SUM: MI: Universal Translator causes crash
Thanks to all those who responded. Several suggested that the crash was caused by a bug with VM; UT would work with VM not running. A patch was created for the bug and is included in recent versions of MI. I am using MI 5.0 and thus the solution had to be sought elsewhere. Today's solution: Make sure that mapinfow.prj resides in the mapinfo installation directory. In my case it existed in several directories (Tools, ArcLink, ShapeLink) but the local root. The file could be accessed by several other procedures, and so hadn't yet appeared as a problem. MapInfo Tech Support identified this while investigating a seemingly unrelated problem with ArcLink. Hats off to Cindy, and thanks to Mike, George, Tony, Peter, and Rick Original message: ** When trying to translate a *.shp file, UT crashes when the Projection button is pushed. Only resurrection on this NT system is to End Task. Once while doing so I found an error message window giving something like "out of disk space for temporary files". Given that there is actually plenty of disk space available, there must be some other source for the error. Any ideas? -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
