HD malaysia gps software & map.

[Inggo]

Anyway, Bro Sunn, i see your garmin "current" map (not AntYong's map), still "have polygon" there..
as i know, papago map is inherit from garmin map.
but why our papago's map was 'LOST' of many polygon, whereas in the 'current' garmin is still there ??

I know what you are saying. Just keep it clean!

Regards

Bro Sunn, how about many papago 'lost' polygon..? this question always still in my mind

can you fix this?

so, it will be stop my enigma in my head

[sunn]

so, it will be stop my enigma in my head

It will not stop your enigma. The maps has its limitations.

[Inggo]

The Garmin format map is released weekly, the monthly Papago map's polygons might "outdated" by 3 weeks.

i know that, but it's for OLD Polygon not for new release polygon.
for ex: polygon in centre KL town (chowkit/kampung baru),
in garmin map still exist but lost in papago... so it's not outdated.
but still not exist...

[Inggo]

so, it will be stop my enigma in my head

It will not stop your enigma. The maps has its limitations.

Bro, if it still exist in garmin, then it should also be inherit to papago!

i was asking this to 76gpsguy while GG couple days ago, he was answered that this polygon just not yet coding.
he explain to me just add single byte code then polygon would appear.

so.. Bro Sun, you should be fix this..!

[sunn]

so, it will be stop my enigma in my head

It will not stop your enigma. The maps has its limitations.

Bro, if it still exist in garmin, then it should also be inherit to papago!

i was asking this to 76gpsguy while GG couple days ago, he was answered that this polygon just not yet coding.
he explain to me just add single byte code then polygon would appear.

so.. Bro Sun, you should be fix this..!

Its not a matter of single byte. Its a matter whether we have the polygons with us. Else we need a redraw.

Furthe, too much polygons will contribute to the lagging issues encountered by our members.

[fruitplus]

I think should be redraw to make it smooth..but take a lots of time.

[sunn]

I think should be redraw to make it smooth..but take a lots of time.

Yes, we should, fruitplus. It seems that the current polygons have a lot of overlapping. You can check under verify maps and "checked" overlapping polygons.

Please send drawn polygons to the respective mappers.

Regards

[fruitplus]

I think should be redraw to make it smooth..but take a lots of time.

Yes, we should, fruitplus. It seems that the current polygons have a lot of overlapping. You can check under verify maps and "checked" overlapping polygons.

Please send drawn polygons to the respective mappers.

Regards

Take noted long time ago for my drawing region..no problem at all but i need to ask you favour. I pm you

[sunn]

Take noted long time ago for my drawing region..no problem at all but i need to ask you favour. I pm you

No problem. You can PM me anytime.

Regards

[Inggo]

Bro, if it still exist in garmin, then it should also be inherit to papago!

i was asking this to 76gpsguy while GG couple days ago, he was answered that this polygon just not yet coding.
he explain to me just add single byte code then polygon would appear.

so.. Bro Sun, you should be fix this..!

Its not a matter of single byte. Its a matter whether we have the polygons with us. Else we need a redraw.

Furthe, too much polygons will contribute to the lagging issues encountered by our members.

i've check for my OLD X3 & my new X5 with my OLD PND and latest PND, both have NO Lagging issue.
Papago engine is fast and optimized in winCE, no problem at all to handle thousand of Polygon in papago,
some lagging polygon issue is only in garminXT version (but not in Nuvi).

Garmin & papago is different engine, so papago is best in PND (WinCE) & mobile version (Android) but not in winMobile version,
as well Garmin is best in Nuvi 'Unix engine' but not in winCE XT version.

if we can do it for garmin, then i hope our mappers can do (drawing) for papago, also.
or someday you can teach me how to draw (tracing) polygon for papago to get it perfectly.