Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jurajs

#1
yeah....
i wasn't looking for some time... and i like what is going on here. thanks to everyone for wonderful progres.
the progres is so huge that i am going to give up all my activities on vector maps. at least for now ;-)

I will adjust the 1st post very soon.

hugs and kisses,
jurajs
#2
Maps / Re: Vector maps - library improvements
April 18, 2013, 22:17:25
yes... you are right... the speed is awfull... the speed could be improved for sure...
#3
Maps / Re: Vector maps - library improvements
April 18, 2013, 17:53:49
like (thumbs up)

one more humble question: what about mapwriter plugin ? ;-) ...are you expcting any progress also here ? the most recent one does not work with the newest osmosis(es) :-(
#4
hi joe.... France is missing at the moment... please be patient... I am trying to build brand new maps at the moment... but tihs can take few more days.... please check again in a week or so....

jurajs
#5
hi there guys....

i was going to create new bunch of maps.... and as i am looking around... i can see that new pyghtmap is out... also new osmosis.... but that bloody mapsfogre map-writer plugin is more than 1 year old... still on the 0.3.0  :-( so the latest possible osmosis here to use is still 0.40.1 ? am i right ? :-(

jurajs
#6
hi col...

i hope it will work for you now....
btw: using just view3 source should be enough. see post written by kech61 viewtopic.php?f=43&t=1839&p=14620&#p14620

J.
#7
well...

my humble guess is that it's problem of rendering... not the map data (including contour data).
I would say that there are simply too many rendered objects to be handled correctly by the mapsforge rendering library.

What about zooms 13... 14+? ... do you have the same "missing objects" problem too ?

and regarding the pyghtmap commnad... I have just one thing to point out here: whould you try to change "-c" values ? e.g. to 200,100 ? the purpose is that elevation_minor and elevation_medium are different.

J.
#8
hey.... you are so faaast reacting. it was missing there for just a flash of a second... right ?
....actually I am going to fix that right now ;) sorry tomas ;-)

but at least you will get the latest maps now.... :-)


edit
@tomas: all links should be valid now.

@all:
-almost all maps are freshly created.
-new map is added (GRE+ALB+CYP).
-map of France was not updated because i wasnt albe to figure it out at this moment.

viewtopic.php?f=43&t=1839#p11684
J.


edit
NEW VERSION OF PYGHTMAP (1.44) IS AVAILABLE...

http://katze.tfiu.de/projects/phyghtmap/download.html
#9
Maps / Re: [MAPS] - Vector maps
September 14, 2012, 13:22:33
I have just tested it.... It works perfectly...
sorry for dumb question, ...but are you totally sure you are using vector map at that particular moment ?
#10
thanks for checking....
well i'm going back to 0.40.1
#11
aaaa Christian ... help me out please....

was there any notable change in new osmosis 0.41 ? I am having trouble making maps with map-writer plugin with this new version. My configuration is the same as was for 0.40. I am confused and frustrated again :-(((
btw: old version is still working fine..

here is the full output:
sep 09, 2012 11:24:29 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.41
sep 09, 2012 11:24:30 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
sep 09, 2012 11:24:31 AM org.mapsforge.map.writer.osmosis.MapFileWriterTask <init>
INFO: mapfile-writer version: mapsforge-map-writer-0.3.0
sep 09, 2012 11:24:31 AM org.mapsforge.map.writer.osmosis.MapFileWriterTask <init>
INFO: mapfile format specification version: 3
sep 09, 2012 11:24:31 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Launching pipeline execution.
sep 09, 2012 11:24:31 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline executing, waiting for completion.
sep 09, 2012 11:24:31 AM org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion
SEVERE: Thread for task 1-rx failed
java.lang.AbstractMethodError: org.mapsforge.map.writer.osmosis.MapFileWriterTask.initialize(Ljava/util/Map;)V
        at org.openstreetmap.osmosis.xml.v0_6.XmlReader.run(XmlReader.java:95)
        at java.lang.Thread.run(Unknown Source)

sep 09, 2012 11:24:31 AM org.openstreetmap.osmosis.core.Osmosis mainSEVERE: Execution aborted.
org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks failed.
        at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
        at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:92)
        at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
#12
well...
ask then !... describe your attempts and failures ;-)
#13
you can define the contourline steps in phyghtmap easily... and for amount the meters you want to.
but ! you have to have in mind also that source elevation data is not continuos, therefore it does not make any sense to use lower values than 10 meters. I personally use 20 meter steps for contour lines for 2 reasons. 1) 20 or 25 steps are mostly used out there and its still detailed enough 2) to avoid enormous data generated by pyghtmap for contourlines in the map itself  (comparing to 10m step)
#14
Thanks for your reply Christian,

btw: i assume that the problem with rendering of water/sea areas is not solved yet by mapsforge directly... right ? I read the workaroud thread on mapsforge forum.... but my brain lacks mental capacity to implement the changes at this moment ;-)
#15
announce:
I will rebuild all maps in 1st post very soon.

attached is the current tag-mapping.xml.
can you guys have a look? any hints for improvements are welcome.