Proposal:Addr:milestone
| Tag:addr:milestone | |
|---|---|
| Proposal status: | Proposed (under way) |
| Proposed by: | JAAS |
| Tagging: | addr:milestone=* |
| Applies to: |  
|
| Definition: | A tag on a node or polygon that captures the distance (in kilometers or miles) as it is used in a common address system found in rural areas. This distance is typically found on roadside markers (highway=milestone) and is a crucial part of the address. The value should be a numeric representation of the distance, with decimal numbers specified using a period (.). |
| Statistics: |
|
| Draft started: | 2019-09-25 |
| RFC start: | 2024-10-07 |
Proposal
This proposal seeks to introduce a new tag, addr:milestone=*, as a subkey of addr=*. This tag aims to capture a common address system prevalent in rural areas worldwide, where the distance (in kilometers or miles) from a starting point is used as part of the address.
Rationale
In many countries, especially in Latin America, Portugal, Spain, Italy, and the Philippines addresses in rural areas often rely on highway location markers (also known as mile-markers or highway=milestone). These markers, placed along highways, indicate the distance traveled from a specific starting point. This distance, expressed in kilometers or miles, becomes an integral part of the address for locations along these highways.
Currently, there is no suitable tag within OpenStreetMap's addr=* subkeys to accurately represent this type of address information. The proposed addr:milestone=* tag would fill this gap, providing a standardized way to capture this important data.
Examples
The image on the right shows a real-world example of an address using kilometers as part of its location description. The address is rendered as "KM 20.1" – the "KM" represents the distance marker, and "20.1" represents the distance in kilometers.
The image above shows another example of a "closed gated residential community" in Guatemala where the only way to locate these communities is by referencing the highway kilometer markings (highway=milestone).
These examples illustrate how addr:milestone=* is vital for accurately mapping addresses in these regions.
This warehouse rental's address uses the Km=10.8 to find it's location on a highway "near" Guatemala City, which has been already included in the OSM database -
Tagging
The addr:milestone=* tag should capture the distance information as a numeric value, with decimal numbers specified using a period (.).
Examples:
Metric System: addr:milestone=20.1, addr:milestone=18, addr:milestone=5.5.
Imperial System: addr:milestone=10 mi, addr:milestone=23 mi, addr:milestone=4.5 mi
The default unit is assumed to be kilometers (km). To specify a different unit, add a space after the number, then the unit abbreviation (e.g., 35.0 mi).
This tag can be used in conjunction with other relevant address tags, such as addr:street=* and addr:housenumber=*, to provide a complete address description. And since its value comes from a distance in a nearby highway, it is required that this highway is referred in the address (addr:street=*). For example:
addr:street=Highway 1
addr:milestone=20.1
Although in the majority of cases the addr:milestone=* value is equivalent to addr:housenumber=*, in some cases there are addresses with both values. In those cases, both tags can be used:
addr:street=Highway 1
addr:milestone=20.1
addr:housenumber=123
Applies to
This addr:milestone=* tag would contain additional address information commonly utilized on rural highways which utilize the highway=milestone as a reference, specifically the kilometer (or mile) information found as being a part of the address.
Rendering
The current form to indicate an address as a node or polygon will remain the same, without altering in any way the appearance which is currently in use.
Features/Pages affected
The addr=* page would need to be updated in order to add the new addr:milestone=* including the description for the proper usage.
External Discussions
This proposal was first made in 2019: https://lists.openstreetmap.org/pipermail/tagging/2019-October/thread.html#48489
After 5 years, the original author addressed all discussed points in diverse discussions, such as the one occurred in Nominatim: https://github.com/osm-search/Nominatim/issues/3541
Current Discussions
Here is a link to the current tagging mailing list discussion: [1]
RFC:https://lists.openstreetmap.org/pipermail/tagging/2019-October/thread.html#48489
Prior Discussions
As this is the second attempt to get this tag approved. Since the first attempt (in 2019) many editors around the world have already adopted the use of this tag and it's use has also been proposed for Nominatium.
Voting
- Log in to the wiki if you are not already logged in.
- Scroll down to voting and click 'Edit source'. Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
| To get this output | you type | Description |
|---|---|---|
|
{{vote|yes}} --~~~~
|
Feel free to also explain why you support proposal. |
|
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. |
|
{{vote|abstain}} comments --~~~~
|
If you don't want to vote but have comments. Replace comments with your comments. |
~~~~ automatically inserts your name and the current date.For full template documentation see Template:Vote. See also how vote outcome is processed.
I approve this proposal. --Kanpaidaisuki (talk) 02:04, 9 November 2024 (UTC) It is practically impossible to map "addr:housenumber" or "addr:street" in the middle of nowhere, it is impressive the amount of records of places like these, it is not a pain to process this tag, since it is mostly in places where it is not used with the other 2 tags mentioned.
- I approve this proposal. I understand that the value should an address part "as written" (verbatim, not interpreted). As a consequence, I believe that its format should not be defined to a precise pattern ("Km. ##" as given above). Instead, the mapper should replicate whatever is written in the given address. For an actual numeric value, add a highway=milestone at the corresponding location on the highway itself. --Dani CS (talk) 20:22, 4 November 2024 (UTC)
I oppose this proposal. I would keep both addr:milestone=* with the default unit and addr:ref=*. --Davileci (talk) 23:15, 4 November 2024 (UTC)
- I approve this proposal. we have thousands of this kind of addresses in the Whole Latin American areas. --JJIglesias (talk) 23:27, 4 November 2024 (UTC)
- I approve this proposal. This should add structure and formalize the de facto tag that's already in use, and is applicable in the Philippines, too. GOwin (talk) 23:55, 4 November 2024 (UTC)
- I approve this proposal. have seen those in abundance, good to formalize the tagging. --Zverik (talk) 07:07, 5 November 2024 (UTC)
- I approve this proposal. While I generally approve the concept, one may consider renaming the proposed tag to
addr:road_distanceto avoid confusion. --Fernando Trebien (talk) 13:53, 5 November 2024 (UTC)
- I approve this proposal. --Santamariense (talk) 14:34, 5 November 2024 (UTC)
- I approve this proposal. I think there are some details that can be improved, but I love this tag and can't see a reason to not approve it. It is the best way to map an address, close to a highway, that use km or mi markers. Name is consistent with highway=milestone. Thanks, Jorge! --Matheusgomesms (talk) 16:03, 5 November 2024 (UTC)
- I approve this proposal. Fidelis Assis (talk) 16:24, 5 November 2024 (UTC)
- I approve this proposal. -- DanielAgos (talk) 16:40, 5 November 2024 (UTC)
- I approve this proposal. I have seen a lot of this in Mexico.--Josuer (talk) 16:48, 5 November 2024 (UTC)
- I approve this proposal. --Baconcrisp
- I approve this proposal. In general, seems sensible as long as it's part of the address. However, I do oppose the "Km. #" notation -- this should use the actual values of the local addressing system, not this arbitrary syntax in English. If an actual value and units are of interest and cannot be easily determined from the field, then subkeys can be added. --HellMap (talk) 18:20, 5 November 2024 (UTC)
- I approve this proposal. --AntMadeira (talk) 18:47, 5 November 2024 (UTC)
- I approve this proposal. Everton Bortolini (talk) 18:57, 5 November 2024 (UTC)
- I approve this proposal. --Alexandre.moleiro (talk) 19:17, 5 November 2024 (UTC)
- I approve this proposal. --Глеб (talk) 19:56, 5 November 2024 (UTC)
- I approve this proposal. -- AndresDuhour (talk) 21:03, 5 November 2024 (UTC)
- I approve this proposal. In Latin America, this tag, once approved, will allow us to map kilometers on the side of the road, especially in Brazil, which has a lot of data to be mapped with this tag.-- Raphaelmirc (talk) 21:43, 5 November 2024 (UTC)
- I approve this proposal. -- Topolusitania (talk) 02:36, 6 November 2024 (UTC)
- I oppose this proposal. Proposal procedure is not followed. No matter the outcome of the vote this proposal cannot be accepted. I suggest to go to RFC stage, make an announcement on the forum and let the proposal process go normally.
- - RFC not announced on community forum
- - Vote not announced on community forum
- - RFC did not take at least two weeks (revived proposals need to start at RFC again)
- - Discussions on talk page have not been resolved
-- Spaanse (talk) 08:18, 6 November 2024 (UTC)
I have comments but abstain from voting on this proposal. When RFC happened? In 2019? Technically you can go straight to vote but it would be better to ask again whether anything new appeared - and maybe old vote has not proceeded because problems were found? --Mateusz Konieczny (talk) 09:04, 6 November 2024 (UTC) - replaced by "no" vote below- I oppose this proposal. Having the default unit depend on the country is a pain for data users. I've reread the section 'Tagging' multiple times, I don't understand what it means. I'm missing information about the relation to addr:housenumber. --Lonvia (talk) 13:07, 6 November 2024 (UTC)
- I approve this proposal. the more specific tags, the better --Kvestena (talk) 18:19, 6 November 2024 (UTC)
- I approve this proposal. --Cyberjuan (talk) 21:14, 6 November 2024 (UTC)
.svg){kind=icon}
- I approve this proposal. --Hugoren Martinako (talk) 06:39, 7 November 2024 (UTC)
- I oppose this proposal. If Lonvia (maintainer of Nominatim search engine) comments that tagging schema is unclear, hard to support and poorly defined... Then it means there are major problem with it and support among data consumers will be a big problem and it is worth at least trying to fix it. And that is why you make RFCs. Also, note that if poorly designed tagging schema will be approved it does not change much for data consumers. Main value in approval process is in discussing tagging schema. Vote itself does not obligate anyone to do anything. --Mateusz Konieczny (talk) 06:43, 7 November 2024 (UTC)
- I approve this proposal. While I support the adding of this tag and find it very valuable for regions such as latinamerica, I do find that the details and tagging schemes where not properly discussed in any forum. Edit: Now that things seem more clear now, I change to yes--Pantufla (talk) 11:22, 7 November 2024 (UTC)
- I oppose this proposal. This proposal hasn't followed the standard procedure. Time needs to be allowed for RFC. --julcnx (talk) 03:55, 8 November 2024 (UTC)
- I approve this proposal. In the Philippines, particularly in the mountainous parts of Cordillera along Halsema Highway, addresses are indicated on how many kilometers away are you from Baguio's Kilometer 0. I have no idea how to tag this address, until I saw this tag. —
- I approve this proposal. --Luisrobledo (talk) 17:57, 9 November 2024 (UTC)
- I approve this proposal. --felipeeugenio 11:52, 10 November 2024 (UTC)
- I have comments but abstain from voting on this proposal, I do not see point of having distance in address. When you use distance as information you should have reference point from which distance is measured. Photo illustration does not look as address table but as some kind of advertising post with distance that relates to post position. I see point of having option to set distance on sign that points to some specific destination which means: "destination is that far from here". but having distance in address, i do not get it. What would that mean: distance from nearest crossroad? distance from next settlement? What if road goes besides address, which direction distance should relate to?. --pedja
- I approve this proposal. I have been using it a long time and it is useful and necessary --Kapazao
- I approve this proposal. --sangonzag 2:15 p.m., 19 november (UTC)
- I approve this proposal. --Sanjorgepinho (talk) 20:03, 19 November 2024 (UTC)
- I approve this proposal. --SekeRob (talk) 13:22, 24 November 2024 (UTC)Been using this tag since whenever while mapping Italian fuel stations along out-of-town ways who's license specifically state the position along the road to about 10 meters exact, combo'd with nohousenumber=yes in the address, An example from the official registry Ministry of Economic Development:: Autostrada A11 FIRENZE-PISA N., Km. 35+500, dir. Ovest - 51030.
- I approve this proposal. As the proposal is currently written, I find it sufficient to cover the variety of global ways to format such distance based addresses. Particularly as relates to Greek distance based addressing, I can safely say that this will work perfectly fine. --PeachyOne (talk) 14:29, 25 November 2024 (UTC)
- I approve this proposal. --Hike&Map (talk) 09:35, 1 December 2024 (UTC) This is critical for addresses outside of the city center here in the city on Luzon where I'm primarily mapping