Preventing the mature features modification
4 views
Skip to first unread message
Jabran
Nov 20, 2009, 3:29:29 PM11/20/09
to mapping-...@googlegroups.com
Hello Team and everyone,
I am starting a conversation where we can provide ideas about prevention or at least moderation of mature features modification done by *ANY* user including the creator. My idea could go with the recent "Review" tab that a certain number of positive review will lock/prevent the direct publishing of any further modification. For example, myself with some more people are on major roads rework in Pakistan at the moment but it is so frustrating to see when new users or some active mature users are just replacing the information to their personal need. Somehow I tried to keep an eye by keeping the whole country in neighborhood for moderation and changes made every day but it is very tiring procedure to go through each road modification/addition to see if the road is not the one which just has been fixed. An example of such work still can be seen on N-5 at various parts and in Karachi at major roads for now but there were many in recent past. Such features are taking so long time to rework for fixing and it is no good to see them getting ruined again and again. Please have your ideas and comments to keep the discussion for some positive outcome. Cheers
Ammar Ahmed
Nov 28, 2009, 1:45:39 PM11/28/09
to Map Your World - Mapping Pakistan
I agree. But there should be a way to make changes if there is eroor
in mature feature.
in mature feature.
Jabran
Nov 30, 2009, 4:03:21 PM11/30/09
to mapping-...@googlegroups.com
Yes of course. That's for we may need a system which passes such feature for moderation independent of modifier's level of trust or where original user will get a prompt for any changes made to such features. So far no interest from anyone else...
Ammar Ahmed
Dec 1, 2009, 11:57:21 AM12/1/09
to Map Your World - Mapping Pakistan
I am all for such a system of moderation. How you plan to propose this
to google.
On Dec 1, 2:03 am, Jabran <jabranrafi...@gmail.com> wrote:
> Yes of course. That's for we may need a system which passes such feature for
> moderation independent of modifier's level of trust or where original user
> will get a prompt for any changes made to such features. So far no interest
> from anyone else...
>
> Regards,
> جabran
>
> ------------------------www.dyzynz.nethttp://acknowledge-pakistan.blogspot.com
>
> 2009/11/28 Ammar Ahmed <ammar...@gmail.com>
to google.
On Dec 1, 2:03 am, Jabran <jabranrafi...@gmail.com> wrote:
> Yes of course. That's for we may need a system which passes such feature for
> moderation independent of modifier's level of trust or where original user
> will get a prompt for any changes made to such features. So far no interest
> from anyone else...
>
> Regards,
> جabran
>
> ------------------------www.dyzynz.nethttp://acknowledge-pakistan.blogspot.com
>
Jabran
Dec 1, 2009, 12:19:35 PM12/1/09
to mapping-...@googlegroups.com
They are reading everything here.. :)
Regards,
جabran
www.dyzynz.net
-----------------------
Sent from iPhone
Regards,
جabran
www.dyzynz.net
-----------------------
Sent from iPhone
JenMazz
Dec 2, 2009, 12:20:20 PM12/2/09
to Map Your World - Mapping Pakistan
Dear Jabran & Ammar,
Thank you for posting about this topic. In fact we do have the ability
to "lock down" features so they can't be edited further -- for example
country borders are not editable. It's an interesting idea to enable
mappers to request feature lock-down, and subsequently if needed un-
locking of a feature to make a correction. Of course if this process
were a manual one, it would not be scalable/feasible for our team to
implement. I'm interested in your additional thoughts.
Cheers,
Jen.
On Dec 1, 9:19 am, Jabran <jabranrafi...@gmail.com> wrote:
> They are reading everything here.. :)
>
> Regards,
> جabranwww.dyzynz.net
>
> -----------------------
> Sent from iPhone
>
Thank you for posting about this topic. In fact we do have the ability
to "lock down" features so they can't be edited further -- for example
country borders are not editable. It's an interesting idea to enable
mappers to request feature lock-down, and subsequently if needed un-
locking of a feature to make a correction. Of course if this process
were a manual one, it would not be scalable/feasible for our team to
implement. I'm interested in your additional thoughts.
Cheers,
Jen.
On Dec 1, 9:19 am, Jabran <jabranrafi...@gmail.com> wrote:
> They are reading everything here.. :)
>
> Regards,
> جabranwww.dyzynz.net
>
> -----------------------
> Sent from iPhone
>
Jabran
Dec 2, 2009, 1:25:06 PM12/2/09
to mapping-...@googlegroups.com
I was not talking about the ability to lock down a feature. I guess locking down a feature and then unlocking it for correction or addition of data will need certain conditions and reasons that why and on what basis it is been locked down. I am talking about a feature that not really locks the feature but it triggers a message to the original mapper about any kind of change with a link to contact the mapper making changes or at least put the feature in moderation state regardless of level of trust of this new mapper who makes any change..
Regards,
جabran
------------------------
www.local.com.pk
www.dyzynz.net
Regards,
جabran
------------------------
www.local.com.pk
www.dyzynz.net
KA
Dec 3, 2009, 5:02:45 AM12/3/09
to Map Your World - Mapping Pakistan
I'll find my self a bit in this discussion. any way.
but first about a derrived idea of Locking and Unlocking features with
any kind of certain conditions. I will not in favour of it. because
there are many Mappers I have seen with Huge Edits but False
Information/Locations/Edits. This feature will have more chances of
being miss-used by them if they are prefered to lock any thing.
I think it should remain with the team. or if you think there should
be some sort of conditions to make a mapper able to use this feature
to less the job of team. then I will vote for it only if the team
desides itself which Mapper is well suited to have this authority. but
not a system with pre-defined certain condtions.
secondly, the Idea of "Trigger to Original Mapper". I really have
thought of this idea, exactly. The modderation of such mature features
should be in place with no preference to the trust of a mapper. but it
should also be discussed to the original mapper to find out about the
new changes. but the priority should be given, in such cases, to the
Mapper most local to the feature.
thanks
Regards
KA
but first about a derrived idea of Locking and Unlocking features with
any kind of certain conditions. I will not in favour of it. because
there are many Mappers I have seen with Huge Edits but False
Information/Locations/Edits. This feature will have more chances of
being miss-used by them if they are prefered to lock any thing.
I think it should remain with the team. or if you think there should
be some sort of conditions to make a mapper able to use this feature
to less the job of team. then I will vote for it only if the team
desides itself which Mapper is well suited to have this authority. but
not a system with pre-defined certain condtions.
secondly, the Idea of "Trigger to Original Mapper". I really have
thought of this idea, exactly. The modderation of such mature features
should be in place with no preference to the trust of a mapper. but it
should also be discussed to the original mapper to find out about the
new changes. but the priority should be given, in such cases, to the
Mapper most local to the feature.
thanks
Regards
KA
Jabran
Dec 3, 2009, 5:30:08 AM12/3/09
to mapping-...@googlegroups.com
Locking unlocking is currently limited and only controlled by team.
Examle of Pakistan as country is locked for any modification of it's
border as there were users from both sides of border claiming the
border by modifying on personal choices. Also other examples are AJK
was locked due to similar on-going disputes. I provided some official
data and requested for replacing name of Gilgit-Baltistan and locking
the Chenab Nagar after replacing with official correct data. But this
all was done by team only after a series of emails and after providing
evidences. I also believe this feature should remain to authorized
people only but discussion carries on other thing of modifying a
mature feature.
However there is one thing to note that currently a feature is only
marked as mature after a certain time of period passed since it was
published and rendered.
Regards,
جabran
www.local.com.pk
Examle of Pakistan as country is locked for any modification of it's
border as there were users from both sides of border claiming the
border by modifying on personal choices. Also other examples are AJK
was locked due to similar on-going disputes. I provided some official
data and requested for replacing name of Gilgit-Baltistan and locking
the Chenab Nagar after replacing with official correct data. But this
all was done by team only after a series of emails and after providing
evidences. I also believe this feature should remain to authorized
people only but discussion carries on other thing of modifying a
mature feature.
However there is one thing to note that currently a feature is only
marked as mature after a certain time of period passed since it was
published and rendered.
Regards,
جabran
www.local.com.pk
nhk
Dec 7, 2009, 2:32:21 AM12/7/09
to Map Your World - Mapping Pakistan
Greetings
1- I think the present system has reasonable checks and balances and
is working quite OK. Putting locks on modifications will be counter
productive and not advisable. The changes and fine tuning of the Map
is a continuous process. Life itself is dynamic and ever changing -
and so is the terrain that supports life.
2- Features that seemed established & complete a year ago are still
continuously in the process of fine tuning due to imagery changes,
misalignment, addition of other features linked with old features etc.
Overall, the MAP is yet far from complete and wide gaps still exist.
3- The new Users do create some problems initially until they have
crossed about 500 edits. In their excitement, they are tempted to name
the road in front of their home on their name and classify it as
primary. But they soon grow out of this initial excitement and even
begin to correct their own earlier errors. We have to live with this
minor nuisance.
4- Keeping the Modification element under the existing restrictions
- and not locking it - is also desirable because new Users keep
cropping up from areas that were still not Marked/Named in detail.
These new Users from those specific Areas add the required information
on the nameless roads, towns and villages.
regards
On Dec 3, 3:30 pm, Jabran <jabranrafi...@gmail.com> wrote:
> Locking unlocking is currently limited and only controlled by team.
> Examle of Pakistan as country is locked for any modification of it's
> border as there were users from both sides of border claiming the
> border by modifying on personal choices. Also other examples are AJK
> was locked due to similar on-going disputes. I provided some official
> data and requested for replacing name of Gilgit-Baltistan and locking
> the Chenab Nagar after replacing with official correct data. But this
> all was done by team only after a series of emails and after providing
> evidences. I also believe this feature should remain to authorized
> people only but discussion carries on other thing of modifying a
> mature feature.
>
> However there is one thing to note that currently a feature is only
> marked as mature after a certain time of period passed since it was
> published and rendered.
>
> Regards,
> جabranwww.local.com.pkwww.dyzynz.net
>
> -----------------------
> Sent from iPhone
>
1- I think the present system has reasonable checks and balances and
is working quite OK. Putting locks on modifications will be counter
productive and not advisable. The changes and fine tuning of the Map
is a continuous process. Life itself is dynamic and ever changing -
and so is the terrain that supports life.
2- Features that seemed established & complete a year ago are still
continuously in the process of fine tuning due to imagery changes,
misalignment, addition of other features linked with old features etc.
Overall, the MAP is yet far from complete and wide gaps still exist.
3- The new Users do create some problems initially until they have
crossed about 500 edits. In their excitement, they are tempted to name
the road in front of their home on their name and classify it as
primary. But they soon grow out of this initial excitement and even
begin to correct their own earlier errors. We have to live with this
minor nuisance.
4- Keeping the Modification element under the existing restrictions
- and not locking it - is also desirable because new Users keep
cropping up from areas that were still not Marked/Named in detail.
These new Users from those specific Areas add the required information
on the nameless roads, towns and villages.
regards
On Dec 3, 3:30 pm, Jabran <jabranrafi...@gmail.com> wrote:
> Locking unlocking is currently limited and only controlled by team.
> Examle of Pakistan as country is locked for any modification of it's
> border as there were users from both sides of border claiming the
> border by modifying on personal choices. Also other examples are AJK
> was locked due to similar on-going disputes. I provided some official
> data and requested for replacing name of Gilgit-Baltistan and locking
> the Chenab Nagar after replacing with official correct data. But this
> all was done by team only after a series of emails and after providing
> evidences. I also believe this feature should remain to authorized
> people only but discussion carries on other thing of modifying a
> mature feature.
>
> However there is one thing to note that currently a feature is only
> marked as mature after a certain time of period passed since it was
> published and rendered.
>
> Regards,
> جabranwww.local.com.pkwww.dyzynz.net
>
> -----------------------
> Sent from iPhone
>
Jabran
Dec 7, 2009, 3:16:46 AM12/7/09
to mapping-...@googlegroups.com
Alright.. Thanks NHK for input. Guys!! The conversation is completely
out of track now and going in wrong side! Lets forget "locking"
because it's as mentioned in previous replies is not asked in this case.
MaiN point of discussion is to trigger an alert for creator/modifiers/
moderators. So they know about the changes made regardless of trust
level of that new modifier. I hope everyone gets the point! Map Maker
Guide, do you have anything to say about this idea? Cheers
Regards,
جabran
www.local.com.pk
out of track now and going in wrong side! Lets forget "locking"
because it's as mentioned in previous replies is not asked in this case.
MaiN point of discussion is to trigger an alert for creator/modifiers/
moderators. So they know about the changes made regardless of trust
level of that new modifier. I hope everyone gets the point! Map Maker
Guide, do you have anything to say about this idea? Cheers
Regards,
جabran
www.local.com.pk
nhk
Dec 7, 2009, 11:01:01 PM12/7/09
to Map Your World - Mapping Pakistan
Just for information, a lot of Tiles have been replaced East of Indus
in NWFP & Punjab. Not all the replaced Tiles are down to one Notch.
Most of them are down to 2-3 Notches which means that the features
earlier mapped on them have become misaligned and they can be deleted
and more accurately re-mapped. An example is patches between Kohat ,
Hangu and Doaba for both road and rail tracks.
regards
On Dec 7, 1:16 pm, Jabran <jabranrafi...@gmail.com> wrote:
> Alright.. Thanks NHK for input. Guys!! The conversation is completely
> out of track now and going in wrong side! Lets forget "locking"
> because it's as mentioned in previous replies is not asked in this case.
>
> MaiN point of discussion is to trigger an alert for creator/modifiers/
> moderators. So they know about the changes made regardless of trust
> level of that new modifier. I hope everyone gets the point! Map Maker
> Guide, do you have anything to say about this idea? Cheers
>
> Regards,
Map Maker
Dec 14, 2009, 7:27:51 AM12/14/09
to mapping-...@googlegroups.com
Hi Jabran,
I understand your point .. it would be great to keep track of all our edits to make sure nothing is being incorrectly changed. Denis has already added this as a feature enhancement : http://code.google.com/p/google-mapmaker/issues/detail?id=386
You might want to add your thoughts and vote up for that issue :)
Regards,
Map Maker Guide.
I understand your point .. it would be great to keep track of all our edits to make sure nothing is being incorrectly changed. Denis has already added this as a feature enhancement : http://code.google.com/p/google-mapmaker/issues/detail?id=386
You might want to add your thoughts and vote up for that issue :)
Regards,
Map Maker Guide.
On Mon, Dec 7, 2009 at 1:46 PM, Jabran <jabran...@gmail.com> wrote:
Alright.. Thanks NHK for input. Guys!! The conversation is completely out of track now and going in wrong side! Lets forget "locking" because it's as mentioned in previous replies is not asked in this case.
MaiN point of discussion is to trigger an alert for creator/modifiers/moderators. So they know about the changes made regardless of trust level of that new modifier. I hope everyone gets the point! Map Maker Guide, do you have anything to say about this idea? Cheers
Reply all
Reply to author
Forward
0 new messages