Greetings Mats.E
Agreed - Dynamic is good and although I sing MapInfo praises, there are a
few tools that don't come in the standard user interface.
The design challenge for the GeoBasemap mapping system was to deliver value
in a generic product. Fortunately we have had a pretty good user experience
with this module, perhaps in part because we stress the need to update
columns after editing in both the user doc and training. But more likely
the uses of our Mapping System (and most subscribers to MapInfo-L) are a
little above your "average" MapInfo users.
When I design an app from scratch, I specify locations in lat/long, store
attributes in a relational database and add some nice VB or Microsoft
Access database edit screens, hot-linked to the MapInfo via Mapinker. And
sometimes we build the Blue Marble co-ordinatate conversion dll into the
database forms. But that require custom development that comes at a price.
We are trying to bring down the cost of custom development with our
Images+/MapLinker suite but I suspect the market is segemnted - The
"applicaiton user" (who needs a nicely tailored custom interface), the
advanced GIS consultant (who appreciates our Mapping System) and the more
advanced GIS applicaiton builders (who could leverage off our MapLinker
product but might not appreicate the simplicity of our Mapping System
product).
Yes, Mats, I agree with your comments. Dynamic is good. And it is always a
challenge to deliver just the right level of technology for each situation
and each end user. .
.... Ken Moule
>Exa-Min wrote:
>> I sympathise with your request. Actually, quite a few or our customers
>> maintain a table view of the coordinates, and update that view to match the
>> map locations after MapInfo editing. Or they want to drop points on a
>> mapper and print out the locations for surveying contractors and the like.
>
>Mats.E wrote
>
>I do understand the need to 'see' coordinate values.
>As I understand, you favor using populated columns in the static table
>structure for that purpose.
>
>My point is that the average user most often fails to understand that
>such column values are disconnected from the graphic table component.
>Consequently, the user believes that points should move when new values
>are entered, or that values should change as points are moved.
>In short, the practice is prone to possibly fatal errors.
>
>This is why I always recommend the use of dynamic columns to show
>coordinates.
>A problem is of course the way MI defaults to lat/long values, but this
>can as you surely know easily be overcome within applications.
>
Exa-Min Resource Industry Consultants
2nd Floor, 143 Charlotte Street, BRISBANE
PO Box 12020, Elizabeth Street Q 4002
AUSTRALIA
Ph: +61 7 32100741 Fax: +61 7 32100738
Email: [EMAIL PROTECTED] WWW: http://www.geobasemap.com
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
