Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add rendering for aboriginal areas #3520

Closed
almccon opened this issue Nov 22, 2018 · 40 comments
Closed

Add rendering for aboriginal areas #3520

almccon opened this issue Nov 22, 2018 · 40 comments
Labels
admin new features Requests to render new features
Milestone
New features

Comments

@almccon
Copy link
Contributor

almccon commented Nov 22, 2018 •
edited
Loading

Aboriginal areas (also called Indigenous Protected Areas, Native Reserves, First Nation Reserves, Indian Reserves, Indian Reservations, etc., depending on the country) are important features that belong on the map.

There had been some discussion in #603 about protected areas in general, but that discussion seems to have narrowed to discuss only natural protected areas, not cultural ones. So if #3509 proposes closing #603, we need to have a new issue to discuss aboriginal protected areas.

Setting aside the debate about whether administrative boundaries belong in OSM at all (the ship has sailed on that one), it seems obvious to me that aboriginal areas are at least as important as many other boundaries we currently show, such as municipal boundaries, or even state/province boundaries. However, I also agree that they should not be overly prominent either (some have proposed that they be mapped as admin_level=2 which seems extreme). In many cases, you can cross in or out of an aboriginal area without knowing it or seeing other evidence on the ground. But in other cases, the boundaries are clearly marked on the ground, and sometimes even travel permits are required to enter these areas. Often there are different laws in effect within aboriginal areas, which seems like an important thing for a map user to know about.

Within OSM there does not appear to be a consensus about whether the tagging should be boundary=aboriginal_lands or whether we should use boundary=protected_area along with protect_class=24. Both are in relatively wide use, and I propose rendering both options until a tagging consensus has emerged. boundary=aboriginal_lands is quite popular in Canada and parts of the US, while boundary=protected_area + protect_class=24 is popular in South America and Australia. It's also worth noting that mappers have been doing a lot of tagging for the renderer, for example using leisure=nature_reserve incorrectly to get these indigenous areas to show up on the map, especially in Brazil.

Overpass query for boundary=aboriginal_lands: http://overpass-turbo.eu/s/DV4
screen shot 2018-11-22 at 22 nov 11 18 51

Overpass query for protect_class=24: http://overpass-turbo.eu/s/DV5
screen shot 2018-11-22 at 22 nov 11 14 31

taghistory

These areas vary widely in size: some Indian Reservations in the United States are larger in area than many European countries, but in other cases, such as the Nooksack Reservation near where I live, they can be as small as one acre (0.4 hectares). For this reason, we need a cartographic style that varies appropriately according to zoom level, and filters out smaller reservations at low zoom levels.

I propose adapting the current leisure=nature_reserve styling, but using a brown color instead of green. Nature reserves have a nice subtle fill color at low zoom levels, but when you zoom in, the fill goes away and they only show a light outline. This level of detail seems appropriate for aboriginal areas as well. The aboriginal areas start showing up at z8, which is the same time we first see national parks and military areas. As with those other features, the aboriginal areas are filtered by area, so only large ones show up. At z10, there is no more polygon fill, just an outline.

Here's southern Arizona at z8, before the change. Note the large empty spaces, some of which are actually occupied by large native reservations.
screen shot 2018-11-22 at 22 nov 9 16 32

Here's the same view, with the change applied.
screen shot 2018-11-22 at 22 nov 10 20 28

Here it is with a different brown:
screen shot 2018-11-22 at 22 nov 10 25 33

In the first screenshot I started with the html "brown" color #835c3b (hsl(28, 38%, 37%)), but then in the second screenshot I adjusted the hue more in the direction of yellow away from red, to avoid too much similarity with the existing red military areas. Currently I'm using #82643a (hsl(35, 38%, 37%))

A few more samples:

With #835c3b (reddish brown):
screen shot 2018-10-11 at 11 oct 5 17 22

With #82643a (orangey brown):
screen shot 2018-11-22 at 22 nov 11 04 23

screen shot 2018-11-22 at 22 nov 11 08 00
screen shot 2018-11-22 at 22 nov 11 09 40
screen shot 2018-11-22 at 22 nov 10 35 28

Here are some cases in Canada where aboriginal areas were also tagged with a type=boundary relation (perhaps tagging for the renderer): https://www.openstreetmap.org/relation/2227709 and https://www.openstreetmap.org/relation/2092741. The interaction of the dashed purple boundary line with the solid brown aboriginal_area line is a bit weird, but not terrible IMO. Once we have correct aboriginal rendering, we can remove these unnecessary boundary tags.

screen shot 2018-11-22 at 22 nov 11 36 45
screen shot 2018-11-22 at 22 nov 11 44 04

I've tested this change for Arizona and Washington State in the US, and British Columbia in Canada. I would have tested against Brazil, but most of the areas tagged with protect_class=24 there are incorrectly tagged as leisure=nature_reserve, so they already show up on the current rendering, just in green, not in brown.

Note: I based my code as closely as possible on #3509, which adds more natural protected areas to the map. If that PR gets merged first, I realize that this PR #3521 will probably need to be rebased to avoid some conflicts.
@almccon almccon mentioned this issue Nov 22, 2018
Merged
@kocio-pl kocio-pl added the new features Requests to render new features label Nov 22, 2018
@kocio-pl kocio-pl added this to the New features milestone Nov 22, 2018
@kocio-pl
Copy link
Collaborator

Hi, thanks for such a detailed research!

I was not aware of boundary=aboriginal_lands, but when making my own research about nature protection, I have also thought about boundary=protected_area + protect_class=24 being good candidate for rendering too.

My comments:

  • boundary=aboriginal_lands needs a wiki page to document how it is used and how it relates to the other scheme (of course similar remark should be done also on the other page)
  • orange brown looks very good and is easily recognizable for me, but it's interesting to me what is the visual difference between this and tourism=zoo ( https://wiki.openstreetmap.org/wiki/Tag:tourism%3Dzoo )

@jeisenbe
Copy link
Collaborator

jeisenbe commented Nov 22, 2018 via email

@bdiscoe
Copy link

bdiscoe commented Nov 23, 2018

When I created the Nez Perce reservation (USA, Idaho, https://www.openstreetmap.org/relation/3907949) in 2014, the only tagging I could find was boundary=protected_area + admin_level=5; it has subsequently been changed from admin_level to protect_class=24, which is apparently more correct, but also had the effect of making it vanish. I'll be delighted to see rendering of the area resume.

@Adamant36
Copy link
Contributor

I was just reading about a place in India with an aboriginal tribe that is technically under the control of the Indian government, but the tribe kills anyone that goes near them. So they are mostly considered autonomous and don't get prosecuted for anything.

There's also some places in South America where land that was once owned by indigenous people got taken over by farmers and was subsequently informally given back by the government, but in a lot of cases the farmers still live there with the indigenous people essentially squatting on their farms, on what "legally" might be the farmers land (but not really outside of that).

Here in America though most native tribes have their own laws, court systems, and clear boundaries as to what is their territory. There's also a few places here that have been stuck in legal limbo since the early sixties that are still in dispute as to ownership and know one lives there, but could probably still be classified as a protected area. So, I agree with @jeisenbe that both tags might be necessary. Since its not so cut and dry. Talking about it on the mailing list wouldn't hurt either though.

@matkoniecz
Copy link
Contributor

Can you consider making new proposal/updating existing at https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:boundary%3Daboriginal_lands ?

Currently it is completely unclear to me what is represented by this areas.

@almccon
Copy link
Contributor Author

almccon commented Nov 25, 2018

Thanks for the comments so far! You're all right that we should try to settle the tagging question at the same time as discussing the style.

I updated the existing proposal at https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:boundary%3Daboriginal_lands and I sent an email to the tagging list requesting that we start voting. Since it's been 10 years since the original proposal for boundary=aboriginal_lands, I hope we can quickly decide whether or not we need that tag or if we should deprecate it in favor of boundary=protected_area + protect_class=24 only. Please join in the tagging discussion via email or on the wiki.

@almccon
Copy link
Contributor Author

almccon commented Nov 25, 2018 •
edited
Loading

Also thanks @kocio-pl for pointing out the similarity with tourism=zoo. I hadn't thought of that.

Currently, we use #734a08 for tourism=zoo and tourism=theme_park. That's hsla(37, 87%, 24%, 1), which is fairly similar to the #82643a I'm using, which is hsla(35, 38%, 37%, 1).

The two colors are very similar in hue, somewhat similar in lightness, but the zoo color is much more saturated. The zoo/theme park labels are in bold type, while the aboriginal areas are in non-bold italics.

My gut feeling is that the colors and labels are different enough to be distinguished, in the rare cases where there would ever be any confusion. I think in most cases the zoos and theme parks will be significantly smaller than aboriginal areas, and filled with very different types of features. So confusion will be extremely rare. Note that the largest zoos in the world are on the order of 100 acres (40 hectares). Most aboriginal reservations are much larger, but there certainly are a few that are that small.

But then there is the concern about what kind of message it sends to the map reader if they notice that we're using a similar color for zoos and for reservations.

Here are a few examples of zoos and theme parks, for context:

Woodland Park Zoo, z16: https://www.openstreetmap.org/#map=16/47.6680/-122.3517
screen shot 2018-11-24 at 24 nov 7 46 02

San Diego Zoo, z15: https://www.openstreetmap.org/#map=15/32.7360/-117.1517
screen shot 2018-11-24 at 24 nov 7 47 14

Berlin Zoo, z14: https://www.openstreetmap.org/#map=14/52.5068/13.3378
screen shot 2018-11-24 at 24 nov 7 48 06

Paris Disneyland, z12: https://www.openstreetmap.org/#map=12/48.8505/2.7287
screen shot 2018-11-24 at 24 nov 7 49 59

@jeisenbe
Copy link
Collaborator

jeisenbe commented Nov 25, 2018 via email

@matkoniecz
Copy link
Contributor

But then there is the concern about what kind of message it sends to the map reader if they notice that we're using a similar color for zoos and for reservations.

Yeah, it would not be unreasonable to interpret it in way that would be really poor to OSM community.

@matkoniecz
Copy link
Contributor

(BTW, why are tourism boundaries and military areas in landuse.mss but
national parks and nature reserves are in admin.mss?)

First two may be more about how land is used, next two can be considered to be more about a legal status. But it may be a result of the history of code or requirements for layering order rather than result of a classification like this.

@pnorman
Copy link
Collaborator

pnorman commented Nov 25, 2018 •
edited
Loading

#734a08 is Lch(35,43,74) - lightness 35, chroma 43, hue 74 #82643a is Lch(44,29,77) - lightness 35, chroma 29, hue 77

Without calculating the exact values, I believe these colours are distinguishable before the transparency, but that's not enough in this case. The colour difference formulas work well for something like commercial vs industrial landuse where they're both similar concepts. Zoos and aboriginal reserves aren't similar concepts, so it needs to be very clear they're different. This could be done by different drawing methods, or different colours. I like the inset semi-transparent border look for this, so it means a different hue needs picking.

Perhaps a hue on the orange side would work, especially if it is a bit
brighter, eg #ba5d1c is hsla(25,74%,42%,1) and Lch(50,61,57), or similar

At full saturation the 70-80 hue range is a yellow-orange. This makes it difficult to get zoos different without making their lightness and chroma wildly different than the other inset transparent areas.

When I was in Boulder I went to the map library specifically to look at Indian reservations on maps. There were two cartograpies in use: Green, identical to nature reserves and parks, and brown. Green is a bad choice because it renders them similar to parks and nature reserves.

I'd rather move zoo's brown towards the green, perhaps 90, and use something like hue 70-60 for reserves

image
Washington Atlas & Gazetteer (Delorme, 2006)

image
Washington Road & Recreation Atlas, 1:1400000 scale (Benchmark Maps, 2007)

image
Washington Road & Recreation Atlas, larger scale (Benchmark Maps, 2007)

Map photos are not colour calibrated.

@almccon
Copy link
Contributor Author

almccon commented Nov 25, 2018

FYI everyone, it was pointed out to me that on the wiki proposal I still didn't have a good description of what these features actually are in the real world. I added a lot more description there: https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:boundary%3Daboriginal_lands#Proposal

Sorry for the confusion for people who live in countries where these features don't exist. I hope the new description on the wiki will help clarify things.

@almccon
Copy link
Contributor Author

almccon commented Nov 25, 2018

@pnorman in your Delorme photo, I think the green there is landuse, not a fill for the reservation. Looking at the larger crop of the same map that you shared in Slack, I see that they're indicating the boundary of the reservation with a small dashed black line (which is very hard to see because it mostly follows roads). They aren't using any fill color for the reservation.

Compare this larger photo with the boundaries of the Lummi Reservation that we have in OSM, which are correct.

delorme reservation

screen shot 2018-11-22 at 22 nov 11 09 40

@pnorman
Copy link
Collaborator

pnorman commented Nov 25, 2018

reservation with a small dashed black line (which is very hard to see because it mostly follows roads). They aren't using any fill color for the reservation.

Ah, well spotted. I think that serves as an example of why a dashed line is bad cartography when it's likely to overlap with other features.

I'm sure I could find an example of green for reservations,

@matkoniecz
Copy link
Contributor

@pnorman thanks for gathering this examples!

@almccon almccon mentioned this issue Nov 26, 2018
Open
@arecvlohe
Copy link

@almccon I would like to speak on the idea of what the tags would be. I am a developer and member of the Muscogee (Creek) Nation so I have some insight into this.

Tribal areas are mainly split into two areas: reservations and boundaries. Reservations are areas which exist within a state, or across states, that are domains where mainly tribal members reside. Then there are tribal boundaries, which are areas where both Native and non-Native communities exist but that share jurisdiction between Native and non-Native governments. Examples of tribal boundaries can be found in OK with tribes such as the Muscogee (Creek) Nation (http://mcngis.com/images/stories/maps/MCN_JURISDICTION_2016.pdf), and Cherokee Nation (http://geodata.cherokee.org/CherokeeNation/) just to name a couple.

Then things get more complex. For example, some tribes who were not set aside reservations will instead put land into trust for tribal members or for the government as a whole. An example of this would be the Thlopthlocco Tribal Town in Okemah, OK (http://tttown.org/about.html). In Florida, there is a band of traditional independent Seminoles who do not believe in land ownership and so have land that is put into trust for them by an outside organization (https://indianlaw.org/projects/past_projects/seminole).

Ideas that I have for tags would be: tribal_reservations, tribal_boundaries, and tribal_trust_lands. These things can be very nuanced so I think tags which speak to each one would be ideal. It's very possible that there just might not be any information, or any one willing to share the information, in regards to tribal trust lands. So that one may prove to not be helpful.

Now on to semantics. In the United States it's common for American Indians/Native Americans to just call one another Native. In South America, it's more common to hear Indigenous. And in Australia, it is more common to hear Aboriginal. This is mainly due to historical reasons and the same goes for the naming conventions above. For example, tribal_boundaries is used to refer to areas in OK, i.e. https://www.okhouse.gov/Documents/Districts/14-1101%20OK%20House%20and%20Tribal.pdf. The terms are certainly dated but it makes sense in terms of historical context.

But I suppose you would like to find something that unifies them. If that is your goal then a more all encompassing term would be aboriginal with any term afterward referring to jurisdictional matters, i.e. aboriginal_lands, aboriginal_trust_lands, aboriginal_reservations. That would be what would make the most sense to me.

I hope this helps!

@Adamant36
Copy link
Contributor

@arecvlohe, thanks for the extra information. It sounds semi complicated and like there might be a better tag possible for these areas then aboriginal lands. If you haven't already, it might be worth bringing up the same in the proposal for the tag. I don't remember seeing anything similar mentioned when I was reading through it and I think it would help people make a better decision to if its a good tag or not if they have the extra information.

https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:boundary%3Daboriginal_lands

@kocio-pl
Copy link
Collaborator

kocio-pl commented Dec 4, 2018

@arecvlohe There is a pending discussion on Tagging list about it, it would be great if you could join it with your knowledge on this topic. There is also voting started on boundary=aboriginal lands (ending 8.12), which you might be interested in:

https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:boundary%3Daboriginal_lands

@matkoniecz
Copy link
Contributor

I would like to speak on the idea of what the tags would be

Note that for this type of discussion tagging mailing list or OSM wiki are much better (for multiple reasons).

@kocio-pl
Copy link
Collaborator

kocio-pl commented Dec 8, 2018

It looks like boundary=aboriginal lands is going to be approved, so the next questions is what about alternatives? Will there be just one and the second will be discouraged or both will be used as currently?

https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Tag:boundary%3Daboriginal_lands

@matkoniecz
Copy link
Contributor

With the current situation I would render both for now.

Unfortunately different regions use different tagging and neither is horribly wrong.

@matkoniecz matkoniecz mentioned this issue Dec 8, 2018
Closed
@almccon
Copy link
Contributor Author

almccon commented Dec 14, 2018

Hi all, now that the boundary=aboriginal_lands tag has been approved (wiki page here), I wanted to revisit the outstanding question about what color to use for the rendering.

One promising suggestion from earlier in this issue is to change the color for zoos and theme parks to something other than brown, so we can use brown for aboriginal_lands. A couple of possible alternatives seem to be orange, or maybe purple if we stop using purple for admin boundaries (see #3489 and #3526).

Here are a few zoos using the current brown color:
https://www.openstreetmap.org/#map=15/47.6683/-122.3542
screen shot 2018-12-13 at 13 dec 10 04 04

https://www.openstreetmap.org/#map=16/47.3056/-122.5220
screen shot 2018-12-13 at 13 dec 10 05 00

https://www.openstreetmap.org/#map=17/47.55235/-122.08098
screen shot 2018-12-13 at 13 dec 10 04 20

Here are those three areas if we use the purple from admin boundaries: #ac46ac
screen shot 2018-12-13 at 13 dec 9 54 09
screen shot 2018-12-13 at 13 dec 9 48 00
screen shot 2018-12-13 at 13 dec 9 51 44

I kind of like the purple, because it matches well with the purple we're already using for attractions within the zoo itself.

I also tried using the gastronomy orange, which has the benefit of being similar to brown but not easily confused with aboriginal areas. But the downside of using orange is that zoos and theme parks don't really have much conceptually in common with the very prominent gastronomy features using orange on our map.

screen shot 2018-12-13 at 13 dec 9 57 17

screen shot 2018-12-13 at 13 dec 10 12 13

screen shot 2018-12-13 at 13 dec 10 08 26

What do you all think?

@turnsole80
Copy link

turnsole80 commented Dec 14, 2018 via email

@Tomasz-W
Copy link

Tomasz-W commented Dec 14, 2018 •
edited
Loading

@almccon Orange outline for zoos and theme parks was already proposed here: #3045 (comment), please continue discussion about outlines colour change in that ticket. As we might use current brown outline for museums, we can use orange for zoos and/ or theme parks.

@matkoniecz
Copy link
Contributor

please continue discussion about outlines colour change in that ticket

Given that main blocker for a rendering of aboriginal areas is a collision of current rendering proposal with zoo areas it is also on topic here.

@almccon
Copy link
Contributor Author

almccon commented Dec 14, 2018

Thanks @Tomasz-W, I wasn't aware of that other issue. I agree that whatever color we pick for aboriginal areas needs to be coordinated with many other color outlines.

It's also a bit of a chicken-and-egg problem. I would like to get aboriginal areas rendered sooner rather than later, without having to wait for the resolution of that other ticket, which has been open for almost a year.

Maybe we can find a "good enough" color for aboriginal areas to start with, and then potentially change them later in conjunction with changing several other boundary colors at the same time in #3045.

@kocio-pl
Copy link
Collaborator

I also think that the outline cleaning task should not be holding back everything. It just did not work as well as expected (nothing bad happened - just like many other interesting rendering ideas), so it's time to move on and maybe it will catch up later; who knows?

It seems to me that in general more intensive colors should be used for smaller features, so big ones do not dominate everything. So using above examples (which are quite similar to what I would pick), I think we could use strong violet for zoos/attraction park (more visible, related to attractions and emotions) and orange for museums (quite close to the brown, but not too strong because the outer line is darker), so simple brown (muted color) will be OK for aboriginal areas, because they are quite big.

@almccon almccon mentioned this issue Dec 14, 2018
Open
@matkoniecz
Copy link
Contributor

I also think that the outline cleaning task should not be holding back everything.

Yes, there is no obligation to solve issues in some order - but it may have some ideas that may make easier to solve this zoo collision issue.

@jeisenbe
Copy link
Collaborator

jeisenbe commented Dec 15, 2018 via email

@Tomasz-W
Copy link

Tomasz-W commented Dec 15, 2018 •
edited
Loading

I propose:

  • brown outlines for aboriginal_lands and museum (because they both have historical heritage protection character)
  • orange outlines for zoo and theme_park (violet is used for industrial areas fill and shop icons, while orange only for gastronomy icons, so I would use less loaded colour for it, to avoid unnecessary confusions as they all match to these features at the same level)

@polarbearing
Copy link
Contributor

I find the 'historical heritage' argument a bit dangerous with respect to the owners of the land. It is a reservation because it is their land, not because it is historic.

@Tomasz-W
Copy link

I find the 'historical heritage' argument a bit dangerous with respect to the owners of the land.

Maybe I wasn't precisious. I mean that both areas types function is to save cultural heritage.

@kocio-pl
Copy link
Collaborator

violet is used for industrial areas fill and shop icons, while orange only for gastronomy icons, so I would use less loaded colour for it, to avoid unnecessary confusions as they all match to these features at the same level

I don't think we can try match areas to lines and nodes.

@pnorman
Copy link
Collaborator

pnorman commented Dec 16, 2018

Maybe I wasn't precisious. I mean that both areas types function is to save cultural heritage.

I have to disagree, or take a view on preserving cultural heritage that is so wide as to be useless. People live there. There are elements of preserving culture, but the same is true of libraries, universities, malls, and most places people congregate.

I'd like to see this tested if anyone has the time.

I'd rather move zoo's brown towards the green, perhaps 90, and use something like hue 70-60 for reserves

@almccon
Copy link
Contributor Author

almccon commented Jan 29, 2019

For those not following along in the PR #3521, we're getting pretty closed to finished.

Currently in the PR aboriginal areas are a light brown #82643a, and thanks to #3582 zoos and other tourism are purple #660033, so there is no color conflict. The aboriginal brown is lighter than the original tourism brown #734a08, which is still used for amenity points.

Some samples of the current brown:
screen shot 2019-01-27 at 27 jan 4 33 19
screen shot 2019-01-27 at 27 jan 4 31 44

@astoff
Copy link

astoff commented Jan 29, 2019

But it is possible that the areas in Brazil or other countries lack as much political/administrative function, and are more of a “protected area” without self-governance.

This is correct. In fact, the Brazilian community agreed that the Indigenous Lands there have enough of a nature conservation function to be (provisionally) tagged as nature reserves. (Of course it's also true that, after a big import effort, we wanted these areas to render.)

In any case, when this issue is closed I'll fix the "wrong" tagging in Brazil. Thanks for working on this!

@kocio-pl
Copy link
Collaborator

kocio-pl commented Jan 29, 2019 •
edited
Loading

My feeling is that it's so stretched, that in fact it's tagging for rendering - these are for cultural and political protection, not nature... I'm happy that this code is finally in the repo.

@almccon
Copy link
Contributor Author

almccon commented Mar 17, 2019

I just saw my first aboriginal areas showing up on osm.org! Thanks again to everyone who helped get these on the map.
Screen Shot 2019-03-16 at 16 Mar 9 05 58
Screen Shot 2019-03-16 at 16 Mar 9 05 17
Screen Shot 2019-03-16 at 16 Mar 9 03 27
Screen Shot 2019-03-16 at 16 Mar 9 02 32

@kocio-pl
Copy link
Collaborator

Good to see that fixed. I hope Brazil is OK now and I guess Australia still needs retagging of some areas:

Screenshot_2019-03-17 OpenStreetMap

@jeisenbe
Copy link
Collaborator

jeisenbe commented Mar 17, 2019 via email

@1ec5 1ec5 mentioned this issue Jan 27, 2022
Open
@jeisenbe jeisenbe added the admin label Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
admin new features Requests to render new features
Projects
None yet
Milestone
New features
Development

No branches or pull requests