Map quality

[Zsolt Elite Voyager]

@Shorty: I reported a missing road today (ID: 29f97634-a9f0-102f-8665-e83f81ca73e1), but oddly MSR decided to relocate my pin, and dragged it to the nearest road, saying there is no road where I want to report. I am sure it is, my old window used to look at it for 20+ years, it is there ever since, and was there since around 1960. MSR shouldn't relocate the pin.

[Zsolt Elite Voyager]

@Shorty: I think there should be one or more zoom in level. Some street labels are either not visible, due to lack of space, otherwise those are all missing?

Is the MSR map updated to v885 as well?

[tulpie]

@Shorty  Is it possible to get more information on a report that is accepted. For example: the map version where the change will be effected, or that the change has been done via Mapshare updates

[Megalos Exalted Voyager Expert (Map quality)]

Excellent suggestions Tulpie. In some way,  these suggestions seem very familiar to me .

[Zsolt Elite Voyager]

There could be something like MSR, but like Map Pre-purchase Check Service. Many people are disappointed to buy a map, and finding out that the reported issues had not been implemented.

[fof]

Zsolt, as the MSR map is always at least one version behind the map on the devices (at least up to now, that may hopefully change some day), I would suggest you wait for the reported change to appear in MSR before you buy a map upgrade. That way, you can be sure that it has been implemented in the map you buy.

[Zsolt Elite Voyager]

I rather don't go into details, not in this topic at least. It is not the point fof

[Shorty]

Agreed - it's a question I still need a definitive answer on but I'm inclined towards fof's point even if the map in MSR is a few weeks behind release that would at least be better than now..

Just by way of summary of the list of suggestions so far [clearly would still need some refinement]

• A number of suggestions on an extended contributor feedback loop.  These may refer to MSR itself but also the the Map Releases themselves.  An indication as to whether such data will (normally) be in the update or ugrade or due timing unfortunately missed the cut off.
• MSR seems unhappy with Opera as Browser
• The MSR map should be the latest map version be it update -xx5 or upgrade -xx0 and should show data contributed and at the very start of the CFL with follow through reports until taken into the next map release (be that an update or an upgrade).  A week or two after a public release would be acceptable
• A description of ones personal favourites for POI of friends location and 'home' in a range of colours - these would follow a street address and not necessarily the street number.
• streetnames should be bi-lingual (at least) where 2 languages are spoken in the majority in that country [refers not only to MSR map but those formally released as well[]

• all the usual map attributes should show,, otherwise duplications of data can arise
• There should be an easier method to zoom in and out of the map and at the location chosen
• Consideration should be given to caravan towing and heavy vehicles when inclines (and declines) are signposted, allowing a suitable alternative 'escape'  - these categories of vehiclc retain posted limit but likely completely so for caravans irrespective of the rig)
• [this one's mine :smileywink]; a facility to make a indicative sketch of the boundaries of shopping centres, parks, industrial areas
• [another one of mine] POI icons should be designed in such a way that the nature of the POI is clear simply from the icon itself
• critical issues in map corrections should receive a priority over others [in a decided prioritastion -egg network change to an interchange; changed entrances to Emergency Access to a hospital; same for Police Stations and Emergency services - could be others]
• contributors data (opted in to Unit Map Share and/or using Mapshare off GPSr) must receive a priority in the production process in recognition of the personal nature being a donation of such contributions
• if possible, image overlays on MSR should be considered (without breaching legal codes &/arrangements)
• MSR should issue a receipt of data by GUID or some other identifiable tag so as queries where data may be pending for too long
• reasons should be given if a contribution is (eventually) not accepted.
• road categories should be shown (even in broad terms) to prevent a router taking one down a 'back road' instead of a using higher category.  Private roads should be carefully 'gated digitally' to prevent alternatives routes being chosen that use these roads.  The HD Traffic override should also not be allowed to use these alternatives as potential ways
• All closures, those requiring a digital gate and those open only at certain times should regarded officially as road closures but an owner would be able to override this at his/her decision where gates are known to be open during certain periods of the day.
• A measure of trust needs to be developed over pin locations contributed, that DO apply at the particular location and not elsewhere; a query should be raised if the digitiser is unsure, before entering such data 

So far so good for this time of a Saturday evening.

[Lupus1 Elite Voyager]

Hi,

just to give an example of how a more detailed feedback about MapShare reports could look like I've just gotten an image of a report I've made via MapInsight from Teleatlas sometime last year (25 October 2011) when MapShare Reporter still seemed to be not as well working as now.

For those of you not speaking German, the feedback marks are the following:

1. We've received your report.
2. We know about the problem.
3. We work on a solution.
4. The problem has been solved.

That information could be a bit more detailed especially if there's one step pending as to give information about why it's pending or if it's been rejected also some more information about why that has happened. With step 4 there could be implemented as to which map version it is probable that the changes are implemented.

Regards

Lars.

[fof]

one more improvement: It should be possible to delete/revoke changes for as long as they are not "accepted". I just saw that one of my reported changes is already in the 8.85 map, so my report that was based on map 8.80 is now "useless" and no-one from Tomtom has to spend time to care about it.
In other instances, people find out that they made mistakes. This happened to me, too, when I reported a missing street "leading westwards from this point", but meant "eastwards". I'd like to revoke or at least edit the wrong report.