Hello Carles, I don't think there is really an active mailing for London unfortunately. To track London related event, it is best to look at the wiki page as it is where most people are going. #osm-gb is a good area too. I would suspect you may want to be in #osm-dev too. Be aware that the community can be a bit harsh at times but it shouldn't discourage you :) DWG is the data working group. They are the group that looks at data and whether to revert data issues, prevent edit wars etc... As for the different workflow, you are welcome. I think it would be the easiest ultimately for you and less likely to get the community to ask what your source:pkey is in the first place.
Emilie Laffray On Wed, Dec 3, 2014 at 3:50 PM, Carles Pina i Estany <car...@pina.cat> wrote: > > Hi Emilie, > > I like your variation of my workflow - I think that I'll implement this > variation. I'm aware that the POI ID might change but as you said this > could have happened using my workflow. Thank you for the idea. > > I'll read DWG and ask if needed there, I wasn't aware of them. I'm > slightly new to the OSM project. > > You said "this mailing list is very very low volume (probably the first > email in years that I have seen).". Where is the best place for > London-related OSM events? (usually I see them on Twitter or #osm-gb IRC > channel). Sadly I've only attended once so far... > > Regards, > > On Dec/03/2014, Emilie Laffray wrote: > > Hello Carles, > > > > There is no definite way regarding the use of source:pkey and source in > > general but I believe that it is better to add the source to the > > transaction in this case. Source could be added to the POI in itself. > > Regarding automated push to OpenStreetMap, I would make sure that you > have > > a mechanism to roll back specific POI if required because you are always > at > > risk of having someone entering potentially bad data in OSM. I would > > recommend discussing with the DWG for better advice. > > I believe your logic should be revisited as I don't see why you would > need > > to store your id in OSM in the first place. I would probably use the > > following flow instead: > > a) We receive a POI from the user and then we add in our database (so > it's > > available to ourselves) > > b) We regularly push the POIs to OSM (using the API) > > c) When the API returns the id of the POI pushed, I update my database > with > > OSM id > > d) When we update OSM (once a week, automatic process): we should remove > > from our DBs the POI that already exists in OSM > > > > Effectively roughly the same logic that you suggested except you don't > > export your own id and rely on OSM ids. Please be aware that relying on > ids > > can be difficult in OSM in the first place as you are never sure that > they > > may not change (Someone can delete it and recreate it). This is also true > > for your own ids if you import in OSM (someone can easily remove it and > > they will once they will realize it is an external id). I would argue > that > > using OSM id would make your app slightly more resistant in the first > place. > > > > By the way, this mailing list is very very low volume (probably the first > > email in years that I have seen). > > > > Emilie Laffray > > > > On Wed, Dec 3, 2014 at 3:22 PM, Carles Pina i Estany <car...@pina.cat> > > wrote: > > > > > > > > Hello, > > > > > > TL;DR: I'd like to use source:pkey=xxx and source=app_name to remove > > > local POIs that I create to OSM. Is this the correct way to do it? Or > > > should I do something else? (e.g. fuzzy matching by location :-( ) > > > > > > Longer explanation: > > > > > > If this is not the the right list to ask this question please let me > > > know - and I'll go to the correct place, apologies. I write to the > > > London one because is where I live. > > > > > > Friend of mine and I are preparing an app that will use OSM map and > > > data. We want to contribute back to OSM and I have a question regarding > > > the workflow. > > > > > > The app will show some POIs and at least a few people will be > > > able to add POIs that doesn't exist at the moment (let's assume that > > > only trusted people will be able to add POIs, people that know how OSM > > > works and the consequencies of adding POIs). > > > > > > I've been thinking of doing something like: > > > a) we receive a POI from the user and then we add in our database (so > > > it's available to ourselves) > > > b) regularly we push the POIs to OSM (using the API) > > > c) when we update OSM (once a week, automatic process): we should > remove > > > from our DB the POIs that already exists in OSM. > > > > > > I thought to tag the POIs that we create with source:pkey=$ID and > > > source=name_of_app (this is similar to what it says on > > > http://wiki.openstreetmap.org/wiki/Osmsync webpage). > > > > > > My question: what's the policy of using source:pkey=$ID, > source=app_name > > > ? Can be used this way or not recomended to be used this way. > > > > > > Thank you, > > > > > > -- > > > Carles Pina i Estany > > > Web: http://pinux.info || Blog: http://pintant.cat > > > GPG Key 0x8CD5C157 > > > > > > _______________________________________________ > > > Talk-gb-london mailing list > > > Talk-gb-london@openstreetmap.org > > > https://lists.openstreetmap.org/listinfo/talk-gb-london > > > > -- > Carles Pina i Estany > Web: http://pinux.info || Blog: http://pintant.cat > GPG Key 0x8CD5C157 > > _______________________________________________ > Talk-gb-london mailing list > Talk-gb-london@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb-london >
_______________________________________________ Talk-gb-london mailing list Talk-gb-london@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb-london
