03-02-2012 01:15 AM - edited 14-02-2012 09:30 PM
I've created this topic to reach out to our Owner Community to note and discuss your experiences, questions and suggestions for improvement and any other aspect in the use of Map Share Reporter. Would appreciate any input here relevant to MSR and most certainly from experienced users but not only.
Please keep the topic clear of data queries and the like; we can deal with these much easier in a separate topic or continuing posts in a relevant topic in the list. Reason why I ask this is that the topic title will be immediately recognisable to another member here and browsers and I hope the posts here will be able to assist where assistance is needed.
Solved! Go to Solution.
03-02-2012 08:55 PM
04-02-2012 02:44 PM
it also doesn't play nicely with Safari on Mac. I use Firefox instead, without any problem.
04-02-2012 03:00 PM
I already wrote it in some other thread, but as this is now the place to collect our ideas and suggestions, I copy my wishes for MSR here:
1. It should always use the latest maps PLUS the accepted changes coming from other users.
2. It should show where other users have made corrections which are "pending" or have not been accepted
3. For the instances where corrections have not been accepted, a short note WHY this happened would be very useful.
4. Map details such as speed limits, POIs etc. should be visible on the Mapshare Reporter map, so that we can correct the easily
5. For countries using non-latin alphabets for street signage, the Reporter must allow the input of street names/POIs in local alphabet AND with latin characters. For example, I could easily provide many street names in my region in Greece, but cannot do it because the Reporter does not have a second field for street names in a different alphabet.
6. There should be an "express lane" for critical changes, where Tomtom guarantees the verification within a week, so that the change will be incorporated into the next map update.
7. the Reporter should allow users to upload data that allow for a quick verification - such as gpx tracks.
8. the reporter should show coordinates, and allow users to put their report to exact coordinates.
9. if at all possible (legally, that is), the Reporter should offer overlays of aerial/satellite images on the maps, to make reporting (and verification!) easier.
10. the Reporter should issue a receipt of each report, if the user wants it, that contains a reference number and details of the report (coordinates, type of correction...)
04-02-2012 04:08 PM
04-02-2012 04:47 PM
06-02-2012 10:48 AM - edited 06-02-2012 10:48 AM
I just stumbled over two more points that should be changed in MSR:
1. Street categories should be shown, and we should be enabled to correct them. Sometimes dirt tracks are categorized as paved streets or vice versa, or small roads are categorized higher than bigger ones that are signposted as the "official" way to go from A to B.
2. "Blocking" or "unblocking" streets MUST be possible at any point on the street. Quite often roads are blocked at one specific point, e.g by a security fence or a physical constriction, making them kind of dead-end, but NOT one-way streets. Thus, we should be able to pinpoint the block exactly, rather than "blocking" or "unblocking" the whole street.
06-02-2012 11:31 AM - edited 14-02-2012 09:31 PM
Yes and on your second point, it is VERY important to locate such closures at exactly the real boundary fence between properties and (advise or) comment as such. One would not like to place such a point in a manner that a house owner be routed into the closed-off section on the opposing side of the closure if you get my drift
.
06-02-2012 12:28 PM
08-02-2012 08:44 PM - edited 14-02-2012 09:31 PM
Have a look at my reply to TomTomista - covers this particular issue - this comment is, strictly seen, out of the topic here so let's try hard to list improvements and/or suggestions as to how Map Share Reporter can be improved based on your experience-in-use.
