Hi guys this has been driving me crazy the last week. I have watched every youtube clip i could find and searched for every bit of info i could, and this seems to be the best place for answers.
I am trying to create a background map of a local dam for my new Lowrance HDS7. I found an aerial photo of it partially dry on sas.plantet that shows the old creek beds.
I have created a .kml file of the area i want with a few different zoom layers that i can open in Google earth and it shows all the details perfectly. I open Insight Map Creator change the processing mode to keyhole open my kml file that is saved to my desktop and click build. It runs for a minute than comes up with Process complete ( I have also tried skipping this step as i read i might not need it). I change processing mode back to Raster.
This is where I'm unsure. From the youtube clip i was trying to follow the source folders added are the ones created under sasplanet/cache/sat/than all the different zoom levels, I directed it to the sat/ folder. Although i even tried directing it to the kml file on my desk top as thats how i thought one person was explaining it. I have tried all different resolution options to try and make it work most with 1-8 or 1-16 as that seem to be what others were using.
For the work directory i have also tried a few different options, making its own folder on the desk top, saving straight to desk top, saving into folder with kml file.
Click build and it starts running. It creates an UnboundAt5s folder with sub folders for the different resolutions. In those folders are files called _3DTexture_D16208180.at5, folder for res 8 gets to about 1MB, and folder 1 gets to about 25MB.
This is where it fails. An error message will pop up, ive had two different ones. Critical Error: Index not found, or Read size does not match expected read size.

Can anyone please help with what i am doing wrong? I like playing around with this sort of thing but it seems im out of my depth here and I just cant figure it out.

Thanks,
Peter

Is this a projection / datum issue ? Have you tried converting your graphics to wgs84 / geographic projection or to Lowrance Mercator ?

T

I have the same issues with big maps... After about 1h-1h30 of processing, like Imagery files from GlobalMapper, and after created about 4.5-5gb in the temp folder (UnboundAt5), I get the exact same critical error, index not found... The only raster I was able to see in my Lowrance HDS was horrible and it was with really small images...

And when IMC give that error, it flush all processed file in the temp folder... I tried to copy them to another directory before it finish, and then, copy the files to the ShadedRelief folder, but it won't work...

Hope someone will come with a fix soon...

I'll see if that is datum issue like AnglingCharts said... But don't know how to do it from now...

Are you using a 32 bit operating system ? With files of that size you'll certainly have problems. Make smaller AT5 files, and simply load them all onto the SD card (give them different names just to keep things simple). You may not need the full range of scales either. Have a think about what you actually use.

T

No I have a 64b Windows 7... And I have I7 8 core, 24gb of DDR3 1600mhz memory, my system run on a SSD drive 280mb/write, and I work my map on another SSD drive 500mb/s write...

But generally, it's not when I'm trying to process AT5 but when I process Raster image that give me that error... Only one time I got it when processing AT5, but it was very large... But my images are very large too (500-600MB)...

I have also been having the same problem with IMC with SAS.

A mate is doing exactly the same as me and it is working for him but not for me.

I am a newby to mapping like this so I don't have much experience is custom mapping but im super keen to learn.

Cheers

Lee

fvignola@hotmail.com wrote:
I have also found that when using min res <8 in IMC i get these errors.

Cheers

Lee

What software level are you using?

I had this error, then backed up to 0.7.2.0, and so far so good.

Current level is 0.7.4.0, but I do not know what features or fixes are included.

LittleGazoo wrote:
Yes i was using 0.7.3.0 but now i have upgraded to 0.7.4.0 and it seems to work.

However I do have problems with with black borders. The option for Image boundary has been removed and has been replaced with Filter: Alpha <value> and I keep getting a black border around my AT'5

Cheers

Lee

Yes, 0.7.3.0 gave me that error. I'm still looking for 0.7.4.0's release description as I would like to upgrade to it.

For black borders:
After selecting Raster Mode:
Advanced Options-->Raster Options--> Filter Image Boundary and check it

Now the trade-off is that the black borders will be filtered, but the outside imagery will not display until you are really zoomed in on that edge image. Make sure you extend your imagery further than you wish to view...

LittleGazoo wrote:
Yes I am trialling the filter as I do not know much about custom mapping etc so I am fumbling my way through learning, which is a good way to find out how and why things works.

Thanks for you help.

Cheers

Lee

Thanks for all the tips I did end up creating a map but couldnt get one to work <8 so there wasnt much detail when zoomed in. I have just updated to version 7.4 and it is working perfectly, just created a map of a local lake when it was nearly empty from resolution 0.25 to 32 and it worked. The contours line up almost perfectly over the image. Detail is so much clearer I can see where timber is laying and rock clusters. Now i just have to find time to go out and try and find them.