Hi Nick,

maybe that works as well, can't try it now. If not, use two steps. The two step
variant is possibly faster, as it requires less memory.

Gerd

nwillink wrote

Hi Gerd

How does  it know which TYP file applies to which option?

-index typ1.typ  --gmapsupp typ2.typ

does this work?

Nick

On 04/04/2015 18:52, GerdP [via GIS] wrote:
> Hi Nick,
>
> I see no reason why this would not work. AFAIK the TYP file is only
> copied
> into the gmapsupp.
>
> Gerd
>
>     nwillink wrote
>     Hi Gerd
>
>     Yes, you can do that , but both gmapsupp and the imgs use ONE and the
>     same typ file
>
>     You can't specify one TYP file for gmapsupp and another for the
>     imgs in
>     the same run , or can you?
>
>
>
>     On 04/04/2015 18:33, GerdP [via GIS] wrote:
>     > Hi Nick,
>     >
>     > maybe I don't understand the problem, but I think you can
>     compile the
>     > tiles
>     > once to create the gmapsupp and use
>     > java -jar mkgmap --nsis --index  ... *.img xyz.TYP
>     > for the Basecamp version.
>     >
>     > Gerd
>     >
>     >     nwillink wrote
>     >     Perhaps I'm the only person who uses 2 typ files for the
>     same map:
>     >
>     >     one  for Basecamp/Mapsource ,another for my gps device
>     >
>     >     I always seem to be compromising my colour palette and line
>     widths
>     >     to accommodate my device and yet I'm always creating my
>     routes on
>     >     Basecamp.
>     >
>     >     So, at present, I'm having to compile the osm twice, once for
>     >     Basecamp and once for my Oregon.
>     >
>     >     I wonder if it were possible to include a new option, ie
>     >     --gmapsupp_typ=
>     >
>     >     I've tried replacing the TYP file within the gmapsupp but there
>     >     are so many entries to alter.
>     >
>     >     Any thoughts?
>     >
>     >     Nick
>     >
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     > discussion below:
>     >
>     http://gis.19327.n5.nabble.com/mkgmap-2-TYP-files-tp5839762p5839763.html
>     > To unsubscribe from mkgmap & 2 TYP files?, click here
>     >
>     < >     <
>
>     > NAML
>     >
>     <http://gis.19327.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>     <http://gis.19327.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml%3E>
>
>     >
>
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the
> discussion below:
> http://gis.19327.n5.nabble.com/mkgmap-2-TYP-files-tp5839762p5839766.html
> To unsubscribe from mkgmap & 2 TYP files?, click here
> <
> NAML
> <http://gis.19327.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
>

---

If you reply to this email, your message will be added to the discussion below:

http://gis.19327.n5.nabble.com/mkgmap-2-TYP-files-tp5839762p5839769.html

To unsubscribe from mkgmap & 2 TYP files?, click here.
NAML