Re: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[Nelson A. de Oliveira]

On Sat, Feb 27, 2016 at 5:44 PM, greg crago  wrote:
> I want to download sections of the osm database (USA- Michigan) and make off
> line changes in JOSM and upload back to OSM when I am back online.

Will you edit the whole state?
Do you really need to have all of it?

Editing large areas and a lot of objects isn't usually the best thing
to do: it can cause duplicate data in OSM and/or you will hit a lot of
conflicts.

overpass is the easiest way to get fresh data, but you need to filter
a smaller region or some specific data that you want.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[greg crago]

I want to download sections of the osm database (USA- Michigan) and make
off line changes in JOSM and upload back to OSM when I am back online.

I looked at Overpass API and it looks like HUGE sections of data (32GB?)
How can I download smaller sections like
http://download.geofabrik.de/north-america.html is laid out?

Greg

On Sat, Feb 27, 2016 at 2:20 PM, Nelson A. de Oliveira 
wrote:

> On Sat, Feb 27, 2016 at 4:12 PM, greg crago  wrote:
> > I thought 20 hour old data was fairly recent data.
>
> What exactly do you want to do?
> Can't you take your data from overpass?
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[Nelson A. de Oliveira]

On Sat, Feb 27, 2016 at 4:12 PM, greg crago  wrote:
> I thought 20 hour old data was fairly recent data.

What exactly do you want to do?
Can't you take your data from overpass?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[greg crago]

I thought 20 hour old data was fairly recent data.

I tried loading OSM data using JOSM, but it only allows a small window of
data.
Downloading OSM data from http://download.geofabrik.de/north-america.html
allows me to download large areas of my country and allows me to make edits
as I need to (offline) and does not force me to constantly be online in
order to download OSM data where I want to work.

Is there any other 'splitter' type program I can use to break up the larger
osm.pbf maps into smaller 10MB 'chunks' I can use with JOSM?

Can we change splitter to keep the version information so I can use it with
JOSM?

Greg

On Sat, Feb 27, 2016 at 12:26 PM, Gerd Petermann <
gpetermann_muenc...@hotmail.com> wrote:

> Hi Greg,
>
>
> yes, splitter removes the version info because it is meant as a tool for
> mkgmap.
>
> You should always load current data into JOSM when you plan to edit, else
> you
>
> may have to fix several conflicts.
>
>
> Gerd
>
>
>
>
> --
> *Von:* mkgmap-dev-boun...@lists.mkgmap.org.uk <
> mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von greg crago <
> gregcr...@gmail.com>
> *Gesendet:* Samstag, 27. Februar 2016 16:39
> *An:* Development list for mkgmap
> *Betreff:* [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old
> OSM data, maybe a SPLIITTER issue?
>
> I downloaded .a mapset (michigan-latest.osm.pbf) from
> http://download.geofabrik.de/north-america.html yesterday. The data is
> about 20 hours old.
> North America - Geofabrik
> 
> download.geofabrik.de
> Not what you were looking for? Geofabrik is a consulting and software
> development firm based in Karlsruhe, Germany specializing in OpenStreetMap
> services.
>
>
> I had to use SPLITTER r428 with this command:
>
> java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter-r428\splitter.jar
> --max-nodes=140 --mapid="1239"
> --geonames-file=\MKGMAP\cities15000.zip --description=MI-greg
> --max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf
>
> Since I could not load the entire Michigan 96MB file into JOSM r9329. The
> resulting file, 12390006.osm.pbf, is 10.8MB and I imported it into JOSM and
> copied a NODES tags to an underlying POLYGON and deleted the NODE and tried
> to upload to the OSM server and got this error message:
>
> "Uploading failed because the server has a newer version of one of your
> nodes, ways, or relations. Click Synchronize entire dataset to synchronize
> the entire local dataset with the server"
>
> It is possible that SPLITTER r428 is not preserving the dataset versions
> or is setting them all to 1 when they really have different versions (eg.
> 2,3,4)
>
> Greg
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[Gerd Petermann]

Hi Greg,


yes, splitter removes the version info because it is meant as a tool for mkgmap.

You should always load current data into JOSM when you plan to edit, else you

may have to fix several conflicts.


Gerd




Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Samstag, 27. Februar 2016 16:39
An: Development list for mkgmap
Betreff: [mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, 
maybe a SPLIITTER issue?

I downloaded .a mapset (michigan-latest.osm.pbf) from 
http://download.geofabrik.de/north-america.html yesterday. The data is about 20 
hours old.
North America - Geofabrik
download.geofabrik.de
Not what you were looking for? Geofabrik is a consulting and software 
development firm based in Karlsruhe, Germany specializing in OpenStreetMap 
services.



I had to use SPLITTER r428 with this command:

java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter-r428\splitter.jar 
--max-nodes=140 --mapid="1239" --geonames-file=\MKGMAP\cities15000.zip 
--description=MI-greg --max-areas="255" --no-trim --status-freq="600" 
michigan-latest.osm.pbf

Since I could not load the entire Michigan 96MB file into JOSM r9329. The 
resulting file, 12390006.osm.pbf, is 10.8MB and I imported it into JOSM and 
copied a NODES tags to an underlying POLYGON and deleted the NODE and tried to 
upload to the OSM server and got this error message:

"Uploading failed because the server has a newer version of one of your nodes, 
ways, or relations. Click Synchronize entire dataset to synchronize the entire 
local dataset with the server"

It is possible that SPLITTER r428 is not preserving the dataset versions or is 
setting them all to 1 when they really have different versions (eg. 2,3,4)

Greg
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Problem uploading data to JOSM wit 20 hour old OSM data, maybe a SPLIITTER issue?

[greg crago]

I downloaded .a mapset (michigan-latest.osm.pbf) from
http://download.geofabrik.de/north-america.html yesterday. The data is
about 20 hours old.

I had to use SPLITTER r428 with this command:

java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter-r428\splitter.jar
--max-nodes=140 --mapid="1239"
--geonames-file=\MKGMAP\cities15000.zip --description=MI-greg
--max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf

Since I could not load the entire Michigan 96MB file into JOSM r9329. The
resulting file, 12390006.osm.pbf, is 10.8MB and I imported it into JOSM and
copied a NODES tags to an underlying POLYGON and deleted the NODE and tried
to upload to the OSM server and got this error message:

"Uploading failed because the server has a newer version of one of your
nodes, ways, or relations. Click Synchronize entire dataset to synchronize
the entire local dataset with the server"

It is possible that SPLITTER r428 is not preserving the dataset versions or
is setting them all to 1 when they really have different versions (eg.
2,3,4)

Greg
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[greg crago]

Greg here,
Yes, I am using a TYP file. I have used up add TYP from 0x00-0x2f and was
trying to start using EXTENDED TYP numbers (0x1-)
When I used 0x1-0x10005) those lines were onlt 1 pixel wide in
BaseCamp. Visible yes, but not the way there were defined by my TYP file.
Dave sent me his EXTENDED TYP file and I am going to compare the TEXT
OUTPUT to my TEXT OUTPUT.

Maybe my TYP editor is not producing the correct TEXT format?

Greg

On Sat, Feb 27, 2016 at 9:17 AM, Minko  wrote:

> Gerd, I think you were confused addressing your reply to Dave, instead you
> should have replied it to Greg Crago.
> I find those discussions via mailing lists very confusing too.
> So question to Greg, are you using a TYP file? This should help to make
> those lines visible.
>
>
> --
>
> *Van: *"Gerd Petermann" 
> *Aan: *daveswarth...@gmail.com, "Development list for mkgmap" <
> mkgmap-dev@lists.mkgmap.org.uk>
> *Verzonden: *Zaterdag 27 februari 2016 13:39:06
> *Onderwerp: *Re: [mkgmap-dev] Anyone determine which linetypes are NOT
> visablein BaseCamp?
>
>
>
> Hi Dave,
>
>
> sorry, I think I got you wrong. I thought you don't use a TYP file.
>
> I guess I should have checked older posts before...
>
> So does that mean that you have lines defined in the TYP file as visible
>
> and still Basecamp doesn't show them ?
>
>
> Gerd
>
> --
> *Von:* mkgmap-dev-boun...@lists.mkgmap.org.uk <
> mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Dave Swarthout <
> daveswarth...@gmail.com>
> *Gesendet:* Samstag, 27. Februar 2016 13:06
> *An:* Development list for mkgmap
> *Betreff:* Re: [mkgmap-dev] Anyone determine which linetypes are NOT
> visable in BaseCamp?
>
> Huh? I can define the width of a way, its color, whether it is dashed or
> solid in my TYP file. Are you saying I don't need a TYP file to make a
> dashed, brown line of width 5 pixels with hex code 0x1007 that is then
> assigned via a style rule to an OSM way?
>
> If I do not then I agree; I don't  understand anything about TYP files.
>
> Can you explain in a little more detail what you are trying to tell me?
>
>
> On Sat, Feb 27, 2016 at 4:45 PM, Minko  wrote:
>
>> See also http://www.openfietsmap.nl/tips-tricks/customize
>>
>> --
>>
>> Hi Dave,
>>
>>
>> it seems you don't understand the meaning of TYP file.
>>
>> It is used to define how POI / lines /  areas are displayed (in Basecamp
>> and the device).
>>
>> Such a file is not part of the mkgmap distribution, don't know why, maybe
>> the reason
>>
>> is that some devices don't support TYP files, maybe it's because
>> programmers aren't
>>
>> much interested in it ;-)
>>
>> You can find samples in other wellknown styles, e.g. here:
>>
>> https://github.com/ligfietser/mkgmap-style-sheets
>>
>> which contains the styles used for Minkos cycling maps:
>>
>> http://www.openfietsmap.nl/home
>>
>> I don't know if this page is up to date, but it may help as well:
>>
>> http://www.openfietsmap.nl/procedure
>>
>>
>> Gerd
>>
>>
>> ___
>> mkgmap-dev mailing list
>> mkgmap-dev@lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>
>
>
> --
> Dave Swarthout
> Homer, Alaska
> Chiang Mai, Thailand
> Travel Blog at http://dswarthout.blogspot.com
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[Minko]

Gerd, I think you were confused addressing your reply to Dave, instead you 
should have replied it to Greg Crago. 
I find those discussions via mailing lists very confusing too. 
So question to Greg, are you using a TYP file? This should help to make those 
lines visible. 

- Oorspronkelijk bericht -

> Van: "Gerd Petermann" 
> Aan: daveswarth...@gmail.com, "Development list for mkgmap"
> 
> Verzonden: Zaterdag 27 februari 2016 13:39:06
> Onderwerp: Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable
> in BaseCamp?

> Hi Dave,

> sorry, I think I got you wrong. I thought you don't use a TYP file.

> I guess I should have checked older posts before...

> So does that mean that you have lines defined in the TYP file as visible

> and still Basecamp doesn't show them ?

> Gerd

> Von: mkgmap-dev-boun...@lists.mkgmap.org.uk
>  im Auftrag von Dave Swarthout
> 
> Gesendet: Samstag, 27. Februar 2016 13:06
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in
> BaseCamp?
> Huh? I can define the width of a way, its color, whether it is dashed or
> solid in my TYP file. Are you saying I don't need a TYP file to make a
> dashed, brown line of width 5 pixels with hex code 0x1007 that is then
> assigned via a style rule to an OSM way?

> If I do not then I agree; I don't understand anything about TYP files.

> Can you explain in a little more detail what you are trying to tell me?

> On Sat, Feb 27, 2016 at 4:45 PM, Minko < ligfiet...@online.nl > wrote:

> > See also http://www.openfietsmap.nl/tips-tricks/customize
> 

> > > Hi Dave,
> > 
> 

> > > it seems you don't understand the meaning of TYP file.
> > 
> 

> > > It is used to define how POI / lines / areas are displayed (in Basecamp
> > > and
> > > the device).
> > 
> 

> > > Such a file is not part of the mkgmap distribution, don't know why, maybe
> > > the
> > > reason
> > 
> 

> > > is that some devices don't support TYP files, maybe it's because
> > > programmers
> > > aren't
> > 
> 

> > > much interested in it ;-)
> > 
> 

> > > You can find samples in other wellknown styles, e.g. here:
> > 
> 

> > > https://github.com/ligfietser/mkgmap-style-sheets
> > 
> 

> > > which contains the styles used for Minkos cycling maps:
> > 
> 

> > > http://www.openfietsmap.nl/home
> > 
> 

> > > I don't know if this page is up to date, but it may help as well:
> > 
> 

> > > http://www.openfietsmap.nl/procedure
> > 
> 

> > > Gerd
> > 
> 

> > ___
> 
> > mkgmap-dev mailing list
> 
> > mkgmap-dev@lists.mkgmap.org.uk
> 
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 

> --
> Dave Swarthout
> Homer, Alaska
> Chiang Mai, Thailand
> Travel Blog at http://dswarthout.blogspot.com

> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[Gerd Petermann]

Hi Dave,


sorry, I think I got you wrong. I thought you don't use a TYP file.

I guess I should have checked older posts before...

So does that mean that you have lines defined in the TYP file as visible

and still Basecamp doesn't show them ?


Gerd


Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von Dave Swarthout 

Gesendet: Samstag, 27. Februar 2016 13:06
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in 
BaseCamp?

Huh? I can define the width of a way, its color, whether it is dashed or solid 
in my TYP file. Are you saying I don't need a TYP file to make a dashed, brown 
line of width 5 pixels with hex code 0x1007 that is then assigned via a style 
rule to an OSM way?

If I do not then I agree; I don't  understand anything about TYP files.

Can you explain in a little more detail what you are trying to tell me?


On Sat, Feb 27, 2016 at 4:45 PM, Minko 
mailto:ligfiet...@online.nl>> wrote:
See also http://www.openfietsmap.nl/tips-tricks/customize



Hi Dave,


it seems you don't understand the meaning of TYP file.

It is used to define how POI / lines /  areas are displayed (in Basecamp and 
the device).

Such a file is not part of the mkgmap distribution, don't know why, maybe the 
reason

is that some devices don't support TYP files, maybe it's because programmers 
aren't

much interested in it ;-)

You can find samples in other wellknown styles, e.g. here:

https://github.com/ligfietser/mkgmap-style-sheets


which contains the styles used for Minkos cycling maps:

http://www.openfietsmap.nl/home

I don't know if this page is up to date, but it may help as well:

http://www.openfietsmap.nl/procedure


Gerd

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[Dave Swarthout]

Huh? I can define the width of a way, its color, whether it is dashed or
solid in my TYP file. Are you saying I don't need a TYP file to make a
dashed, brown line of width 5 pixels with hex code 0x1007 that is then
assigned via a style rule to an OSM way?

If I do not then I agree; I don't  understand anything about TYP files.

Can you explain in a little more detail what you are trying to tell me?


On Sat, Feb 27, 2016 at 4:45 PM, Minko  wrote:

> See also http://www.openfietsmap.nl/tips-tricks/customize
>
> --
>
> Hi Dave,
>
>
> it seems you don't understand the meaning of TYP file.
>
> It is used to define how POI / lines /  areas are displayed (in Basecamp
> and the device).
>
> Such a file is not part of the mkgmap distribution, don't know why, maybe
> the reason
>
> is that some devices don't support TYP files, maybe it's because
> programmers aren't
>
> much interested in it ;-)
>
> You can find samples in other wellknown styles, e.g. here:
>
> https://github.com/ligfietser/mkgmap-style-sheets
>
> which contains the styles used for Minkos cycling maps:
>
> http://www.openfietsmap.nl/home
>
> I don't know if this page is up to date, but it may help as well:
>
> http://www.openfietsmap.nl/procedure
>
>
> Gerd
>
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>



-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] splitter r428 : work-around for JOSM problem

[schlenn]

I use splitter in combination with osm2mp. Unfortunately osm2mp cannot read pbf 
files. So usually I don't need to edit the files, but nevertheless need xml 
output.

So an option V0.5 or V0.6 would be perfect. Or just add osmconvert to the 
documentation.

Von meinem iPad gesendet

> Am 26.02.2016 um 12:09 schrieb Gerd Petermann 
> :
> 
> Hi Andrzej,
> 
> my concern is more about the 12% when unzipped. I think 
> the only good reason to use the osm.gz format is that one
> whants to edit the file(s), and I searched a while to find editors
> which can handle huge files without problems. Maybe today that
> is no longer a problem.
> 
> Gerd 
> 
> 
> Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
>  im Auftrag von Andrzej Popowski 
> 
> Gesendet: Freitag, 26. Februar 2016 11:45
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] splitter r428 : work-around for JOSM problem
> 
> Hi Gerd,
> 
> 2% of planet.osm is about 650MB, I can live with it ;)
> 
> If you have doubts, than maybe add an option?
> 
> --
> Best regards,
> Andrzej
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] when I use SPLITTER to IMPORT om.pbf files into JOSM I get error

[schlenn]

Hi,

They said that they disabled Api V0.5 since JOSM r7013 because V0.6 is out 
since 2009 and there should be no reason to still support V0.5. 

See https://josm.openstreetmap.de/ticket/9975

osmconvert is a good option. From my point of view it would be also ok to stay 
at V0.5 and add the osmconvert workaround to the documentation.

Von meinem iPad gesendet

> Am 26.02.2016 um 08:23 schrieb Gerd Petermann 
> :
> 
> Hi Michael,
> 
> 
> yes, JOSM seems to expect metainfo (version, userid, last change timestamp) 
> and fails to read 
> a pbf file without that info. No idea why, but I've added a workaround in 
> splitter r428 right now.
> 
> 
> I was not aware that JOSM requires version 0.6 now, how crazy is that ? 
> Instead of using an editor you can use osmconvert:
> 
> osmconvert --fake-version  -o=output.osm
> 
> I hesitate to change splitter in this case because the extra information 
> increases the osm.gz files
> 
> by ~2% . I'd first like to understand why JOSM doesn't allow api version 0.5 
> anymore.
> 
> 
> Gerd
> 
> 
> 
> 
> Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
>  im Auftrag von Michael Schlenstedt 
> 
> Gesendet: Freitag, 26. Februar 2016 07:38
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] when I use SPLITTER to IMPORT om.pbf files into 
> JOSM I get error
>  
> Hi Gerd,
> 
> I also struggled around with this incompatibility splitter/JOSM. I used 
> XML-files, but JOSM does not support API V0.5 for quite a while now, and 
> splitter still produces v0.5 XML files.
> 
> Dirty Workaround: I open all yml-file in an editor, changed Line 2 into "osm 
> version='0.6'" and add "version='1'" to all id-instances. For VIM: :%s/ id='/ 
> version='1' id='/g
> 
> Maybe that's also the reason why JOSM doesn't like the PBF-files...
> 
> Regards,
> Michael
> 
> 
>> Am 25.02.2016 um 23:46 schrieb Gerd Petermann:
>> Gerd Petermann wrote
>> > Hi Greg.
>> > 
>> > 
>> > You can use osmconvert which should be able to read the output of
>> > splitter, e.g.
>> > 
>> > osmconvert 12360002.osm.pbf -o=12360002-josm.osm.pbf
>> 
>> Sorry, was too quick. 
>> You probably need option --fake-version for osmconvert:
>> osmconvert  --fake-version 12360002.osm.pbf -o=12360002-josm.osm.pbf
>> 
>> I think that's the reason for the problem: JOSM doesn't like input
>> in pbf format that doesn't have the meta info (version, author etc)
>> 
>> I never cared about that because I use o5m format and an o5m plugin that
>> I wrote once for JOSM. It is not in the plugins repo, but I may try again to
>> add 
>> it there.
>> 
>> A 3rd alternative is to use --output=xml in splitter, the files in that
>> format are
>> no problem in JOSM, but may decrease performance in splitter and mkgmap.
>> 
>> Gerd
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://gis.19327.n5.nabble.com/when-I-use-SPLITTER-to-IMPORT-om-pbf-files-into-JOSM-I-get-error-tp5868501p5868511.html
>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>> ___
>> mkgmap-dev mailing list
>> mkgmap-dev@lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[Minko]

See also http://www.openfietsmap.nl/tips-tricks/customize 

- Oorspronkelijk bericht -

> Hi Dave,

> it seems you don't understand the meaning of TYP file.

> It is used to define how POI / lines / areas are displayed (in Basecamp and
> the device).

> Such a file is not part of the mkgmap distribution, don't know why, maybe the
> reason

> is that some devices don't support TYP files, maybe it's because programmers
> aren't

> much interested in it ;-)

> You can find samples in other wellknown styles, e.g. here:

> https://github.com/ligfietser/mkgmap-style-sheets

> which contains the styles used for Minkos cycling maps:

> http://www.openfietsmap.nl/home

> I don't know if this page is up to date, but it may help as well:

> http://www.openfietsmap.nl/procedure

> Gerd
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in BaseCamp?

[Gerd Petermann]

Hi Dave,


it seems you don't understand the meaning of TYP file.

It is used to define how POI / lines /  areas are displayed (in Basecamp and 
the device).

Such a file is not part of the mkgmap distribution, don't know why, maybe the 
reason

is that some devices don't support TYP files, maybe it's because programmers 
aren't

much interested in it ;-)

You can find samples in other wellknown styles, e.g. here:

https://github.com/ligfietser/mkgmap-style-sheets


which contains the styles used for Minkos cycling maps:

http://www.openfietsmap.nl/home

I don't know if this page is up to date, but it may help as well:

http://www.openfietsmap.nl/procedure


Gerd


Von: mkgmap-dev-boun...@lists.mkgmap.org.uk 
 im Auftrag von greg crago 

Gesendet: Samstag, 27. Februar 2016 01:19
An: daveswarth...@gmail.com; Development list for mkgmap
Betreff: Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in 
BaseCamp?

Dave, do your linetype have any 'thickness'. I tried with 0x10001-0x10005 and 
only got razor thin lines visible in BaseCamp v4.6.1

Greg

On Fri, Feb 26, 2016 at 6:26 PM, Dave Swarthout 
mailto:daveswarth...@gmail.com>> wrote:
I am using line types 0x1 through 0x1001b for various lines and they all 
display in BC and on my Montana. 0x1 and 0x10001 are the oneway arrows that 
display alongside ways that are oneway. Of course, I have the styles defined in 
my lines file and the hexadecimal codes are in a custom TYP file.

Hope this helps.

Dave

On Fri, Feb 26, 2016 at 5:16 AM, greg crago 
mailto:gregcr...@gmail.com>> wrote:
Thank you, that worked well.

In BaseCamp v4.6.1 linetype 0x17,0x2c,0x30-0x3f are NOT VISIBLE.

Attached is a map that I changed all COLORS for lines and polygons to RED, 
except for the background container 0x4b is white. This map is located NE of 
London

The Garmin Montana 600 can see linetypes 0x00-0x3f and polygons 0x01-0x7f

Has anyone got EXTENDED linetype to be visible in BaseCamp? I used 
0x10001-0x10005 but they show up as thin lines only (no thickness)

Greg

On Thu, Feb 25, 2016 at 10:09 AM, Gerd Petermann 
mailto:gpetermann_muenc...@hotmail.com>> wrote:

Hi Greg,


try this command:

java -jar mkgmap.jar test-map:all-elements


to generate a map containing all possible types for lines and poi.


Gerd



Von: 
mkgmap-dev-boun...@lists.mkgmap.org.uk
 
mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>>
 im Auftrag von greg crago mailto:gregcr...@gmail.com>>
Gesendet: Donnerstag, 25. Februar 2016 15:57
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Anyone determine which linetypes are NOT visable in 
BaseCamp?

I realize that not all linetypes are visible in all GPS units.

Since map development is easiest when I can see my results quickly, using 
BaseCamp is a great tool to see my results without having to download .img 
files to my GPS every 10 minutes.

Do any of you 'mappers' have a TEST MAP file containing ALL POSSIBLE LINETYPES 
so I can use it and view in BaseCamp, or any GPS device to determine a USEFUL 
SET of visible LINETYPES. I think this would be a good to for mappers to have, 
otherwise, every time you want to add a new linetype, you have to see if it is 
visible in BaseCamp (or whatever software you are using) AND you need to verify 
that linetype is also visible in  your GPS unit.

I realize this 'test area' would have to exists in 1 location in the world, but 
you could make in the the ocean somewhere and just give coordinates so other 
mappers can find it.

Has anyone else determined additional non visible linetypes in BaseCamp besides 
0x17,0x31,0x32 and 0x34?

Greg

On Thu, Feb 25, 2016 at 8:48 AM, Andrzej Popowski 
mailto:po...@poczta.onet.pl>> wrote:
Hi Greg,

there is no consistency in a way Garmin's devices display different objects. 
Even if you see something in BaseCamp it doesn't mean that this object will be 
visible on nuvi or outdoor device.

There are some informations for meaning of objects (poi, lines, areas), which 
you can find on some web pages, for example:
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Polyline_Types
http://wiki.openstreetmap.org/wiki/Editing_OSM_Map_On_Garmin/Area_Types

As a general rule I suggest to follow description in cGPSmapper manual:
http://cgpsmapper.com/manual.htm

Usually maps contain a TYP file, which define graphics for objects. This 
somehow unify map view for different devices. I think TYP allows for viewing 
some objects, that otherwise would be invisible.

--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk