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

#46
hiking map theme v0.5

what's changed:
- motorways and trunks clearly visible also on lower zooms (e.g. <12)
- tunnels now overlaying some more areas (zoo, camp, parking, etc... )
- adjusted colors and fonts for highways
- fixed administrative boundaries
- changed military area pattern and added boundary lines
- some other bugs
#47
hiking map theme v0.4

what's changed:
- national park boundaries
- added fancy pinky transparent administrative boundaries
- vineyard areas added (+pattern)
- minor fixes
#48
maps are created according to this prefference already : view1,view3,srtm1,srtm3
#49
alps ready
#50
Hi Christian,

Glad to see you here ;-) I am sure indeed that your input will be valuable here.
I have already some perl scrips to convert gpx to poly, but as far i need to have .poly files as simple as possible, the way with gmaps along with editing kml to poly is sufficient and comfortable enough for my purpose ;-) thanks anyway.

p.s. welcome to locus community ;-)
#51
hi skids,

I have been experiencing similar issue when i was building my first map (Slovakia), and i tough that srtmfill utility is going to fix that for good. obviously is not. it's important to tell that this problem is caused by "invalid" srtm data.

possible causes/solutions:
1. it was my fault. that means i forgot to process one or more hgt files with srtmfill.
   - can you isolate the area where those hexagons are appearing? (in whole degrees e.g. N48-49 W002-004) so i can try to run the utility again.
2. if 1. is not the case, we should find some kind of tool with possibility to change the elevation data in hgt file manually. (and fix those bugs)
3. find another (better) source of srtm data to try.

jurajs
#52
new map of France is out

France 2012-05-09 (1391 MB): //https://docs.google.com/open?id=0B3Ijv5irWwU7OUhFNVkzNWQ1MG8
alps will be next...

please note that this is the first map generated with new "ruleset" (see 1st post for details) and better rendering for zooms 12-13. feel free to test it and give some feedback/bug report.
#53
Wishlist / Re: Zooming with an overlay
May 08, 2012, 20:30:38
+100
also some predefined overlays are welcome.
one more thing. when i set an overlay -> stop locus -> start locus -> no overlay. (bug? feature? am i doing something wrong?)
#54
checked...
the link for britain_ireland_iceland.ter.osm.map (https://docs.google.com/open?id=0B3Ijv5 ... 1llTlZCam8) is completely ok.
maybe you are proud owner of some bulletproof antivirus software? ... or hmmm...  :ugeek:
try to re-download or something ;-) maybe someone else can try it too and report the results...

j.
#55
let me check...
#56
Themes - Vector maps / Re: [Theme] Volatile
May 08, 2012, 18:00:15
hi joopiii,
i guess it's this one :
viewtopic.php?f=43&t=1877

j.
#57
here it is ....
#58
boze ja som blbec....

toto je urcite ta najlepsia rada:
samozrejme najjednoduchsie to budes mat ked si kupis tie mapy priamo v locuse cez locus shop  :mrgreen:
#59
well... Tom... you are like an angel... suddenly comes from nowhere and helped a lot ;-)
its still not perfect, but the improvement is visible indeed !
#60
That bloody osmosis is still "building"the map... I can't wait anymore to finally test it ;-)
but ....
I am in doubt if this is going to solve that issue ... (still hoping)
       <attribute name="force-polygon-line" type="boolean" default="false"></attribute>
        <attribute name="equivalent-values" type="string"
                use="optional">
                <annotation>
                        <documentation>
                                The usage of some tags such as "oneway" is quite
                                inconsistent in the OSM dataset. Expressions such as
                                "oneway=yes", "oneway=1" or oneway="true" are
                                semantically equivalent. This attribute allows to
                                associate these equivalent values to the single
                                canonical value defined in the "value-attribute".
                        </documentation>
                </annotation>
        </attribute>

hmmm...