When translating from TAB to SHP format, the translator truncates the field names to a maximum of 10 characters, which is the DBase III standard imposed by SAFE and used since around 2007.  It leaves me with two choices, either clean up the table after the translation or export in another format, e.g. mif-mid, which does not have a 10 character limit.  With the next release of the translator, would it be possible for the Pitney Bowes development team to find a workaround solution?  Or, possibly SAFE could license another version of the translator to Pitney Bowes, which would allow a field name longer than 10 characters.

In the old version of the Browser window we could use the "shift" key to select all records between mouse clicks.  The new browser window apparently makes us drag to select multiple records.  This is very cumbersome when attempting to select hundreds if not thousands of records.

Please bring back the ability to use the "shift" selection option in the browser window...

Thanks

Mike

There are topics with many votes for re/moving Close All icon. From my point of view removing icon and make shortcut key for menu item "Close all..." is the best solution. Icon can't be accidentaly clicked and function is still easily accesible without searching in menu.

But custom shortcut keys would help way more than just with this issue. Very often I want "Print to PDF..." and I believe everybody who works with Mapinfo everyday have the most used menu items (my are also Select/ SQL Select etc.) not mentioning some menu items deep in Discover menu...

Example how is it solved in Corel:

A couple of built-in MapBasic funtions to convert  MapInfo geo-objects to wkt / ewkt / hexewkt and back. 

An example:

  update myTab set obj = wkt2obj( myDdl( obj2wkt( obj )  )

where wkb2obj is a built-in mapbasic function that converts wkt to a mapinfo geo-object, obj2wkb is a built-in function doing the reverse and myDll is some external dll function that accepts a wkt variable as an argument and returns a wkt value.

If you pt. want to get the positional information from regions or polylines you have to iterate through a region/polyline object using ObjectNodeX and ObjectNodeY to extract coordinate information into an array. This is extremely slow in MapBasic, because MapBasic iterates at a snails pace.

If you had the 2 above mentioned function you could deliver the object as a wkt string the the dll and let the dll do the iteration (a 1000 times faster than MapBasic)  

I would like the ability to create data entry forms for MapInfo, I imagine the feature would allow you to setup and associate a form with a particular table then whenever a new object is added to that table the user would get a form popup that would allow the user to enter the attributes for that record.

Example Form


I would like the form to be as user-friendly as possible so it would require a number of different input types including textbox, preconfigured dropdown, dynamic dropdown, textbox with auto completion based on values already entered, calendar widget, ect.

The main reason I think this would be of great benefit is it would allow you to standardise the data entered into a table as well as reducing the complexity for users of correctly attributing data.

A few other things would need to be thought though such as data validation, reuse of forms across multiple tables, permanent form association vs. workspace based form association.

Please add comments if you think there is anything I missed.

When an identifier in mapbasic is declared the same as a built-in function, a warning / error message should be shown. It may be possible and allowed to overwrite it, but it leads to lot of confusion.

Letting halo mode be the default for labels. I always turn it on.

when using the 'recover off screen windows' menu option - also recover the message window.

or alternatively always set the message window to appear in top left corner of MapInfo Pro working screen on first appearance each  time.

this would save lots of time have a button that switches between layout and data view. save having to keep going to the windows drop down and selecting layout.

there is already a tool that does this build it into mapinfo

logic

on layout view, select data frame, click button, that mapview bought into focus

with mapview selected press button go to layout with that mapview on it.

For us, a welcome addition to the functionality of MapInfo Professional would be:
an export option to GML, preferably version 3.2

Hi,

all is in the title !

i have two table :
1 mapinfo table containing ID
1 excel table containing the same ID but with some attributes data

1 - I would like to open the excel table and join with the mapinfo table (like in ArcGis, on a right clic on the properties of the mapinfo table or excel table)
2 - I'd like to change the excel data both in mapinfo and excel

If you could do that in the mapinfo 12.0, you will do a real step !

Best regards

The multi table structure manager doesn't save the mapbasic code once run so this is isn't repetable.

There should be an option to save a table restructure so it can easily be run again.

also useful would be an alias look up table so that eg. st. would change to street for a field name.

I think many users have exressed frustration that when a table is packed or replaced with an updated version of the table which has different ROWIDs that custom labels become out of sync and get messed up.

Can the label function be modified so you can choose a unique column to relate the label to intead of ROWID?

Then if a table is packed, or the source table is updated on the network, the labels won't be messed up. I think this will save a lot of frustration and confusion.

I would like to be able to copy text from the legend screen and paste into Word

GeoJSON is an Open data format for describing spatial objects (points, multipoints, lines, multilines, polygons, multipolygons, etc) It is commonly used with a range of web services such as REST.

As a format is is rapidly gaining support in the Open Geo community and can be used natively in libraries such as OpenLayers and Leaflet as well as GIS applications such as QGIS and FME and also the PostGIS spatial database.

The specification is here: http://geojson.org/geojson-spec.html

As an aside, it is similar to ESRI's JSON format, but obviously has no proprietary bits and pieces. Support for Open Standards like GeoJSON would be good PR for Pitney Bowes Software, IMHO.

-=-
Richard

I have noticed that the close table window is now bigger than it was before and it's a very good thing.  But would it be possible for Pitney Bowes to ameliorate a bit more this window by allowing us to stretch it in the dimension we want by clicking the right-down corner with our mouse?  Would be great!

I hope Pitney Bowes will consider the idea of giving us the possibility to choose "Mètres" or "Kilomètres" in French (with the French accents) as a possible measurement unit inside the draw scale bar tool.  Because I draw almost every scale bar in French, it would render my work easier.  Thanks for taking this idea into account.

I hope Pitney Bowes will consider the idea of giving us the possibility to choose "Mètres" or "Kilomètres" in French (with the French accents) as a possible measurement unit inside the draw scale bar tool.  Because I draw almost every scale bar in French, it would render my work easier.  Thanks for taking this idea into account.