Converting JNX to raster IMG

**Swall** · 14th February 2019, 11:45 PM

Originally Posted by AlexWhiter

I'm glad my work finds its users

Sure. One technical question, if I may. Early you'd said that 36 seems the most suitable value for the MapSeries parameter for raster maps. But the map product I'd mentioned uses 23 instead (assuming the generated report is correct). Can you approve that deviation?

**Giomen** · 15th February 2019, 02:48 AM

Originally Posted by Swall

Sure. One technical question, if I may. Early you'd said that 36 seems the most suitable value for the MapSeries parameter for raster maps. But the map product I'd mentioned uses 23 instead (assuming the generated report is correct). Can you approve that deviation?

Originally Posted by Swall

1. It seems they'd removed all images of the finest scale (1:50000) from the map (perhaps to avoid legal problems) but not from the advertisement. So on the device, max zoom level is limited to 200ì. Attempt to zoom in further results in empty screen.

I think these guys do not have any legal problem because of the project illegal at the whole.
Only mistakes take place. Partially you answer yourself. I do not use SAS.Planet. If only to peep new WMS servers. But I sure the bugs with lack of some scale tile and wrong mapseries are a common problem for Dummies.

The source is great. It is not a scanned map where distortion of scanning, projection recalculation and latitude error for printing purpose is present. It is the product ready for use on a digital device. All that one need to pick up a projection by latitude (it is damn hard)and slightly improve binding. The result is absolutely good after that. Plus or minus 3-6 meters is not predictable and not significant to estimation because on this scale (1:50000) the error in 5 meters is the greatest achievement in any case. And what is stopping to use any routable map for routing and searching beneath the raster layer?

**Swall** · 16th February 2019, 12:13 AM

Originally Posted by Giomen

And what is stopping to use any routable map for routing and searching beneath the raster layer?

No problem to do so with the device. Unfortunately, Basecamp is less capable in that regard. Beside, the screen size does matter. This raster picture looks great when it's displayed by Ozi Explorer running on a 8" tablet. Not so great on a tiny screen of GPSMAP 62 device. This is where the vector graphics wins. Power consumption. Perhaps the silicon chips uses more clocks to render a raster image so more current is drawn from the battery making the device less useful in the wood. The greatest advantage is that this map is easy to make. But what puzzles me, this is a very old stuff, the scanned images (not discussing how perfect they are) are circulating on the internet for more than a decade, so it's de-facto a public information. Why the topological information from this images is not yet vectorized by the independent mapping projects like OSM, OTM, etc.?

AlexWhiter · 15th February 2019, 06:43 AM

Originally Posted by Swall

Sure. One technical question, if I may. Early you'd said that 36 seems the most suitable value for the MapSeries parameter for raster maps. But the map product I'd mentioned uses 23 instead (assuming the generated report is correct). Can you approve that deviation?

ProductId <> 36 means some of the vector information from other maps - for instance, roads and POIs - will be visible above the raster.
This also changes the way the map's layers are distributed by the zoom levels in the device, the distribution becomes dependent on the device's detalization settings.
Perhaps, if you change the detailization to the max level, the map will become visible at the zooms below 200m.

**Swall** · 16th February 2019, 01:03 AM

Originally Posted by AlexWhiter

ProductId <> 36 means some of the vector information from other maps - for instance, roads and POIs - will be visible above the raster.
This also changes the way the map's layers are distributed by the zoom levels in the device, the distribution becomes dependent on the device's detalization settings.
Perhaps, if you change the detailization to the max level, the map will become visible at the zooms below 200m.

You're right, the map detail setting affects the visibility at max zoom levels (at the cost of slowing the device down). Now the misalignments are more apparent. But all the four layers (including 1:50000) are present, I did not noticed that initially. Out of curiosity, the only way to get more information about the MapSeries parameter is to install MPC and read the help files and to experiment, right?

AlexWhiter · 16th February 2019, 04:12 AM

Originally Posted by Swall

You're right, the map detail setting affects the visibility at max zoom levels (at the cost of slowing the device down). Now the misalignments are more apparent. But all the four layers (including 1:50000) are present, I did not noticed that initially. Out of curiosity, the only way to get more information about the MapSeries parameter is to install MPC and read the help files and to experiment, right?

I've tried all the values from 0 to 60, and they all behaved the same in my GPSMAP 62 - except 36th of course.
Perhaps, in the marine devices the level distribution differs.

**Allin** · 14th February 2019, 02:01 PM

Alex

I'm glad my work find its users

Yes, look here

All these maps of France in .img format do not exist in the trade, they were created thanks to your program jnx2img and SAS planet.
These cards are made freely available on this P2P site.
Alex I already wrote to you, you are the best.
thank you so much
(Google translation)

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

**Eyelet99** · 31st March 2019, 07:19 PM

Brilliant work Alex

I have a converted a few JNX files using all the default settings (i.e. none of the optional command line parameters) and the resultant single IMG files appear in my GRSr without a problem.

However, if I convert a series (>1 map) of adjacent JNXs and load them onto my SD card, only one IMG is available and selectable in Map Setup to be viewed - all the other IMGs are not listed. These are single level JNXs which are all under 1Gb in size.

Which of the optional command line parameters do I need to specify to resolve this?

Many thanks.

**Giomen** · 1st April 2019, 01:07 AM

Originally Posted by Eyelet99

However, if I convert a series (>1 map) of adjacent JNXs and load them onto my SD card, only one IMG is available and selectable in Map Setup to be viewed - all the other IMGs are not listed. These are single level JNXs which are all under 1Gb in size.

Use GMapTool for changing of FID in IMG. In this case the IMGs for each FID will be shown separately in map setup.

**Eyelet99** · 1st April 2019, 03:06 PM

Thank you Geomen - problem solved.

I followed the on-line instructions for the GMapTool and allocated numbers for FID and PID. This didn't initially resolve the problem until I spotted that the three test maps had all been given the same MapID during conversion to IMGs.

From Post #1 "MapID=<hex or decimal number>", where hex number must be either prefixed with '0x' or '$', or suffixed with 'h' - to manually set MapID, default is a random id.

I thought that the default setting gave a random id for each converted map, but it used the same one for each of the three maps I converted in succession.

Once I changed the MapIDs to unique numbers with the GMApTool all three were visible and selectable in Map Setup. Next time I will manually set the MapID in the command line.

Thread: Converting JNX to raster IMG

Thread Tools

Display

Hybrid View

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions