Search the web
Sign In
New User? Sign Up
global_mapper · Global Mapper
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Real people. Real stories. See how Yahoo! Groups impacts members worldwide.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Polish format import/export   Topic List   < Prev Topic  |  Next Topic >
Reply | Forward  |  Next Message > 
RE: [global_mapper] Re: Polish format import/export

I took a look at this and discovered that indeed the MARINE=Y attribute was
not being added in all cases as it should have been for features with the
3-byte attributes. I have placed a new build at
http://www.globalmapper.com/global_mapper11.zip with this fixed for you to
try. Simply download that file and extract the contents into your existing
v11.xx installation folder to give it a try. If you are using the 64-bit
version, there is a new build available at
http://www.globalmapper.com/global_mapper11_64bit.zip .



Let me know if I can be of further assistance.



Thanks,



Mike

Global Mapper Support

support@...



From: global_mapper@yahoogroups.com [mailto:global_mapper@yahoogroups.com]
On Behalf Of dasorsan
Sent: Monday, October 26, 2009 1:27 PM
To: global_mapper@yahoogroups.com
Subject: [global_mapper] Re: Polish format import/export





Ok ok, now i understand what you mean and i think i can define exactly what
is my problem. Maybe im doing somethig wrong but in my case, GM doesnt
recognize 0x01**** or 0x1***** as MARINE=Y

Copy this small polish format map in notepad and save it as map.mp. Then
open it with GM. If i have understood you, both element of the map below
should be MARINE=Y for GM but they are is just MARINE=N... am i missing
something?

; Generated by GPSMapEdit 1.0.57.3

[IMG ID]
CodePage=1252
LblCoding=9
ID=12345678
Name=test map
Preprocess=F
TreSize=1024
TreMargin=0.00000
RgnLimit=1024
POIIndex=Y
Levels=4
Level0=24
Level1=23
Level2=22
Level3=21
Zoom0=0
Zoom1=1
Zoom2=2
Zoom3=3
[END-IMG ID]

[POLYLINE]
Type=0x10e14
EndLevel=2
Data0=(41.64801,2.74740),(41.64880,2.74740),(41.64880,2.74761),(41.64889,2.7
476)
[END]

[POLYGON]
Type=0x010f0a
EndLevel=2
Data0=(41.64775,2.74725),(41.64817,2.74480),(41.64887,2.74497),(41.64876,2.7
462)
[END]





[Non-text portions of this message have been removed]




Mon Oct 26, 2009 8:06 pm

global_mapper
Offline Offline
Send Email Send Email

Forward
 |  Next Message > 
Expand Messages Author Sort by Date

Hi You are right, all garmin 3 bytes types (marine or custom) begins with 0x01****,so it seems that we could ignore the 01, but i'll try to explain what...
dasorsan
Offline Send Email
Oct 26, 2009
5:31 pm

I'm not quite sure I follow you. Whenever GM sees a 3-byte type starting with 0x01 it should import it with the lower 4 digits as the type and set MARINE=Y, so...
Global Mapper Support
global_mapper
Offline Send Email
Oct 26, 2009
6:30 pm

Ok ok, now i understand what you mean and i think i can define exactly what is my problem. Maybe im doing somethig wrong but in my case, GM doesnt recognize...
dasorsan
Offline Send Email
Oct 26, 2009
7:27 pm

I took a look at this and discovered that indeed the MARINE=Y attribute was not being added in all cases as it should have been for features with the 3-byte...
Global Mapper Support
global_mapper
Offline Send Email
Oct 26, 2009
8:06 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help