On Mon, Nov 28, 2011 at 12:45:30AM +0100, Olaf Hasemann wrote:
>#def and #undef is IMO not so useful at all, cause you allways are able
>to prevent the execution of a rule by catching the element within
>another rule given before the rule you want to 'undef'.
You are right, the #undef would mere
Am Sonntag 27 November 2011, 15:34:31 schrieb Steve Ratcliffe:
> Hi
>
> >> indicates that they should be separated. They could be placed in one
> >> file, which would be used by each of the different geometry types.
> >
> > I agree, one file for these should be enough. I did not quite follow you
Hi,
ok, here is my last and final patch for the copyright/license
informations in MapSource/Basecamp/Garmin Device.
Works now for me in all cases I can test.
Thorsten
--
Thorsten Kukuk, Project Manager/Release Manager SLES
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff
Thanks Steve, I tested mkgmap-gmap-mdr-r2125.jar:
- Transparency in Basecamp: solved!
See http://img821.imageshack.us/img821/3453/gmap.jpg The map is bordered by a
thin blue line, which is normal. Underlying basemap is not visible anymore.
One issue: there is a small thin blue line within the ma
On 27/11/11 21:08, Minko wrote:
> Thanks Steve,
> Unfortunately I dont know how to compile a patched mkgmap so I can't test it,
> but this patch and a search index in gmapsupp is very good news!
OK I committed it to the branch, so you can get it from the download
page along with the address inde
Thanks Steve,
Unfortunately I dont know how to compile a patched mkgmap so I can't test it,
but this patch and a search index in gmapsupp is very good news!
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listi
Hi
The uderlying basemap is still visible through the osm map,
and the line style of this basemap is defined by the osm typ file.
We have noticed it does not occur with generated maps by cgpsmapper.
The attached patch fixes this.
..Steve
Index: src/uk/me/parabola/mkgmap/general/MapDetails.j
Hi
> I meant indeed gmapsupps created by Mapsource (because I need a working
> address index).
Perhaps this is a good time to mention the gmap-mdr
branch which is about making a working address index!
It is now in a working state, at least for single countries.
..Steve
Greg Troxel schrieb am 27.11.2011 17:12:
> I still don't understand why it would make sense to make a POI
> per node. What I'm getting at is that perhaps the line2poi code should
> somehow default to making only one synthetic point POI.
Below is an example from my points-style, where I generate i
Steve wrote:
>That flag is not set by mkgmap, unless I'm mistaking what is meant. Is
>this for ones created by mapsource?
Sorry, I didnt check what happens with gmapsupp.img's generated with mkgmap.
I meant indeed gmapsupps created by Mapsource (because I need a working address
index).
>As far
Minko writes:
> Greg wrote:
>> Can you explain when you want to have a POI for every node in a way? It
>> seems the area->POI code makes one POI for the closed way, and this is
>> different. (Not trying to be difficult; I really don't get it.)
> I use the add-poi-to-lines option only in a f
Hi
> By default the Ms (Mapsource) flag is set to 1 but you can set it to 0 with
> Gmaptool:
That flag is not set by mkgmap, unless I'm mistaking what is meant. Is
this for ones created by mapsource?
> I have tried it with my Openfietsmap and it worked. However I
> discovered that my map is tr
Hi
>> indicates that they should be separated. They could be placed in one
>> file, which would be used by each of the different geometry types.
>
> I agree, one file for these should be enough. I did not quite follow you
> regarding access tags. They do not matter for polygons, do they? For
> p
I use the add-poi-to-lines option only in a few cases (yet), and I don't use it
on every node either, but only in the middle of a road segment
(mkgmap:line2poitype=mid).
One example is on lines tagged with route=ferry & opening_hours=*
http://www.openstreetmap.org/browse/way/40326852
route=fe
14 matches
Mail list logo
