UK Users Group

Welcome to the community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-10-2017 09:44

    When the data is downloaded there is a separate file for resources which contains a number of separate GML files inside it. Should I move these into the same folder as the main GML files and run the translator for all the files together? Does it make any difference if this is run as a batch or separately?



  • 2.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-10-2017 09:49

    I shall clarify that and say that using v15 has anyone used it and it worked? After 5 hours today it crashed out and created a 2GB roads.dat file that seems to have no data in it.



  • 3.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-13-2017 05:50

    I've played with FME within MapInfo V16 64bit and found that I had to translate each GML file individually and prefix the filenames with the relevant OS tile e.g. SJ8545_TopographicArea in order to place all of the files together into the same folder. Once all of the tiles had been translated into tab files, I then used seamless tables to bring them all together for ease of loading into my workspace, one for TopoArea, one for TopoLine etc. However then came the issue of theming the layers in order to give them the usual OS look and feel, this I didn't have so much luck with I'm afraid, it was far too time consuming to add a theme and then select the colours to match the OS standard. I think this is probably why most people use third party OS data loaders such as OSM2MIF/MIFTAB, MapGML etc. as the GML gets translated and themed accordingly, unless there's another way of adding the theming information to the layers?



  • 4.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-13-2017 17:19

    ?Martin, are you using 32-bit MI Pro?

    Sounds like you have hit the 2GB limit in 32-bit mode - at which point MapInfo halts.



  • 5.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-23-2017 04:43

    No this was the 64bit v16.2. It seemed to happily create some of the files but not the road network tab. I am using the Routing dataset. Perhaps, as Matthew says above, the issue can be solved by individually translating the files or chunking it up and converting sections. Bit frustrating though.   



  • 6.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 11-23-2017 12:29

    There is the RouteFinder translator and MapGML that are capable of handling OS Highways - but a cost is associated. OS Highways is only available? now as a region or national coverage - not chunks/tiles.



  • 7.  RE: Has anyone gone through the process of converting OS Highways GML files using MIPro 15/16 FME translator?

    Posted 12-12-2017 08:58

    An update on this issue. I actually already had purchased the Routefinder translator? but hadn't used that as I thought I did not need to and that the fme tool within MIPro would do it. I know that OS have released workbench files for the full FME on github but it seems poor that as a user I would need to purchase the full version of FME in order to get my OS product to work in one of the industry leading GIS products on the market. Not sure whose fault it is (and it could always be mine as there is no guide anywhere I can find) but if OS provided the data in tab format it wouldn't be an issue.. Suffice to say Routeware's OS Highways Translator worked beautifully, converting the whole dataset in under 20 minutes and I would recommend that to anyone with issues. Probably saved me days of researching and searching for solutions that would work.