Re: [Talk-us] Mapcarta with wrong info in Utah - whom to contact?
They appear to be pulling straight from Google, which is probably driving a whole lot more traffic to that telephone number than MapCarta: https://www.google.com/maps/place/Eagles+Campground/@41.2627649,-111.6961183,17.5z/data=!4m5!3m4!1s0x8753a519e0bdd163:0x85fa260f95cdae2a!8m2!3d41.2637729!4d-111.6944602?hl=en On Wed, Aug 26, 2020, at 4:14 PM, Frederik Ramm wrote: > Hi, > > does anyone have contacts with Mapcarta? > > https://mapcarta.com/Eagles_Campground_2422656 > > lists a camp ground that is not on OSM, and has never been, together > with a phone number that belongs to the USDA forest service and they're > not super stoked about would-be campers calling them to book. > > MapCarta claims to be using OpenStreetMap data (hence why the USDA > forest service contacted us). But clearly this campground comes from a > different source. (Which is just as well because Mapcarta doesn't have > proper attribution.) > > (The phone number in question was indeed recorded for a different camp > site in Utah, Monte Cristo Campground, and I've removed it from there. > Doesn't solve the Eagles Campground riddle though.) > > Mapcarta doesn't have any point of contact on the site and the whois > doesn't return anything useful either. > > Bye > Frederik > > -- > Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Mapcarta with wrong info in Utah - whom to contact?
https://mapcarta.com/About_Mapcarta lists a contact email address: m...@imedia.io. On Wed, Aug 26, 2020 at 3:16 PM Frederik Ramm wrote: > Hi, > > does anyone have contacts with Mapcarta? > > https://mapcarta.com/Eagles_Campground_2422656 > > lists a camp ground that is not on OSM, and has never been, together > with a phone number that belongs to the USDA forest service and they're > not super stoked about would-be campers calling them to book. > > MapCarta claims to be using OpenStreetMap data (hence why the USDA > forest service contacted us). But clearly this campground comes from a > different source. (Which is just as well because Mapcarta doesn't have > proper attribution.) > > (The phone number in question was indeed recorded for a different camp > site in Utah, Monte Cristo Campground, and I've removed it from there. > Doesn't solve the Eagles Campground riddle though.) > > Mapcarta doesn't have any point of contact on the site and the whois > doesn't return anything useful either. > > Bye > Frederik > > -- > Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Mapcarta with wrong info in Utah - whom to contact?
Hi, does anyone have contacts with Mapcarta? https://mapcarta.com/Eagles_Campground_2422656 lists a camp ground that is not on OSM, and has never been, together with a phone number that belongs to the USDA forest service and they're not super stoked about would-be campers calling them to book. MapCarta claims to be using OpenStreetMap data (hence why the USDA forest service contacted us). But clearly this campground comes from a different source. (Which is just as well because Mapcarta doesn't have proper attribution.) (The phone number in question was indeed recorded for a different camp site in Utah, Monte Cristo Campground, and I've removed it from there. Doesn't solve the Eagles Campground riddle though.) Mapcarta doesn't have any point of contact on the site and the whois doesn't return anything useful either. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Potential Import of Addresses for Thurston County, WA, USA
It might work, although it opens some wiki questions. I mean, at some point somewhere, I am gonna have to put probably on the wiki that thurston county gave permission to use the data so that we have it for future records. On Wed, 2020-08-26 at 03:08 -0700, Pat Tressel wrote: > One option for both including the attribution and also not having to > worry about future mappers editing it, and hence needing to be warned > to remove an attribution, is to put the attribution in the changeset > comments, rather than in a tag. Or, to use a tag, include some > boilerplate with the attribution that says it was originally from XYZ > but they are not responsible for later changes. > > When they say changed, do they mean just the material map data -- > points, polygons, addresses? If so, removing their tags / metadata > would not constitute a change under that definition of change. > > (Semi-off-topic: Note that for a different project, if we imported > external data, we *wanted* the metadata. In particular, we wanted > any dataset / table primary key or identifier, *in case we had to > update the record with changes from the same dataset* -- we wanted to > match up the record we had with a modified record in the original > source. Likewise, if we had a change on our end, that needed to be > pushed back to the original source -- we'd need the identifier for > that as well.) > > -- Pat > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] [Imports] Potential Import of Addresses for Thurston County, WA, USA
One solution might be to modify the dataset then provide some upload of the modified dataset as the source? My understanding is that yes it could. The goal is that they do want to be seen as responsible if we modify the data in any way that is incorrect, nor do they want us to represent them in any official capacity. On Wed, 2020-08-26 at 06:07 +0200, Mateusz Konieczny via Imports wrote: > Is specifying source in changeset > or on import page on Wiki qualifying > as crediting them? > > Because doing this is actually required. > > > 26 Aug 2020, 02:07 by thekingofrav...@disroot.org: > > Alright I have an update: > > > > After an email chain with Thurston County GeoData Center, I finally > > got > > explicit permission to use the data in open street map. > > > > "Hello Raven, > > > > You can use the data in Open Street Maps and credit GeoData UNLESS > > you > > change the data in any way. If you change the data you can still > > use it > > in Open Street Maps but CANNOT credit GeoData and the County. We > > make > > no warrantees about the data temporally, spatially, or in terms of > > attribution. > > > > Please let me know if this helps to clarify the disclaimer or if > > you > > still have questions. > > > > Thank you! > > > > Leslie Carman > > GIS Analyst I" > > > > I can provide the entire email chain if required but this is the > > part > > that matters. As for the terms they gave me, what is the best way > > of handling this? My instinct is just to, in some very minor way, > > ensure every piece of data is modified somehow so future mappers do > > not have to worry about it. Does just adding it to OSM count as > > modification, since we convert the data fields? > > > > At this point, I would like to propose that we import this data, as > > this includes rural towns and unincorporated thurston > > county. > > I would divide the building footprints into small blocks to avoid > > well > > mapped areas. > > As for addresses, because they are points and there are so few > > addresses in my region, I feel like we could be more aggresive > > about > > that import, although how much so I am not certain. > > > > > > Also @Clifford Snow if you see this I would appreciate whatever you > > have to teach about imports. > > > > Sincerely, > > Raven > > > > > > ___ > > Talk-us mailing list > > Talk-us@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/talk-us > > ___ > Imports mailing list > impo...@openstreetmap.org > https://lists.openstreetmap.org/listinfo/imports ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
