If you are using MapInfo Font symbols or normal MapInfo 3.0 everything should come across almost exactly. mapinfoToQgis.py will use the same fonts in QGIS as you did in MapInfo and select to the correct symbol size. Although if you are using custom MapInfo 3.0 symbols you will get the default QGIS black square symbol,you can just change it to something better after loading the QML.
Like I said at the start, hopefully other people will find this tool handy as I know I have. If you do find it handy let me know, I would love to hear peoples feedback. Also if you find any bugs let me know in the comments or log a issue on -to-QGIS-style-generator/issues
Then we have sorting, which is meant to be the cool new feature. This is not the normal just click on the header to sort the column, no because that would be too easy, you have to right click in the browser, click sort and select the options which then opens a new browser window. um what?
Next. No visible scroll progress. When you move the little scroll box on the side the browser waits until you have finished to show you the data. I guess the old browser did this too so why change it!
What is the typical sort pattern? Left click header, table sorts ascending click again and table sorts descending or vice versa. Then you normally have any extra sorting stuff in the right-click menu e.g Sort Ascending, Sort Desending, Clear Sort etc.
The other day I posted an entry about using MapInfo with Python and Qt (see -map-control-into-qt-python-form/), one big thing that I missed was support for callbacks, which if you want to do anything related to integrated mapping is a must for map tool support.
I think Python could be a good language to prototype MapInfo based app, or even build a whole app itself. If you do end up making something of it let me know I am quite interested with what people could come up with.
A while ago I posted about how to create an instance of MapInfo in .Net, If you missed those posts then they can be found here. In these posts I outlined how you can create a instance using three different methods, in the reflection based post I said that one of the disadvantages of doing it this way was that it was slower. I said this due to just my observations but I thought it would be a good idea to put it to the test and show the speed difference.
I created a simple project to test and show me the results of three different things: Speed of complied MBX, calling a MapBasic function though the Do and via the interface (see posts 1 & 3) and calling Do and Eval via reflection (see post 2)
Since the release of version 0.5 of my MapInfo Window Manager I have been working on the new version which will be Version 1.0 and to be released soon. It has some new features, bug fixes and a improved UI.
However I would like to get some more testing done by some other people to make sure that Version 1.0 is good and stable. I am also still look out for anymore ideas that I could throw into Version 1.0.
If you would like to give the beta a test and do some bug hunting for me, or likewise if you have a feature you would like to see rolled into Version 1.0, please contact me on here or by email (which you can see in the about tab page screenshot above)
A lot of information flows though the global MapInfo-l message board, things that would be nice to have down as feature requests or bugs so that people can comment and PBBI can really see what people would like in their products. I am aware that you can send feature requests though the MapInfo Professional software however I think having a community effort would be much better as you can quickly see what other people
have thought of and if you support that idea also, which in turn lets PBBI see what the community wants.
Over the last couple of weeks I have been working on a new MapInfo Professional tool called Window Manager, it is nothing big but I find it very handy. The window manager shows all the open map and layout windows in a visual WPF tree view control and gives the users quick access to basic functions when dealing with windows in MapInfo eg Rename and Clone etc.
The current version (0.5) is only really a preview version and still has a little bit of work to make it a bit more polished looking, however I have tested the clone, close,rename and bring to front commands a lot as I use this tool all the time and it feels stable. I am releasing it early rather than waiting for a couple of more weeks for a couple of reasons 1) Fear of forgetting to release it due to being busy 2) Would like to see what other people would like to do with a tool like this.
I have been working on a rather large mapping project over the last couple of months, and that thought I would write a blog post about some features that I would like to see implemented in MapInfo Pro to make map making a little bit easier. This could get long so I might break in down into different posts.
Thematic maps are great, I use them all the time but unfortunately they are a big pain in the butt when it comes to using and applying them across a large range of maps and workspaces and using them to keep map updated.
This means you would be able to store templates in one place and any time somebody opens the workspace, the theme file is read and applied to the map, meaning you will always have the latest style changes. By using the full path or just the theme name you could store theme files on a network drive or just with the workspaces if it is only going to be used for a selected job with lots of workspaces.
MapInfo Professional supports a range of data formats including many common PC file formats (such as Microsoft Excel, Access, DBF and CSV files), relational and spatial database formats (Oracle, Microsoft SQL Server, PostGIS, SQLite and ODBC compliant databases), and spatial data formats ( AutoCAD DXF/DWG, SHP, DGN and more).
You can also use imagery (aerial images, satellite images, scanned paper maps, etc.) of almost any format in your maps. And MapInfo Professional includes access to Microsoft Bing aerial and hybrid maps as standard.
You can also aggregate values using statistical or any math functions to associate a symbol or colour to a point or a region based on a calculated value. For example, view your sales territories according to the number of customers in each area.
MapInfo Professional v16.0 allows you to keep up-to-date with the latest MapInfo news and events through the inclusion of an in-product notification system. The new reader inside MapInfo Professional will automatically check for and retrieve notifications of important information such as patch releases and updates, thought leadership articles and license expiry notifications.
Encom Discover boosts the data handling capabilities of MapInfo Professional, adding support for over one hundred additional industry-standard formats. These include advanced functionality such as image rectification and re-projection, batch ECW import, vector import and conversion (such as the GPS eXchange and Google Earth formats) and database connectivity (e.g. DataShed and AcQuire).
MapBasic allows the development of software in popular programming languages such as C, C and Visual Basic to help automate repetitive operations in MapInfo Professional. Hundreds of third party applications have been created using this flexible development environment, many of which are offered to the MapInfo Community for free.
MapInfo MapBasic is specifically for customising MapInfo Professional. For professional developers we offer a range of developer tools for different environments and deployment models. Pictured (left/right) is MapInfo MapXtreme, a 100% .NET development kit for desktop or web based applications. We also offer a modular platform for enterprise grade applications consisting of Location Intelligence, Routing, Geocoding, Address Management and other modules.
Purpose. To examine the association between living in proximity to Toxics Release Inventory (TRI) facilities and the incidence of childhood cancer in the State of Texas. Design. This is a secondary data analysis utilizing the publicly available Toxics release inventory (TRI), maintained by the U.S. Environmental protection agency that lists the facilities that release any of the 650 TRI chemicals. Total childhood cancer cases and childhood cancer rate (age 0-14 years) by county, for the years 1995-2003 were used from the Texas cancer registry, available at the Texas department of State Health Services website. Setting: This study was limited to the children population of the State of Texas. Method. Analysis was done using Stata version 9 and SPSS version 15.0. Satscan was used for geographical spatial clustering of childhood cancer cases based on county centroids using the Poisson clustering algorithm which adjusts for population density. Pictorial maps were created using MapInfo professional version 8.0. Results. One hundred and twenty five counties had no TRI facilities in their region, while 129 facilities had at least one TRI facility. An increasing trend for number of facilities and total disposal was observed except for the highest category based on cancer rate quartiles. Linear regression analysis using log transformation for number of facilities and total disposal in predicting cancer rates was computed, however both these variables were not found to be significant predictors. Seven significant geographical spatial clusters of counties for high childhood cancer rates (p
b1e95dc632