I’m trying to add some of Hungary’s national parks as new places, but I bump into errors. In OSM (OpenStreetMap.org) I can find and download the correct polygon KML (initially an XML) file, for example https://www.openstreetmap.org/relation/377923. However, when I try to add the KML as a new place at iNat, I get error messages pointing to missing data or inappropriate format.
In this forum post I see some instructions to follow that require installing a piece of software, but since I’m in Chrome, I’m looking for a browser-based solution.
are you using a chromebook type stripped down laptop?
I think a browser-based solution for this is going to be a serious challenge to come by. I’ve personally only added one “place” to iNat and my challenges were quite different from the ones you’re having now. ime, addressing these kinds of challenges often requires the sort of flexibility you get from a full computer OS (and sometimes specifically Windows, as a lot of geospatial software is Windows-only). There are some Linux-based solutions, and fewer Mac-based options.
What are the specific error messages you’re getting from iNat when you try to add a place? Is it possible for you to open the kml file as a simple text file to find what the error messages are referring to?
How are you converting the XML file to KML? On your example page, the “Download XML” link at the bottom of the page returns a file that has no boundary data, just references to 5 “member” segments that would need to be downloaded and combined, then reformatted into KML format. Did you use a web tool for that conversion?
The European inventory of nationally designated protected areas holds information about designated areas and their designation types, which directly or indirectly create protected areas. This is version 20 and covers data reported until May 2022
If you need some help I can probably find a bit of time to isolate and convert the files. I’m a bit limited on time at the moment as I’m getting ready for vacation, but I have a little bit of time today, but then won’t have nay for a week or two after that.
UPDATE: i forgot to mention that you should check to make sure the place you intend to add doesn’t already exist in iNat. in the case of the park that you referenced in your original post, it looks like there’s already a version of the place in iNat: https://www.inaturalist.org/places/bukki.
just a guess, but if you export directly from OSM (without doing some transformations via the Overpass API), you’re often exporting points or lines or some combination of features, rather than a polygon. so if you try to import non-polygon features into iNat, iNat won’t like that.