Printable View
Proggy 9.18.27.676280 from this forum just before the big crash.Quote:
Originally Posted by osiris4isis [Only registered and activated users can see links. Click Here To Register...]
Map is Here New Zealand 2016.Q4
Sent from my SM-A310Y using Tapatalk
Osiris4Isis,
excuse me, I was very busy. I'll try to answer your last post from yesterday.
The \content\ map folder containing only the .fjv file. Note the marking (1): "Junction View".
Spoiler: pic
The \content \map folder containing both .FJV and .FJW. Note the marking: (1) "Junction View" and (2) "Junction View NG"
Spoiler: pic
Mark (1) = FJV and (2) = FJW.
Nextgen works with FJV and FJW. Primo works only with FJV. I hope I have helped you. ;)
[]'s
PS: Boki, thanks for the help with the "spoiler". ;)
Preliminary decoding of junction data showed that for HERE, the .fjv and .fjw are in similar format (which confirmed that they looks similarly in vector format)
Here are the stats for HERE New Zealand 2016Q4
Spoiler: .
However, TomTom .fjv are quite different, they are indeed raster image
Here are the stats for TomTom New Zealand 2016.12 (I could not find TomTom .fjw files)
Spoiler: .
Great work!
Here is a screenshot of a TomTom fjv as it appears when driving
There doesn't seem to be a landscape option that I can find.
Spoiler: TOO LARGE PIC
Sent from my SM-A310Y using Tapatalk
Thanks for verifying, I was wondering if it would stretch in landscape mode. Ok, so we have something new. The .fjv can store format similar to .fjw (definitely different from raster format) I have to investigate on how to decode that format. But why create two file extensions for storing similar format AND why .fjv always less entries than .fjw (but bigger in size)?
It would take a lot of testing to confirm but since the HERE images don't contain a lot of detail it's possible they re-use the same image for many junctions. That could partially explain the different counts.
That wouldn't work for TomTom because the images are very specific. In the example I used the buildings and even the big tree are actually there in real life.
Sent from my SM-A310Y using Tapatalk
Yes, vector format (for sure) use parts to build an image. This is same way Garmin does it. And it's widely known that .fjw are vector format. What's interesting is we now have vector format in .fjv as well. But why bother? There are less junction in .fjv and it's bigger in size. So we have some violated rules (or preconceptions)
1. Vector are in .fjw and Raster are in .fjv
2. Why store similar format in .fjw and .fjv?
3. If Primo/iGO can read .fjv with vector format, that's mean it's capable of doing so very early on (BEFORE .fjw was introduced)
Only thing I can think of is they are made by different entity. I need to find HERE .fjv in raster format, anyone got old version of .fjv (before 2010?)
BTW, for raster, a "count" is definitely one junction image. For vector, I'm 99% sure a "count" is also to build one junction image (ie: not parts of an image)
Here is an example of the first two entries for New_Zealand_HERE_2016.Q4_170102_(JW).fjw
Spoiler: .
And here are first two entries for New_Zealand_HERE_2016.Q4_170102_(JV).fjv (do not assume they are corresponding with .fjw file)
Spoiler: .
Hello,
is there actually a way to use FJW Files? Or is it still for becker and falk?
I'm using Israel Nextgen.
Thanks.
Any NextGen can use fjw files.
You just must have all lycs (or have fully cr*ck*d software), and active ux in proper folder.
Then enabled that options in NG settings.
thanks.
Which active UX?
NG Settings?
Have you got a screenshot?