a section of 401hwy, Ontario not rendered

[Aleksandar Mićić]

This is the problematic section, properly rendered, as shown by default online OSM render:

http://www.openstreetmap.org/?lat=44.3971&lon=-75.9401&zoom=14&layers=M

Attached is the screenshot of Osmand rendering. Clearly, about 1km of hwy missing in NE direction and about 5km in opposite direction.

Not only rendering is incorrect, but offline router does not see the section either. So, could be more a problem with ontario.obf file!? I noticed a problem months ago, and since than it was always the same with various versions of Osmand and issues of ontario.obf

This a major Ontario highway, and would be really good if this could be fixed....

And one more problem not directly related, but again affecting Ontario (and a few other provinces in Canada). Rawindex link is broken (getting 404 error):
http://download.osmand.net/download.php?file=Canada_ontario_northamerica_2.obf.zip

Regards,
Aleks

[Aleksandar Mićić]

In original post I embedded the screenshot, but I was not able to see it after I read the post. So I'm trying again, not embedding, but just as an attachment.

[Harry van der Wolf]

Hi,

The embedded image doesn't work when sending it to these kind of web based systems. Embedded images get reencoded to a base64 ASCII-7 string.

2013/6/8 Aleksandar Mićić <micic.al...@gmail.com>

There are two OBFs for Canada_Ontario. If you download via the official site, and not a driect link, you would have seen that the map has grown and is now so big that it extends to two zip files, like
http://osmand.googlecode.com/files/Canada_ontario_northamerica_2.obf.zip-1
and
http://osmand.googlecode.com/files/Canada_ontario_northamerica_2.obf.zip-2

That could possibly also be the reason for the incorrect rendering. Or did you download Ontario from within OsmAnd?

Harry

[Aleksandar Mićić]

HI Harry,

yes I noticed that obf has grown into two files (from Osmand), but I did not realize it affected the web link above. Could the links in http://download.osmand.net/rawindexes/ be updated (I can live with it, but for future users)?

As for rendering/routing problem.... I downloaded obf from within Osmand. I cannot tell for sure, if that is related or not to this file split. I could be wrong, but from what I remembered, the problem was observed before the file was split.

Thanks for the quick response.
Aleks

[Harry van der Wolf]

Hi,

The Ontario polygon is not correct. see attached (low quality) image.
The purple line is the border, the straight gray line is the polygon (outside border) as used to create the Ontario map. It's simply cutting of part of Ontario.
I have corrected the polygon and uploaded it to OpenStreetMap.org, but I have no idea how and when it will be incorporated into OsmAnd. But you can of course do that yourself using osmconvert and OsmAndMapCreator. I attached the canada_ontario.poly as well for that purpose.

About the raw indexes: I have no influence on that. I assume someone from the DEV team has to do that.

Harry

[Aleksandar Mićić]

Ok, I see, nothing wrong with OsmAnd (kind of what I suspected) but Ontario obf file was left out some  OSM data that actually belongs to Ontario.

So, I assume,  the sole purpose of that way you updated (http://www.openstreetmap.org/browse/way/224942110) is to surround actual relation of province/state/region (http://www.openstreetmap.org/?relation=68841 in this case) for obf file generation.

If so, how is this way identified/recognized by obf file generator (ie. how do i find appropriate way for any other country/province)? And somewhat releated small thing that I am confused is version (1) of the way . Appears like you introduced a new one instead of updating an existing one...

Nice and quick finding (although, I'll just wait for new obfs to be autogenerated). Thanks a lot, again.

Aleks

[Harry van der Wolf]

Hi,

2013/6/9 Aleksandar Mićić <micic.al...@gmail.com>

Ok, I see, nothing wrong with OsmAnd (kind of what I suspected) but Ontario obf file was left out some  OSM data that actually belongs to Ontario.

So, I assume,  the sole purpose of that way you updated (http://www.openstreetmap.org/browse/way/224942110) is to surround actual relation of province/state/region (http://www.openstreetmap.org/?relation=68841 in this case) for obf file generation.

Yes, exactly.

However, the changeset as such is incorrect. It doesn't contain the correct way/relation (meta)data. It's now an empty non-related polygon. I have reverted it (sigh).
But on the other hand: I sent the poly also to geofabrik so that they can update their dataset.
 

If so, how is this way identified/recognized by obf file generator (ie. how do i find appropriate way for any other country/province)? And somewhat releated small thing that I am confused is version (1) of the way . Appears like you introduced a new one instead of updating an existing one...

Nice and quick finding (although, I'll just wait for new obfs to be autogenerated). Thanks a lot, again.

The original map is actually an xml describing what's in the map.  It's not "recognising" something. It "simply" copies the xml data inside the polygon. The programs used to create maps based on these polygons, "simply" take whatever is in the polygon and generate a map for that "cut out" part of the OSM map.

On land you want to have your polygon as narrow as possible as you pick something with it from the other neighbouring country like, in this case, New York.
So the map of Ontario might include some 100-800 meters of the New York map, and the New York map might incorporate some 100-800 meters of the Ontario map. This data is then actually double rendered in any navigation app.


Harry
 

[Harry van der Wolf]

The Ontario poly will be added to the geofabrik.de dataset tonight. I assume that the next OsmAnd Ontario map will be correct.

Harry