I suspect that some users of GBIF-mediated data will use SimpleMappr. If so, you might be interested in an effort to provide a replacement (based on David’s original code).
The project is SimpleMappr Dkr (don’t ask), and there is a version running at https://simplemappr.cloud. I am the author of this project, and my goal is to get something that does the basics well enough for people to find it useful. If you use SimpleMappr, I’d welcome any feedback (for example, via a GitHub issue GitHub · Where software is built ). This is very much a side project, so I can’t make any promises, but it felt like a shame to lose such a useful tool, one in which David had invested a lot of time in creating and running.
Thanks so much @rdmpage for extending the life of this much-used, much-loved tool. It is also, for example, embedded in our TaxonWorks software for our adopters to use if they wish (and some do wish). We look forward to your efforts. I’m guessing the endpoint we need will change. See this @matt
Thanks @Debbie I don’t actually us SimpleMappr (nor, ironically, does @dshorthouse ) so I will rely on people who telling me what they need. Dogfooding is a much stronger driver, so it would make more sense that the person developing this would also be a user, but in the absence of that, you’ve got me.
It would be helpful to know what endpoint(s) TaxonWorks uses as so far I have only implemented a subset of the user interface. I suspect this won’t support what TaxonWorks does. If I knew the requirements I could investigate adding them.
If I understand what’s happening, it looks like TaxonWorks has an export routine that makes a text file that users then uploaded to SimpleMappr. Perhaps the port could accept either of the two txt file structures as an upload if it doesn’t already? See the “Point Data” tab on https://www.simplemappr.net for the two linked Examples.
