@Carlos LGBTQ = lesbian, gay, bi, trans and queer. It’s a common acronym. Not all people identify (or want to identify) as queer, since it has often been used against them.

I’m open to using other acronyms, but I suspect we’ll always come up short. 🙂

Yes, the TIGER import was done in 2007 An initial attempt in 2005 was reverted. The quality is pretty bad.

The PBF format has numerous tricks to save space, which means common tags for a “chunk of objects” might only take 1 byte to store the key.

There used to be a QA tool that used contour data to see if a river was mapped as flowing uphill, and flag it as suspect. But I can’t remember what it was.

@ftrebrien I’m suggesting lgbtq:*=*. So one can map lgbtq=primary for a simple, general case, and go into more details with lgbtq:lesbian=primary, lgbtq:gay_male=no, etc., etc.

@ChristianSW I covered problems with the gay=* tag in my first email, namely the LGBTQ community is larger than just gay (men).

@Alan Trick: There are a minority of LGBTQ venues aimed at certain subsets of the LGBTQ community, I think that could be solved with lgbtq:X=(primary/no/only)" etc. (e.g. lgbtq:lesbian=primary -> mainly a lesbian venue. lgbtq:lesbian=no -> no lesbians allowed. lgbtq:lesbian=only only lesbians (though I'm unsure about 'only')), so further details can be tagged. lgbtq=primary/designed/whatever` can mean “the LGBTQ in general”.

I thought about =designated, and it’s in keeping with OSM conventions. I thought it was only for things officially designed that by an official body. LGBTQ venues aren’t like that. 🤔

Welcome to OSM. I’m glad OSM has helped you with social issues. Is there anything it can’t do? ☺

Yeah, OSM is great for getting you to explore every little side street and stuff.

Welcome to OSM! It’s a shame the imagery you were looking at was well old. Maybe if you tell us where you’re looking at, there might be newer imagery?

I don’t think “urgent emergency” is as big a loophole as might be expected. I presume this refers to cases like the 2010 Haitian earthquake, which you cannot predict in advance. Some of the 2017 hurricanes only existed about a few days before HOT started working on it. But lots of HOT work (e.g. Global Mapathon to help end female genital mutilation), wouldn’t fall under that “urgent” case. You can’t fake a earthquake!

You say “The dataset you are ready to import to OSM cannot be older than two years”, and I’m pretty sure that’s not true. I’ve imported a dataset that started life decades ago, and is a few years old now. “Data quality” is important, and often associated with age, but one still have to look at the data, even if it’s “new”.

A tricky thing to describe is the emailing to the imports@ list. It’s not controlled by an import committee who will decide and vote and then tell you their result, so it’s hard to describe what “approval” means in this case. And if one person emails back “Looks good 👍” a new user might think that’s “approval”. “Seek consensus on the import@ mailing list” is more accurate, but vague if you’re not used to that form of decision making.

Cool. There was a long discussion on the talk@ list in August (starting here) about importing OLC data into OSM (a bad idea) compared software support (like your site). There is a discussion about adding the search to the OSM.org search bar, like your site, but I don’t think it’s been merged in yet…

Welcome to OSM! Have fun. 🙂

Welcome to OSM! Have fun. 🙂

Would the tracktype tag be useful here? It’s a little less subjective than smoothness.

Previously I said:

a place where it’s illegal to be out + LGBTQ … SoTM Asia 2018 had/have similar issues.

It would be remiss of me not to point out that the Indian courts have just overturned that law, and so this complaint no longer applies to upcoming SotM Asia 2018. 😁

Great to see you playing around with things. But be careful of importing these buildings, unless you follow the Import Guidelines….

If you make loads and loads of API calls and put the sever under undue load, then your app would be banned and people who are maintaining the servers for free in their spare time would be mad at you.

There is a /full API end point for nodes/ways/relations which, I think, will return all the members as well. I think you can also get many objects at once in one API call. That might help. (I haven’t done a lot with the API, so I’m not sure).

Another approach is to download the OSM data and just use that rather than querying the API for every object. You can download a regional extract from Geofabrik, or the use osmium to cut out a part of the planet file (or any other extract). You need to figure out how to store the file. But it’s the same XML format. It would be much faster than an API call for every element. When people do a lot of work on OSM objects this is probably more common than lots of API calls

I’m not really sure what you’re doing exactly. But from what you’ve described I can’t see anything obviously wrong or slow. So I don’t think there’s a faster way. I’m surprised you say it’s slow, how are you storing/processing/fetching the OSM data? Maybe it could be speeded up there?

@alexkemp: Your examples of “natural” & fair selection criteria is… grammar schools and UK universities in the 1960s?! 🤣🤣