TYP files collection

**catymag** · 20th July 2013, 11:14 AM

@Roger
May be it's like in CNEUR (Michel's reply in post n17) ?

The TYP files of CNEUR doesn't contain any polygon, polyline or POI but a very long DrawOrder list. So, all the polygons ( if they are listed in the DrawOrder) all the polylines and all the POI are displayed according to default settings of the rendering engine (i.e. Basecamp,Mapsource or the firmware of the GPS unit).

**Roger** · 20th July 2013, 11:39 AM

@ Catymag

+ or -

For CNNTEU yes, but with POIs

For CNNT(U)EU no...it's almost "full"

Bye,bye

**sherco40** · 24th July 2013, 12:33 AM

@ Roger & catymag

This typ file (I000B6D.TYP) is very light , compared with CNNTEU :only 375 ko. It doesn't contain any Polygon, Polyline , POI ,ExtraPoi , only a long list of Special labels ..

@Roger
CNNTEU typ file doesn't contain POI : it only contains ExtraPois (it is not the same object and, AFAIK, no one knows how to add ExtraPoi to a map...)

**Cnfhbr** · 24th July 2013, 12:55 PM

Originally Posted by sherco40

it is not the same object and, AFAIK, no one knows how to add ExtraPoi to a map...

Most likely, the source shapefile of the ExtraPOIs contains additional attribute (BRAND_ID) as against standard POIs, see [Only registered and activated users can see links. ] and [Only registered and activated users can see links. ]

Kanopus · 24th July 2013, 01:41 PM

All compute well:
0x1FF*32 + 0x18 = 16376
0x1FF*32 + 0x15 = 16373

So it is rather brand ID than type/subtype value.

**Cnfhbr** · 24th July 2013, 07:40 PM

You can try to play around with the BRAND_ID attribute on the input of MPC. The creation of these ExtraPOIs is absent in Help of MPC, but there are a lot of warnings in the bowels of the program, for example:

- brand id does not fit in calculated size

- brand id required bits does not fit in 5 bits, % ERROR!

- ERROR: size calc mismatch on Yellow Pages POI brand id

- Invalid max brand ID value detected! Max brand ID cannot be smaller then the base brand ID!

etc.

P.S. The "Special Labels" in the TYPViewer is likely to "brand list" according to terminology of MPC.

**jamie oliver** · 25th July 2013, 01:13 AM

Originally Posted by kidgasosa

Does anyone have the "typ" file of the Topo Portugal Ciclonatur V5?

Regards

typ file

[Only registered and activated users can see links. ]

Note by MOD: Thanks I copied your post in this 3rd and join your file TYP in post of TOPO TYPs

**sherco40** · 25th July 2013, 01:30 AM

@ cnfhbr
Yes, you are right!

What I have called "Type" and "SubType" for ExtraPOI are not their type and subtype.

I have made some tests after reading your post and it appears that ExtraPOI do have type and subtype, but these type and subtype do not appear in the section "ExtarPOI" of the typ file.
ExtraPOI have another identifier that corresponds to what you see in MPC Viewer, and this is that identifier that appears in the section "ExtraPOI" of a typ file.
So, in TYPViewer I will correct this and call this identifier "Brand ID" instead of "Type" and "Subtype".

The tests I have made , show that if the ExtraPOI of the map is not in the typ file (i.e. not in the POI section AND not in the ExtraPOI section) the ExtraPOI is displayed with the default icon according to its type and subtype, if there is a POI of this type/subtype, the ExtraPOI is displayed with the icon of this POI and if there is an ExtraPOI with its brand ID in the typ file, the ExtraPOI is displayed with the icon of the ExtraPOI of the typ file.

For example, near my home there is a supermarket named "Leclercq" and in CNNTEU it is represented with an ExtraPOI with Type/Subtype 10f/02 and Brand ID 007/1D ( i.e.253 in decimal) and the icon is a big "L".
If in the typ file there is no POI 10f/02 AND no ExtraPOI with Brand ID of 253 , then the Garmin default icon for GROCERY_STORE is displayed.
If the typ file contains a POI 0x10f/02 BUT DOES NOT contain an ExtraPOI with Brand ID of 253 , the icon of this POI is displayed.
If the typ file contains an ExtraPOI with Brand ID of 253, the icon of this ExtraPOI ( i.e. the big "L" ) is displayed, no matter if there is a 10f/02 POI in the typ file.

So Brand ID seems to be like an identifier of a subcategory that has priority on POI.

One question: is it better to note the brand ID with one integer between 0 and 65536 or with to integers, one for the first 5 bits and the second for the 11 next bits ? One of the errors you have encountered deals with a number of 5 bits... so maybe it is worth to separate the Brand ID in two...

For the Special Labels, it seems that I have to rename them "Brand list" in TYPViewer...

**Cnfhbr** · 25th July 2013, 12:39 PM

Originally Posted by sherco40

So Brand ID seems to be like an identifier of a subcategory that has priority on POI.

I think so, too.

Originally Posted by sherco40

One question: is it better to note the brand ID with one integer between 0 and 65536 or with two integers, one for the first 5 bits and the second for the 11 next bits ? One of the errors you have encountered deals with a number of 5 bits... so maybe it is worth to separate the Brand ID in two...

These values I'd like to see in a form that is used to write values to the BRAND_ID attribute in source shapefile, but I still cannot insert brand ID into the map via MPC. Values, such as 16373, 16376, ... are not compiled into .img file. Perhaps the MPC does not support the creation of ExtraPOIs at all.

Originally Posted by sherco40

For the Special Labels, it seems that I have to rename them "Brand list" in TYPViewer...

This is just my timid assumption based on the strings found in MPC distro, such as:

- The packing size of brand list table is not correct
- Non-Aux Brandlist brand count bit size of %d exceeds %d bits
- Non-Aux Brandlist brand id bit size of %d exceeds %d bits
- Non-Aux Brandlist feature subclass bit size of %d exceeds %d bits
- Non-Aux Brandlist feature class bit size of %d exceeds %d bits
- Aux Brandlist brand count bit size of %d exceeds %d bits
- Aux Brandlist brand id bit size of %d exceeds %d bits
- Aux Brandlist feature subclass bit size of %d exceeds %d bits
- Aux Brandlist feature class bit size of %d exceeds %d bits
- Feature type is not supported for packing brand list table
- Brand list record bit size cannot be 0. We should have at least one brand list record to pack
- Packing brand list for Auxiliary point feature...
- Packing brand list for point feature...

Perhaps need additional confirmation of this ...

**sherco40** · 25th July 2013, 02:42 PM

Originally Posted by Cnfhbr

Apart from this I'd rather not lose type/subtype values for the ExtraPOIs in TYPViewer.

What do you mean?
In fact, types and subtypes of ExtraPOI are not present in the typ file and so are not present in TYPViewer.
What I had called type/subtype are in fact Brand ID.

Thread: TYP files collection

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions