[talk-ph] Planned import: 7-Eleven Branch data

[Eugene Alvin Villar]

For branch=* vs. name:branch=*, there's already a proposal to use the
plain branch=* key name: http://wiki.openstreetmap.org/wiki/Key:branch

As for ref=*, while this is normally added to highways, ref=* can be
used for anything where it makes sense such as ID numbers and
reference codes. See this: http://wiki.openstreetmap.org/wiki/Key:ref


On Thu, Oct 4, 2012 at 10:25 PM, Rally de Leon <ralleon at gmail.com> wrote:
> (I think this was asked before already)
>
> In case the import pushes through, what tag should osmph formally
> adapt for the branch name for those chain-establishments, "branch" or
> "name:branch"?
> (eg. Banks, Pharmacies, Fastfood Chains, 24/7 Convenience Stores, Gas
> Stations, Utility Companies)
>
> I think an issue was raised before, that tag "branch" was already in
> use somewhere in Europe to refer to a "transportation line/route" or
> something (can't remember). I don't know if it was adapted or dropped.
> So to prevent future conflict, I already used "name:branch" in some of
> my edits.
>
> Although I'm in favor of plain "branch" since it's easier to type, but
> we should make a formal proposal/inquiry with the other communities
> (especially if we have a substantial number of establishment-branches
> in PH to tag)
>
> Regarding "ref="  for use in connection with 7-Eleven branches, you'll
> notice that the banks also uses branch codes. I would love to have
> this info on osm if allowed (since it may be internal info to the
> bank). Sometimes, it can be useful when tracking your payments if
> somebody ask you to deposit an amount to a particular bank, given only
> an account number and a name. Some branch-name tend to be very long
> (eg. Taytay-Manila East Road), compared to a branch code which is
> normally a 3 or 4 digit numeric. who knows if someday, somebody can
> find useful search apps for this.
>
> But I'm more inclined to use another tag (other than "ref") since it's
> already used on "highway" (although it's a line, not a node). Can this
> complicate things when filtering info for existing mobile apps (eg.
> unpredictable rendering)? what if we just use "branch_code" or
> "branch:code" (more specific, but longer to type). some may say it has
> no practical use to majority of the map users, but so is the ICAO (4
> letter alphanumeric code for airports) :-)
>
> +1 for branch name and +1 for branch codes for all chain establishments
>
> I suggest we ask permission from these companies (for the masterlist &
> its periodic updates). It is in their best interest that all their
> branches become searchable via internet, particularly when mobile
> using osm maps.
>
>
> On Thu, Oct 4, 2012 at 8:03 PM, ianlopez <ian_lopez_1115 at yahoo.com> wrote:
>> I'm planning to import location data of 7-Eleven branches nationwide in the
>> coming weeks. Based on a file that I found on the Internet Archive Wayback
>> machine, the location master containing the name of its branches and
>> location ID's (and other unrelated data)[0] is (presumably) licensed under
>> CC BY 3.0 PH. However, I'm not sure of its current status. It would be best
>> if we send an email to Philippines Seven Corporation regarding this matter.
>>
>> If imported, a typical 7-Eleven branch will have the following tags:
>>
>> name=7-Eleven
>> shop=convenience
>> opening_hours=24/7
>> branch=(name of branch in the location master)
>> ref=(location ID of branch)
>> source=(to be discussed)
>>
>> [0] http://web.archive.org/web/20100612175639/http://van.7-eleven.com.ph/