Kara, For background, here are some references on labelling as a GIS problem: http://www.spatialprojects.com.au/splinks.htm?exptag=ref&exptag=lbl
In other words, until we have 100+ GHz computers on our desk and memory to hold all data, solutions are going to require batch-style processing.(Even then, a city's worth of processing is never going to be as fast as a simple autolabel). An important characteristic of current generation solutions to look for is that the output is dynamic. This means that once a geographic area is processed, the feature styles and labelling should be available for normal interactive map display in desktop and web applications through all display scales. The end user should see display performance about the same as for a conventional autolabelled map. Making a few assumptions here but: Considering that the layers you want improved labelling on are usually static (updates for streets, zipcodes and suburbs once a year? ), and your own layers are most likely simpler point layers, one scenario is: process label layers for the base layers once and then combine this output with your own layers, giving them label priority and save to workspaces. Although I havent reviewed EverName and MapText recently, they should provide dynamic output of processed workspaces. Alternatively, put pressure on your data providers to deliver "quality label processed" street and boundary tables and workspaces. There is no reason why data providers cant do significantly more value-add before delivering data (eg. using a product such as spCarto). (Some of the data I receive for processing for my customers is in a truly woeful format! eg. common-attribute rivers and roads that are not a single polyline object between intersections). Street data providers (IMO) should provide a set of clean tables optimised for query and analysis, a set of tables with display handler applications (if needed) for quality label display, and workspaces to suit. My own applications deliver solutions using this approach: http://www.spatialprojects.com.au/spcarto.htm is designed primarily for urban street and boundary output. Workspaces and geosets allow reuse in MapInfo Pro, MapX or with a little more work, MapXtreme. http://www.spatialprojects.com.au/polylabel.htm is designed for general polyline and region labelling where character-alignment to the feature produces a much better result than word or string alignment. http://www.spatialprojects.com.au/spatialsql.htm?exptag=exp2&exptag=labelfns corrects point and region label layers for clashes with other features and labels. This uses an "iterative, greedy" approach as described in the first reference above. Although the output can be saved in workspaces (and zoomed etc.), the absolute placement is ideal for the chosen display scale only. HTH. Phil Waight. _______________________________________ SPATIAL PROJECTS Email : [EMAIL PROTECTED] Web: www.spatialprojects.com.au ----- Original Message ----- From: Kara Schneider To: [email protected] Sent: Wednesday, October 05, 2005 1:31 AM Subject: MI-L Label Placement Tool To Whom It May Concern: I am a MapInfo user working in the GIS Department at Blockbuster Inc. Our department is in the process of locating a good quality label placement tool to use with MapInfo Professional. The main purpose of finding this tool is to save time in the labeling process of creating very extensive detailed maps. We have tested two label placement tools used in MapInfo, for instance, SmartLabel by Map Text and EverName by EverMap. SmartLabel is able to mark streets, unlike EverName, but it still takes an extreme amount of time to run the application, and the results are not what I anticipated. Our main concern when creating detailed maps is the time consumption toward labeling streets and cities to make them visually appealing. We need a product that will label these items quickly with precision, and no overlap. If you know of any products that fit these criteria, please inform us. Thank you. Kara Schneider Development - GIS
