Re: [Talk-us] Proposed small import of UTA bus stops
On 22/apr/2013, at 02:55, Martijn van Exel m...@rtijn.org wrote: Paragraph 5 states: 'UTA grants You a limited, revocable license to use, reproduce, and redistribute UTA’s Web Services API (“Data”) in accordance with the terms of this section if the permission to distribute is revocable we shouldn't incorporate the data... cheers, Martin ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed small import of UTA bus stops
On 4/22/13 4:08 AM, Martin Koppenhoefer wrote: On 22/apr/2013, at 02:55, Martijn van Exel m...@rtijn.org wrote: Paragraph 5 states: 'UTA grants You a limited, revocable license to use, reproduce, and redistribute UTA’s Web Services API (“Data”) in accordance with the terms of this section if the permission to distribute is revocable we shouldn't incorporate the data... this is one of the reason's i'm not looking at bringing in any of the local transit authority data here in Albany, their open license includes a clause about reserving the right to change it at any time, and to require anyone redistributing the data to transmit the revised license terms to everyone who has taken a copy. not even remotely acceptable for OSM. richard ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed small import of UTA bus stops
COUNTY -- is_in:county CITY -- is_in:city ACCESS -- wheelchair = yes|limited|no BENCH -- bench = yes|no LOCATIONID -- uta:stop_id This looks good - I'm also glad that you also included the shelter tag in the data because that's useful. Re: is_in*; it seems to be redundant because the nodes should be actually located in those admin boundaries. The normal argument for using is_in applies if a highway spans beyond its normal boundary, such as a state highway spanning into another state.That might be true for this data, where a stop in one city is under another's city's transportation organization (but I'm not sure of the meaning of is_in for that case). Are the bus stops identified by the LOCATION_ID? That is, is the traveling public aware of those numbers; for example texting that number from a sign to get the delay until the next arriving bus time? If so, I'd argue for including those as a name instead of database ID. There's also a line of thought that says the database ID is not generally useful for point data because if people add and remove nodes manually, updated data sets still need to be conflated by location. Some decent node conflation scripts now exist, but I haven't used them. I'd also recommend tagging for both old and new transportation tagging schemes: highway=bus_stop public_transport=platform Some software finds it easier to support the new scheme because the layout makes more sense, while some renders only support the old scheme. Also, I saw some extra translation applied: tag k='is_in:city' v='Salt Lake is_in:city' / and Park City Regards, Mike ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed small import of UTA bus stops
On Sat, Apr 20, 2013 at 11:44 PM, Martijn van Exel m...@rtijn.org wrote: Hi all, During the edit-a-thon today I finally got around to working on preparing a relatively small import of bus stop point data for the UTA service area Try to guess my topic of interest. :-) So, Martijn, tell me about their license. :-) If I've found the appropriate page and license, [1] and if I'm reading it correctly, this data in not suitable for inclusion in OpenStreetMap, because of the license. Specifically: - an appropriate statement, reflecting this disclaimer be used on all products using SGID geospatial data as a source, and that a currency date and stewardship credit for the data be included on the map; and [1] http://gis.utah.gov/about/data-policies/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed small import of UTA bus stops
On 04/21/2013 06:47 PM, Richard Weait wrote: On Sat, Apr 20, 2013 at 11:44 PM, Martijn van Exel m...@rtijn.org mailto:m...@rtijn.org wrote: Hi all, During the edit-a-thon today I finally got around to working on preparing a relatively small import of bus stop point data for the UTA service area Try to guess my topic of interest. :-) So, Martijn, tell me about their license. :-) If I've found the appropriate page and license, [1] and if I'm reading it correctly, this data in not suitable for inclusion in OpenStreetMap, because of the license. Specifically: * an appropriate statement, reflecting this disclaimer be used on all products using SGID geospatial data as a source, and that a currency date and stewardship credit for the data be included on the map; and [1] http://gis.utah.gov/about/data-policies/ Good question. gis.utah,gov is not the owner of this data though, they merely act as a redistributor. UTA's license is here, although I am not quite sure it also pertains to their data: http://developer.rideuta.com/TermsOfUse.aspx Paragraph 5 states: 'UTA grants You a limited, revocable license to use, reproduce, and redistribute UTA’s Web Services API (“Data”) in accordance with the terms of this section. You must present the Data with the following legend, prominently displayed: Route and departure data provided by permission of UTA unless otherwise agreed by UTA in writing.' [...] I will get clarification from their legal team that our intended use is in concordance with our license. Martijn -- Martijn van Exel ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
